moved configurations page

2025-03-11 10:59:29 +02:00
parent 5a5da0d6a1
commit ac989a6ed1
30 changed files with 11817 additions and 9814 deletions
@@ -39,7 +39,7 @@ For example, the EmailPass Auth Module Provider authenticates a user using their

 By default, users of all actor types can authenticate with all installed auth module providers.

-To restrict the auth providers used for actor types, use the [authMethodsPerActor option](/references/medusa-config#http-authMethodsPerActor-1-3) in Medusa's configurations:
+To restrict the auth providers used for actor types, use the [authMethodsPerActor option](!docs!/learn/configurations/medusa-config#httpauthMethodsPerActor) in Medusa's configurations:

 ```ts title="medusa-config.ts"
 module.exports = defineConfig({
@@ -67,7 +67,7 @@ The Medusa application's authentication API routes are defined under the `/auth`

 By default, the Medusa application you created will have an `AUTH_CORS` environment variable, which is used as the value of `authCors`.

-Refer to [Medusa's configuration guide](/references/medusa-config#authCors) to learn more about the `authCors` configuration.
+Refer to [Medusa's configuration guide](!docs!/learn/configurations/medusa-config#httpauthCors) to learn more about the `authCors` configuration.

 ---

@@ -21,7 +21,7 @@ In this document, you’ll learn how to deploy your Medusa application to [Railw

 <Note>

-The same Medusa project is used to deploy the server and worker modes. Learn more about the `workerMode` configuration in [this document](/references/medusa-config#workermode).
+The same Medusa project is used to deploy the server and worker modes. Learn more about the `workerMode` configuration in [this document](!docs!/learn/configurations/medusa-config#workermode).

 </Note>

@@ -74,7 +74,7 @@ The `redisUrl` configuration specifies the connection URL to Redis to store the

 <Note>

-Learn more in the [Medusa Configuration documentation](/references/medusa-config#redisurl).
+Learn more in the [Medusa Configuration documentation](!docs!/learn/configurations/medusa-config#redisurl).

 </Note>

@@ -1804,7 +1804,7 @@ return res.json({
 })
 ```

-You first retrieve the [http Medusa configuration](/references/medusa-config#http) which holds configurations related to JWT secrets and expiration times. You then use the `jsonwebtoken` package to sign a token containing the wishlist ID. You return the token in the response.
+You first retrieve the [http Medusa configuration](!docs!/learn/configurations/medusa-config#http) which holds configurations related to JWT secrets and expiration times. You then use the `jsonwebtoken` package to sign a token containing the wishlist ID. You return the token in the response.

 ### Test API Route

@@ -116,7 +116,7 @@ AUTH_CORS=http://localhost:5173,http://localhost:9000,http://localhost:3000

 You can add other origins as well if necessary.

-Learn more about CORS configurations in [this guide](/references/medusa-config#http-storeCors-1-1).
+Learn more about CORS configurations in [this guide](!docs!/learn/configurations/medusa-config#httpauthcors).

 ---

@@ -7,4 +7,4 @@ Error: connect ECONNREFUSED ::1:5432
 This error occurs because the application couldn't connect to the PostgreSQL database. The issue could be one of the following:

 1. PostgreSQL server isn't running. Make sure it's always running while the Medusa application is running.
-2. The connection URL to your PostgreSQL database is incorrect. This could be because of incorrect credentials, port number, or connection URL format. The format should be `postgres://[user][:password]@[host][:port]/[dbname]`. Make sure that the connection URL format is correct, and the credentials passed in the URL are correct. You can learn more about formatting the connection URL [here](/references/medusa-config#databaseUrl)
+2. The connection URL to your PostgreSQL database is incorrect. This could be because of incorrect credentials, port number, or connection URL format. The format should be `postgres://[user][:password]@[host][:port]/[dbname]`. Make sure that the connection URL format is correct, and the credentials passed in the URL are correct. You can learn more about formatting the connection URL [here](!docs!/learn/configurations/medusa-config#databaseUrl)
@@ -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 [databaseUrl configuration documentation](/references/medusa-config#databaseUrl) to learn how to set the database URL for an installed Medusa application.
+Refer to the [databaseUrl configuration documentation](!docs!/learn/configurations/medusa-config#databaseUrl) to learn how to set the database URL for an installed Medusa application.
@@ -19,4 +19,4 @@ module.exports = defineConfig({
 })
 ```

-Learn more about these configurations in [this documentation](/references/medusa-config#http).
+Learn more about these configurations in [this documentation](!docs!/learn/configurations/medusa-config#http).
@@ -10,5 +10,5 @@ port: 9000

 This means that there's another process running at port `9000`. You need to either:

- Change the default port used by the Medusa application. You can do that by setting the `PORT` environment variable to a new port. When you do this, make sure to change the port used in other apps that interact with your Medusa application, such as in your [admin](/references/medusa-config#admin) or [storefront](../../../nextjs-starter/page.mdx#change-medusa-application-url).
+- Change the default port used by the Medusa application. You can do that by setting the `PORT` environment variable to a new port. When you do this, make sure to change the port used in other apps that interact with your Medusa application, such as in your [admin](!docs!/learn/configurations/medusa-config#admin) or [storefront](../../../nextjs-starter/page.mdx#change-medusa-application-url).
 - Terminate other processes running on port `9000`.
@@ -78,4 +78,4 @@ module.exports = defineConfig({

 Where `qs` would be the third-party library you're using.

-Learn more about the `optimizeDeps` configuration in the [Vite documentation](https://vite.dev/config/dep-optimization-options). Also, learn more about Medusa's admin configurations in [this documentation](/references/medusa-config).
+Learn more about the `optimizeDeps` configuration in the [Vite documentation](https://vite.dev/config/dep-optimization-options). Also, learn more about Medusa's admin configurations in [this documentation](!docs!/learn/configurations/medusa-config).