/symfony-boilerplate

An example of an application built with Symfony 5, GraphQL and Nuxt.js

Primary LanguagePHP

Caution: this is still work in progress.

Companies and products

Replace this title and the following description with your project name and description.

This project is an example of a web application built with Nuxt.js, Symfony 5, and GraphQL.

Setup

Prerequisites

Linux

Install the latest version of Docker and Docker Compose.

macOS

We strongly recommend installing Vagrant and VirtualBox.

Indeed, Docker currently has huge performance issues on macOS, and using Vagrant allows us to have an almost Linux-like experience regarding performances.

Windows

We strongly advise using a Linux-like terminal to run the Makefile commands. Vagrant might also be a solution regarding performances.

If not possible, you may also directly run the commands specified in the Makefile. For instance, instead of running make up, run docker-compose up -d.

macOS and Windows

Update your hosts file with the following entry:

127.0.0.1   *.localhost

On macOS, run sudo nano /etc/hosts to edit it.

On Windows, edit the file C:\Windows\System32\drivers\etc\hosts with administrative privileges.

If you're using Vagrant, check there is no application running on port 80 (like Apache or another virtual machine).

If OK, run make vagrant, then vagrant up, and finally vagrant ssh to connect to the virtual machine. From here, you'll be able to run all the next commands like Linux users!

Update the variable PROJECT_NAME from the Makefile with your project name. Only use alphanumeric characters (no spaces, distinguish words with _ or -).

Starting the Docker Compose stack

Copy the file .env.dist to a file named .env. For instance:

cp .env.dist .env

Edit the .env.dist by updating the default values of DOMAIN, MYSQL_DATABASE and APP_SECRET environment variables.

Next, make sure there is no application running on port 80 (Vagrant users can skip this check).

Vagrant users: the first time you start the Docker Compose stack, you have to "comment" the following environment variables from the api service in the docker-compose.yml file: STARTUP_COMMANDS_2, STARTUP_COMMAND_3, and STARTUP_COMMAND_4. Indeed, composer install fails miserably, but there is a workaround. See below.

Good? You may now start all the Docker containers with the following commands:

make up

It may take some time as each container will also set up itself, such as installing dependencies (PHP, JavaScript, etc.), compiling sources (JavaScript), or running migrations to set up the database structure.

In some cases, the api service will try to run the migrations before the mysql service is ready. If so, restart the api service with docker-compose up -d api.

The containers will be ready faster next time you run this command as the first run is doing most of the setup.

Vagrant users: enter the api service with make api. Here, run composer install --prefer-source (and prepare some coffee). When done, exit the container, uncomment the previous environments variables, and rerun make up.

Once everything is ready, the following endpoints should be available:

Update the domain with the one used in your project.

You may now enter the api service and load the development data:

make api
php bin/console app:fixtures:dev
exit

Last but not least, start the message consumer with:

make consume

What's next?

Configuring Git

It would be best if you ignored globally some folders like those generated by your IDE and Vagrant.

If not already done, you need to tell Git where to find your global .gitignore file.

For instance, on Linux/macOS/Windows git bash:

git config --global core.excludesfile '~/.gitignore'

Windows cmd:

git config --global core.excludesfile "%USERPROFILE%\.gitignore"

Windows PowerShell:

git config --global core.excludesfile "$Env:USERPROFILE\.gitignore"

Then create the global .gitignore file according to the location specified previously.

You may now edit it, according to your environment, with:

# IDE
.idea
.vscode
# MacOS
.DS_Store
# Vagrant
.vagrant

Documentations

Make sure you have read the following documentations:

Day-to-day guidelines

In-depth explanations

Don't hesitate to update these documentations but also add your documentations.

How to stop the stack?

As simple as the make up command, run make down to stop the entire Docker Compose stack.

If you're a Vagrant user, you may also stop the virtual machine with vagrant halt.

If you're not going to work on the project for a while, you may also destroy the virtual machine using vagrant destroy.

How to view the logs of the Docker containers?

All aggregated logs:

docker-compose logs -f

Logs of one service:

docker-compose logs -f SERVICE_NAME

For instance, if you want the logs of the api service:

docker-compose logs -f api