Shahed Nasser
1e4ff3d047
* docs: fixes to Medusa Cloud sections * apply comments --------- Co-authored-by: Oli Juhl <59018053+olivermrbl@users.noreply.github.com>
100 lines
4.4 KiB
Plaintext
100 lines
4.4 KiB
Plaintext
export const metadata = {
|
||
title: `${pageNumber} Medusa Deployment Overview`,
|
||
}
|
||
|
||
# {metadata.title}
|
||
|
||
In this chapter, you’ll learn the general approach to deploying the Medusa application.
|
||
|
||
## Medusa Project Components
|
||
|
||
A standard Medusa project is made up of:
|
||
|
||
- Medusa application: The Medusa server and the Medusa Admin.
|
||
- One or more storefronts
|
||
|
||
|
||
|
||
You can either deploy the Medusa application fully (server with the admin), or deploy the Medusa Admin separately. The storefront is always deployed separately.
|
||
|
||
---
|
||
|
||
## Deploying the Medusa Server
|
||
|
||
You must deploy the Medusa server before the admin or storefront, as both of them connect to it and won’t work without a deployed Medusa server URL.
|
||
|
||
|
||
|
||
The Medusa server must be deployed to a hosting provider supporting Node.js server deployments, such as Railway, DigitalOcean, AWS, Heroku, etc…
|
||
|
||
<Note title="Tip">
|
||
|
||
For optimal experience, make sure that the hosting provider and plan offer at least 2GB of RAM.
|
||
|
||
</Note>
|
||
|
||
Your server connects to a PostgreSQL database, Redis, and other services relevant for your setup. Most hosting providers support deploying and managing these databases along with your Medusa server (such as Railway and DigitalOcean).
|
||
|
||
### How to Deploy Medusa?
|
||
|
||
Medusa Cloud is our managed services offering that makes deploying and operating Medusa applications possible without having to worry about configuring, scaling, and maintaining infrastructure. Medusa Cloud hosts your server, Admin dashboard, database, and Redis instance.
|
||
|
||
With Medusa Cloud, you maintain full customization control as you deploy your own modules and customizations directly from GitHub:
|
||
|
||
- Push to deploy.
|
||
- Multiple testing environments.
|
||
- Preview environments for new PRs.
|
||
- Test on production-like data.
|
||
|
||
[Sign up and learn more about Medusa Cloud](https://medusajs.com/contact)
|
||
|
||
To self-host Medusa, the [next chapter](./general/page.mdx) explains the general steps to deploy your Medusa application.
|
||
|
||
Refer to [this reference](!resources!/deployment) to find how-to deployment guides for general and specific hosting providers.
|
||
|
||
---
|
||
|
||
## Deploying the Medusa Admin
|
||
|
||
### Deploy Admin with the Server
|
||
|
||
The Medusa Admin can be deployed on the same hosting with the server.
|
||
|
||
In this scenario, make sure the hosting provider and plan of your choice provide at least 2GB of RAM, as the admin build requires high RAM usage.
|
||
|
||
|
||
|
||
<Note title="Tip">
|
||
|
||
The [server deployment guides](!resources!/deployment) mention details on how to deploy the admin with the Medusa server.
|
||
|
||
</Note>
|
||
|
||
### Deploy Admin Separately
|
||
|
||
You can deploy the admin into a separate hosting provider or instance. The admin can be hosted on providers that support front-end websites and frameworks, such as Vercel.
|
||
|
||
<Note title="Important">
|
||
|
||
Per Vercel’s [license and plans](https://vercel.com/pricing), their free plan can only be used for personal, non-commercial projects. So, you can deploy the Medusa Admin on the free plan for development purposes, but for commercial projects, you must update your Vercel plan.
|
||
|
||
</Note>
|
||
|
||
Refer to [this reference](!resources!/deployment) to find how-to deployment guides for specific hosting providers.
|
||
|
||
---
|
||
|
||
## Deploying the Storefront
|
||
|
||
The storefront is deployed separately from the Medusa application, and the hosting options depend on the tools and frameworks you use to create the storefront.
|
||
|
||
If you’re using the Next.js Starter storefront, you may deploy the storefront to any hosting provider that supports frontend frameworks, such as Vercel.
|
||
|
||
<Note title="Important">
|
||
|
||
Per Vercel’s [license and plans](https://vercel.com/pricing), their free plan can only be used for personal, non-commercial projects. So, you can deploy the storefront on the free plan for development purposes, but for commercial projects, you must update your Vercel plan.
|
||
|
||
</Note>
|
||
|
||
Refer to [this reference](!resources!/deployment) to find how-to deployment guides for specific hosting providers.
|