Did you know Strapi Cloud supports external databases?
This post will cover how to add an external database to your strapi cloud account.
Although this is a supported feature, it is not something we recommend unless you have a specific reason for doing so. Proceed at your own risk.
- It may impact the performance of running SQL connection over the public internet.
- Network latency. Choose a data center closer to your cloud region.
- Security is your responsibility.
- No support from Strapi Cloud SE
We recommend using the default Strapi Cloud database for most users because it is optimized for Strapi.
But, in your case, you need to use an external database, so let's see how we can set one up on our cloud account.
- Local Strapi project.
- The same project deployed to Strapi Cloud.
- Credential for an external database.
- If using an existing database, the schema must match the Strapi project schema.
You can watch the following video on deploying a new Strapi Project to the cloud. But in this example, I already have a project running locally on my computer.
I have a local project running SQLite database, and the same project deployed on Strapi Cloud with the default PostgreSQL database.
But now I want to point my Strapi project to my external production db hosted on digital ocean.
Let's take a look at how to accomplish this. The steps are similar to how you would do them on a regular project.
But, I wanted to make this walkthrough as a supplementary post to our documentation. Strapi Docs DB Settings
warning: before proceeding, make sure you have all your data backed up.
We are currently using sqlite database locally and default postgreql on Strapi Cloud.
config/server.js
const path = require("path");
module.exports = ({ env }) => {
const client = env("DATABASE_CLIENT", "sqlite");
const connections = {
mysql: {
connection: {
connectionString: env("DATABASE_URL"),
host: env("DATABASE_HOST", "localhost"),
port: env.int("DATABASE_PORT", 3306),
database: env("DATABASE_NAME", "strapi"),
user: env("DATABASE_USERNAME", "strapi"),
password: env("DATABASE_PASSWORD", "strapi"),
ssl: env.bool("DATABASE_SSL", false) && {
key: env("DATABASE_SSL_KEY", undefined),
cert: env("DATABASE_SSL_CERT", undefined),
ca: env("DATABASE_SSL_CA", undefined),
capath: env("DATABASE_SSL_CAPATH", undefined),
cipher: env("DATABASE_SSL_CIPHER", undefined),
rejectUnauthorized: env.bool(
"DATABASE_SSL_REJECT_UNAUTHORIZED",
true
),
},
},
pool: {
min: env.int("DATABASE_POOL_MIN", 2),
max: env.int("DATABASE_POOL_MAX", 10),
},
},
mysql2: {
connection: {
host: env("DATABASE_HOST", "localhost"),
port: env.int("DATABASE_PORT", 3306),
database: env("DATABASE_NAME", "strapi"),
user: env("DATABASE_USERNAME", "strapi"),
password: env("DATABASE_PASSWORD", "strapi"),
ssl: env.bool("DATABASE_SSL", false) && {
key: env("DATABASE_SSL_KEY", undefined),
cert: env("DATABASE_SSL_CERT", undefined),
ca: env("DATABASE_SSL_CA", undefined),
capath: env("DATABASE_SSL_CAPATH", undefined),
cipher: env("DATABASE_SSL_CIPHER", undefined),
rejectUnauthorized: env.bool(
"DATABASE_SSL_REJECT_UNAUTHORIZED",
true
),
},
},
pool: {
min: env.int("DATABASE_POOL_MIN", 2),
max: env.int("DATABASE_POOL_MAX", 10),
},
},
postgres: {
connection: {
connectionString: env("DATABASE_URL"),
host: env("DATABASE_HOST", "localhost"),
port: env.int("DATABASE_PORT", 5432),
database: env("DATABASE_NAME", "strapi"),
user: env("DATABASE_USERNAME", "strapi"),
password: env("DATABASE_PASSWORD", "strapi"),
ssl: env.bool("DATABASE_SSL", false) && {
key: env("DATABASE_SSL_KEY", undefined),
cert: env("DATABASE_SSL_CERT", undefined),
ca: env("DATABASE_SSL_CA", undefined),
capath: env("DATABASE_SSL_CAPATH", undefined),
cipher: env("DATABASE_SSL_CIPHER", undefined),
rejectUnauthorized: env.bool(
"DATABASE_SSL_REJECT_UNAUTHORIZED",
true
),
},
schema: env("DATABASE_SCHEMA", "public"),
},
pool: {
min: env.int("DATABASE_POOL_MIN", 2),
max: env.int("DATABASE_POOL_MAX", 10),
},
},
sqlite: {
connection: {
filename: path.join(
__dirname,
"..",
env("DATABASE_FILENAME", "data.db")
),
},
useNullAsDefault: true,
},
};
return {
connection: {
client,
...connections[client],
acquireConnectionTimeout: env.int("DATABASE_CONNECTION_TIMEOUT", 60000),
},
};
};The above file is used to configure your server. And most of the work is already done. But first, we must add your database credential on Strapi Cloud to point to our external database and then redeploy our project.
Let's see how this is done.
Before saving and pushing changes to github let's log into Strapi Cloud and add our environment variables.
# Database
DATABASE_CLIENT=postgres
DATABASE_HOST=your_host
DATABASE_PORT=your_port
DATABASE_NAME=your_db_name
DATABASE_USERNAME=your_username
DATABASE_PASSWORD=your_password
DATABASE_SSL=true
DATABASE_SSL_REJECT_UNAUTHORIZED=false
DATABASE_SHEMA=publicnote: To ensure a smooth deployment, it is recommended to not change the names of the environment variables.
You can add your variables under settings -> variables
Once you added all your required variables, click the save button.
If you have any changes in the application, you can push them to git and trigger a redeploy; otherwise, you can trigger a redeploy after saving your environment variables.
Since I don't have any changes in code, I will redeploy my project manually.
Once your application is finished building, you should now be using your external database.
If you're using Strapi Cloud project and had previously added environment variables related to an external database, reverting back to the default database can be accomplished quickly.
All you need to do is remove the previously added environment variables from the Strapi Cloud project dashboard, click the save button that I forgot to click, and redeploy. This will revert to the default database.
Remember that any data you had on the external database will no longer be accessible after this action.
In conclusion, Strapi Cloud does support external databases. However, it's only recommended if you have a specific reason to do so.
In this post, we've walked through the process of adding an external database to a Strapi Cloud project, along with the necessary configurations and environment variables.
We also covered how to revert to the default database. While using an external database may be a viable option for some users, weighing the caveats and understanding the potential risks involved, such as performance impact, network latency, and security concerns, is essential.
If you prefer a video walkthrough, you can find it here