@@ -116,22 +116,16 @@ After pushing the changes, you can find the files in your GitHub repository.
After logging into your account, click on the Create button at the top right, then choose App.
### Choose Repository
In the Create App page, choose GitHub from the Service Provider list.
If you haven’t given DigitalOcean access before, click on Manage Access under Source Code. You’ll then be redirected to GitHub to give DigitalOcean access.
Once DigitalOcean have access to your GitHub account, you should see a Repository input. Click on it and search for the repository you created earlier.
Once DigitalOcean has access to your GitHub account, you should see a Repository input. Click on it and search for the repository you created earlier.
Additional inputs will show up to choose the Branch, Source Directory, and Autodeploy options.
If you host your Medusa backend in a monorepo, you should change the Source Directory to the directory the backend is available in the repository. Otherwise, it can be left as is.
Once you’re done, click Next to move on to the next step.
@@ -140,32 +134,22 @@ Once you’re done, click Next to move on to the next step.
In the next step, you’ll see the resources to create.
If you have a Dockerfile available in the backend’s codebase (which is available by default), you’ll have two resources showing. You can remove it by clicking on the trash icon at the right of the resource.
If you have a Dockerfile available in the backend’s codebase, you’ll have two resources showing. You can remove it by clicking on the trash icon at the right of the resource.
By default, DigitalOcean hosts the web service in a sub-path of the domain name of the created App. To change it to the root of the domain, click on the edit icon at the right of the Web Service resource.
Then, scroll to HTTP Request Routes and expand it by clicking on Edit at its right. Change the value of the Routes input to `/`.
Once you’re done click Save. You’ll be taken back to the Resources page.
### Specify Database Resources
On the same page, expand the Add Resources section, choose Database, then click Add.
In the new page, you’ll be shown a PostgreSQL database to be created. Notice that it’s important to choose a name that you’ll remember as you’ll need the name in next steps. You can leave the name as is if it’s not necessary to change it.
Once you’re done, click Create and Attach. You’ll be redirected back to the previous page with the database added to the resources.
Once you’re done, click Next to move on to the next step.
### Set Environment Variables
@@ -174,8 +158,6 @@ In this section, you’ll add environment variables that are essential to your M
You should see two ways to add environment variables: Global or specific to the Web Service.
Click Edit on the second row to add environment variables specific to the Web Service. Add the following environment variables:
```bash
@@ -213,8 +195,6 @@ Once you’re done click Save.
In the next section, you’ll be shown the app info and the region it will be deployed to. You can leave it all as is or make changes if you find it necessary.
Once you’re done, click Next to go to the next step.
In the final step, you can see a review of everything you created. If everything looks good, scroll down and click Create Resource.
@@ -225,16 +205,10 @@ While the backend is being deployed, you can create the Redis resource.
Click the Create button at the top right and choose Database from the dropdown.
In the new page under Choose a database engine, choose Redis.
Then, scroll down to the “Choose a name” input. Since you used the name `redis` in the `REDIS_URL` environment variables, change the value to `redis` here.
Once you’re done, click on Create Database Cluster.
### Attach Redis Database
@@ -243,12 +217,8 @@ Once the Redis database is created go back to the App you created earlier by cho
Click at the white Create button at the top right and choose Create/Attach Database.
In the new page, click on the Previously Created DigitalOcean Database radio button. Then, under Database Cluster select the Redis database you just created.
Once you’re done click Attach Database. This will add the Redis database to the list of resources of your App and will trigger a redeploy of the App.
---
@@ -257,11 +227,11 @@ Once you’re done click Attach Database. This will add the Redis database to th
Once the redeployment is complete, copy the URL of the App which can be found under the App’s name.
Then, go to `<YOUR_APP_URL>/store/products`. If the deployment was successful, you should receive a JSON response.
### Health Route
You can access `/health` to get health status of your deployed backend.
### Testing the Admin
@@ -288,8 +258,6 @@ medusa user --email <EMAIL> --password <PASSWORD>
Make sure to replace `<EMAIL>` and `<PASSWORD>` with the credentials you want to give the user.
---
## Add Environment Variables
@@ -298,12 +266,8 @@ You’ll likely need to add environment variables later such as Admin Cross-Orig
To add environment variables, on the App’s page click on Settings and choose the Web Service component.
Then, scroll down and find Environment Variables. You can expand the environment variables by clicking Edit on the right. Here, you can edit, add, and remove environment variables.
Once you click Save, the environment variables will be saved and a redeployment will be triggered.
@@ -96,6 +96,10 @@ Once the build process is complete, a new deployment with the infrastructure res
After the deployment is finished, navigate to Resources → [AppName] (Medusa in this example) → Overview. Then, under the Resource Outputs section you should see the "AccessUrl". This is the backend's URL that you can use to access API endpoints and test them. You can try getting the list of products using the endpoint `<AccessUrl>/store/products`.
### Health Route
You can access `/health` to get health status of your deployed backend.
@@ -191,6 +191,10 @@ If you generated a random domain, you can find it by clicking on the GitHub repo
:::
### Health Route
You can access `/health` to get health status of your deployed backend.
### Testing the Admin
:::note
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Shahed Nasser
GitHub