Jump toUpdate content
Deploying Strapi on an Instance
Strapi - Overview
Strapi is an open-source, Node.js based, headless CMS to manage content and make it available through a fully customizable API. Unlike traditional CMSs such as Wordpress, with Strapi the content is decoupled from the front end. Strapi simultaneously provides for content creators, who get an easy-to-use, database-driven interface to create, organize and manage content, and developers, who get the convenience of an API that they can use to query, deliver and integrate that content to diverse applications and front ends.
In this tutorial you will learn how to deploy Strapi on a Scaleway Instance.
You may need certain IAM permissions to carry out some actions described on this page. This means:
- you are the Owner of the Scaleway Organization in which the actions will be carried out, or
- you are an IAM user of the Organization, with a policy granting you the necessary permission sets
- You have an account and are logged into the Scaleway console
- You have configured your SSH Key
- You have a Instance running on Ubuntu Bionic Beaver (18.04).
Connect to your Instance using SSH.
Update the apt packet cache and upgrade the software already installed on the instance:apt update && apt upgrade -y
Strapi requires Node.js minimum version 12.x in order to run, as well as npm minimum version 6.x. Use the following command to add a maintained and up to date repository for Debian-based Node.js:apt install -y curl && curl -sL https://deb.nodesource.com/setup_14.x | bash -
Install Node.js with the following command (npm will also install):apt-get install -y nodejs
Check that Node.js and npm are installed in minimum versions 12.x and 6.x respectively:node -v && npm -v
You should see an output confirming the installed version number of each.
Strapi uses the yarn package manager. Install the repository for the required version of Yarn by running the following commands:curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add -echo "deb https://dl.yarnpkg.com/debian/ stable main" | tee /etc/apt/sources.list.d/yarn.listapt update && apt install yarn
Check that yarn has installed with the following command:yarn -v
You should see an output confirming the installed version number.
Installing Strapi and creating a project
Navigate to a your home directory and create a new folder for your Strapi project:cd /home/<user>mkdir strapi-projects
Install Strapi in this directory and create a new project:cd strapi-projectsyarn create strapi-app my-strapi-project --quickstartNote:
--quickstartflag installs Strapi using an SQLite database. You can omit this flag, but you need to follow some other steps to configure an alternative database (Strapi supports PostgreSQL, MongoDB, SQLite, MySQL and MariaDB). Your choice of database must be installed and running locally before you create your Strapi project.
You should see Strapi install and run (this may take a few minutes). There is some useful information at the end of this output that you may wish to read and take note of, particularly about the different commands like
yarn startthat you can use to run your Strapi app in different modes. In any case, the output should finish with a message like:Create your first administrator 💻 by going to the administration panel at:┌─────────────────────────────┐│ http://localhost:1337/admin │└─────────────────────────────┘[2020-12-02T09:20:59.034Z] debug HEAD /admin (14 ms) 200[2020-12-02T09:20:59.038Z] info ⏳ Opening the admin panel...
We’re now ready to start configuring our Strapi app.Tip:
There is some useful information about working with Strapi in the rest of the output in your terminal here, that you may wish to read and take note of.
Setting up Strapi and adding content
In this step, we will use the Strapi dashboard to configure Strapi for a very simple blog use case. First we need to create a SuperAdmin user, then set up a database to hold our blog posts, then write a “Hello World” blog post and see how to access it.
In a browser, go to
http://<Instance IP Address>:1337/admin.
You should see the following:
Complete the form with your desired information in order to create an admin user, then click
Let's Start. Next, we will essentially define a new database to hold our blog content.
Create Your First Content Type.
Blogas the display name (UID will auto-complete), and click
The following screen displays:
Next, we will define the fields for our Blog database. We’ll add two text fields, one to hold the title of each blog post, and one to hold the content of each post:
Text. The following screen displays:
Titlein the name field, and click
Add another field:
You are taken back to the list of possible field types:
Text. The following screen displays:
Contentin the name field, and select
Long textunderneath, then click
A summary of the Blog collection that you have just created displays. Cick
Strapi will restart and refresh your dashboard.
Now that we have set up the database to hold our blog, we will create a quick “Hello World” blog post:
Blogs, which now appears as a Collection Type in the top left of the screen:
The following screen displays:
Add New Blogin the top right. The following screen displays:
Enter a title and content of your choice, or use the following ‘Hello World’ examples. Then click
Save, followed by
The screen should now look like this:
The final step is to make all our blog content publicly available.
In the left-hand menu, click
Settings, then under the
Users & Permissions pluginclick
Public. The following screen displays:
Permissions, you can see our
BLOGapplication. Check the
findboxes to enable the public to find our blog posts. Then click
Now we can access our “Hello World” blog post from the built-in API with the following action:
Open a new browser tab, and go to
http://<Your-Virtual-Instance-IP:1337/blogs. The following will display:
You can also retrieve your blog post from the command line by running
Deploying PM2 to run Strapi as-a-Service
Now you can access your Strapi admin interface, configure your app, create content and access it via the API. However, there is a problem: as soon as you close your terminal or disconnect from your Instance, your Strapi project will go offline. Your content and admin interface will no longer be available until you reconnect to your Instance and restart Strapi. To get around this, you can use PM2, a daemon process manager, to run Strapi as-a-Service and keep keep your Strapi project online 24/7, even when you are disconnected from your Instance.
If your Strapi app is still running in your terminal at this point, kill it with
On your Instance, use yarn to install PM2:yarn global add pm2
Next, you need to edit your
.bashrcfile to permit the use of global Yarn packages:
.bashrcfile with a text editor. Here, we use nano:nano ~/.bashrc
Add the following to the very end of the file and save the changes:export PATH="$PATH:$(yarn global bin)"
Now, to get that modification to the
.bashrcfile to take effect, type:source ~/.bashrc
Make sure you are in your Strapi app’s directory, and run the following command to launch Strapi as-a-Service with PM2. You can replace
my-strapi-projectwith your chosen name:pm2 start npm --name my-strapi-project -- run developNote:
run developpart of this command will launch your project in develop mode, which allows you to do certain actions not available in production mode, eg edit and create collection types. If you want to run in production mode however, replace
You should see an output like the following:[PM2] Starting /usr/bin/npm in fork_mode (1 instance)[PM2] Done.┌─────┬──────────────────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐│ id │ name │ namespace │ version │ mode │ pid │ uptime │ ↺ │ status │ cpu │ mem │ user │ watching │├─────┼──────────────────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤│ 0 │ my-strapi-project │ default │ N/A │ fork │ 25501 │ 0s │ 0 │ online │ 0% │ 28.4mb │ root │ disabled │└─────┴──────────────────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘
Now, even when you disconnect from your Instance, you will still be able to access your Strapi app’s admin dashboard and API.Note:
There are alternative ways to run your Strapi project with PM2, eg via an
ecosystem.config.jsfile. You can also use PM2 to start Strapi on boot. See the official PM2 documentation, or the Strapi Process Manager Documentation for more information on using PM2.
You now know how to deploy a simple Strapi app on a Scaleway Instance. Here, we’ve just seen the beginning of what you can do with Strapi. For more complex use cases, and more information on using the API, please visit the official Strapi documentation