asyavee/medusa-store
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

docs: update config to be camel case (#7501)

Browse Source
This commit is contained in:
Shahed Nasser
2024-05-28 15:52:03 +03:00
committed by GitHub
parent 82be054a1a
commit 8f97af0d91
6 changed files with 9 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
www/apps/book/app/basics/scheduled-jobs/page.mdx
View File

@@ -67,7 +67,7 @@ To test out your scheduled job:
const projectConfig = {
// ...
// Uncomment the following lines to enable REDIS
redis_url: REDIS_URL,
redisUrl: REDIS_URL,
}
```

4
www/apps/resources/app/deployment/medusa-application/digitalocean/page.mdx
View File

@@ -105,13 +105,13 @@ const DATABASE_URL =
`@${DB_HOST}:${DB_PORT}/${DB_DATABASE}`
```
In addition, add to the `projectConfig` property in the exported object a new property `database_extra`:
In addition, add to the `projectConfig` property in the exported object a new property `databaseExtra`:
```js title="medusa-config.js"
module.exports = {
projectConfig: {
// ...
database_extra: { ssl: { rejectUnauthorized: false } },
databaseExtra: { ssl: { rejectUnauthorized: false } },
},
}
```

4
www/apps/resources/app/deployment/medusa-application/general/page.mdx
View File

@@ -32,13 +32,13 @@ Make sure the `start` script in your `package.json` runs migrations, the `build`
## Set SSL Database Option
In production, it’s recommended to set the [database_extra option](/references/medusa-config#database_extra) in `medusa-config.js` to disable the `ssl.rejectUnauthorized` option:
In production, it’s recommended to set the [databaseExtra option](/references/medusa-config#databaseExtra) in `medusa-config.js` to disable the `ssl.rejectUnauthorized` option:
```js title="medusa-config.js" highlights={[["4"]]}
module.exports = {
projectConfig: {
// ...
database_extra: process.env.NODE_ENV !== "development" ?
databaseExtra: process.env.NODE_ENV !== "development" ?
{
ssl: {
rejectUnauthorized: false,

4
www/apps/resources/app/deployment/medusa-application/heroku/page.mdx
View File

@@ -186,13 +186,13 @@ Update the `scripts` in `package.json` to include the following scripts:
### Changes to medusa-config.js
Add to the `projectConfig` property in the exported object a new property `database_extra`:
Add to the `projectConfig` property in the exported object a new property `databaseExtra`:
```js title="medusa-config.js"
module.exports = {
projectConfig: {
// ...
database_extra: { ssl: { rejectUnauthorized: false } },
databaseExtra: { ssl: { rejectUnauthorized: false } },
},
}
```

2
www/apps/resources/app/troubleshooting/_sections/database-errors/docker.mdx
View File

@@ -22,4 +22,4 @@ npx create-medusa-app@latest --db-url "postgres://user:password@localhost:<YOUR_
Where `<YOUR_PORT>` is the exposed port if it's different than `5432`.
Refer to the [database_url configuration documentation](/references/medusa-config#database_url) to learn how to set the database URL for an installed Medusa backend.
Refer to the [databaseUrl configuration documentation](/references/medusa-config#databaseUrl) to learn how to set the database URL for an installed Medusa backend.

2
www/apps/resources/app/troubleshooting/_sections/database-errors/privileges.mdx
View File

@@ -1,3 +1,3 @@
The database user you use in the `database_url` Medusa backend configuration must have create privileges. Otherwise, you'll face problems when running migrations.
The database user you use in the `databaseUrl` Medusa backend configuration must have create privileges. Otherwise, you'll face problems when running migrations.
If you're using the `postgres` superuser, then it should have these privileges by default. Otherwise, make sure to grant your user create privileges. You can learn how to do that in [PostgreSQL's documentation](https://www.postgresql.org/docs/current/ddl-priv.html).