Contained in this repository is an empty Strapi + Nuxt.js starter kit, setup with the following:

• Strapi.js Backend
• Strapi.js GraphQL
• Postgres
• Nuxt.js Frontend SPA
• Nust.js + SCSS/SASS
• Traefik Edge Router
• Docker Deployment

There is no default model for Strapi. This was branched from strapi-nuxt-blog-starter-kit when I realized I needed more flexibility in making small side projects.

Make sure that node is installed on your system. I built this using version 12.16.1.

Then run:

cd scripts && chmod +x setup.sh && ./setup.sh

This file only needs to be run once.

The setup.sh script creates a .env file that you can edit. .gitignore is setup so that this file is not checked into your repository.

Now edit the .env file so that all the variables are what you desire. I recommend only changing the obvious things, like passwords, secrets. etc.

Recommend installing Postgres locally and not running the entire docker compose locally. The reason is that you will have much better development speeding without using Docker on your local machine. This, however, is your preference.

You will need to log into your Postgres instance and create the database that you specified in your .env file in the POSTGRES_DB variable.

psql -U postgres -c 'create database myblog;'

For more information if you get stuck, see here.

NOTE: you do not need to do this when deploying the Docker containers because the postgres imagedoes this automatically from the .env. You only need to run this locally.

Note: You might be interested in editing the default name in your backend/package.json.

By default, Strapi.js loads its configuration from the .env file. If you need to customize things take a look at the backend/config/ folder.

To start the server with debugging enabled on port 9229:

cd backend
yarn debug

If this works, your browser will open to http://localhost:1337/admin/auth/register.

You can create your first user and log into the Strapi Admin section here, where you can see your blogs default models :D

Note: You might be interested in editing the default name in your frontend/package.json.

While the backend is still running, go ahead and start the frontend in a new terminal:

cd frontend
yarn dev

Then navigate to http://localhost:3000/.

You will get an error that says Cannot read property 'filter' of undefined (or something similar).

If you check the Developer Tools -> Network panel and refresh, you will see that all the GraphQL calls are returning content that will have an error Forbidden. The reason for this is that permissions for access to the models are configured within the Postgres database and we have not done that yet.

For more information on how stuff works, setting more things up, etc. you can check out my blog series on setting up this blog at Building this Blog w/ Strapi JS.

NOTE: By default the repo is setup to hit AWS S3 buckets for saving images. To remove this, you can remove (or change) the block of code in backend/config/plugins.js. If you remove this block of code, it will save files to local.

For more information on hitting S3 for image / media saving:

1. First see the Strapi File Upload Instructions
2. Install the Strapi S3 Upload Plugin
3. Set IMAGE_BASE_URI= (empty) in your .env file (the S3 urls already have a domain)
4. Completely restart your local Strapi.js develop

Your setup is probably going to be super custom. For example you might be using Bitbucket Pipelines or Intertube Packets. Whatever your technology, the following setup is assuming you are doing a really unsophisticated deploy from local without a proper CI/CD setup. Clearly this not not ideal for a longer term setup, but I don't really have time to write out a giant README on setting up CI/CD so just use this as a reference.

Important! Everything that follows assumes you have a working knowledge of Docker, DSN A and CNAME records, shell scripts, and SSH.

• Make sure that your .env file has all appropriate settings
• Make sure that you have a docker repository. I recommend making a free one at Docker Hub.
• Make sure you have proper A and CNAME records in your DNS settings for your domain name. You will need CNAME records for SITE_DOMAIN, www.SITE_DOMAIN, SITE_API_DOMAIN, and TRAEFIK_DASHBOARD_DOMAIN. See .env file for what you have chosen.
• Make sure you have a server with at least 2 GB of RAM and 8 GB of free disk space and SSH access. You might be able to run more lean, but I would not recommend it.
• Install Docker on your server (if not already installed)
• Install Docker Compose on your server (if not already installed)
• Make sure your server is running rsync
• Make sure that nothing on the server is running on the ports you have chosen in your .env
• Make sure you can actually SSH into your server easily (best bet is to add your public ssh key into the ~/.ssh/authorized_keys of the server)
• IMPORTANT! Verify with something like https://dnschecker.org/ that your CNAME records have propagated and are pointing to the right IP address. The reason for this is that Traefik uses LetsEncrypt to create your https certificates. If your CNAME records have not propagated, LetsEncrypt cannot verify that you own the domain and Traefik will fail when starting your containers.

You will need to edit the traefik/traefik.toml file. Make sure the domain names are correct in the [acme] section according to your .env file and the CNAME records you have created.

From the root folder:

./scripts/build-all.sh

source .env
docker push $DOCKER_EXTERNAL_REPO/$DOCKER_BACKEND_IMAGE:latest && docker push $DOCKER_EXTERNAL_REPO/$DOCKER_FRONTEND_IMAGE:latest

./scripts/deploy-to-production.sh

There are probably a lot of things that can be improved, feel free to make a fork and a PR!