Using Flightdeck

Preparation

Before starting Flightdeck, you need to be sure that other local web development environments stuch as MAMP, WAMP, Acquia Dev Desktop, and even locally installed services such as Solr are stopped.

Flightdeck acquires many of the same ports as these products, and they cannot be used at the same time.

Stop MAMP, WAMP, Acquia Dev Desktop, and any local web server services using their perferred method.
Stop any existing Docker containers:
```
docker kill $(docker ps -q)
```

Starting

Once the proper files have been deployed and the .env file configured, you’re ready to start Flightdeck for the first time.

Navigate to the directory containing the docker-compose.yml file.
```
cd path/to/my_project
```
Start Flightdeck using the following command:
```
docker-compose up -d
```
Using a web browser, navigate to docker.test.

Using CLI tools

Flightdeck includes several CLI tools in the web container for your use. This includes Drush, Drupal Console, npm, sass, and others. This allows you to leverage these tools without installing them on your host OS.

To use the CLI tools:

Navigate to the directory containing the docker-compose.yml file.
```
cd path/to/my_project
```
Start Flightdeck if you haven’t already.
Start an interactive shell session into the web container:
```
docker-compose exec web /bin/bash
```
Use Drush or any of the included command line applications as needed.
When finished, leave the interactive session:
```
exit
```

Stopping

When your done with using Flightdeck, you can stop it as follows:

Navigate to the directory containing the docker-compose.yml file.
```
cd path/to/my_project
```
Stop Flightdeck:
```
docker-compose kill
```

DO NOT use the docker-compose down command!

The down command deletes the containers, which includes the database container and your loaded database. The kill command merely stops the containers, allowing you to pick up work where you left off.

Multiple Projects

Flightdeck is designed to run only one site codebase at a time. If you have multiple projects relying on Flightdeck you must shutdown Flightdeck for your current project before moving to the next one.

Remember, commands like docker-compose look at your current working directory to know which docker-compose.yml file to read.

Navigate to the directory of the project you’re finished using.
Stop Flightdeck as described above.
Change to the directory for the next project you’ll be working on.
Start Flightdeck as described above.

Loading Databases

Flightdeck provides two options to load databases, phpMyAdmin and a CLI method.

To use phpMyAdmin:

Using a web browser, navigate to http://docker.test:8001.
Select the database name in the left-hand sidebar.
Open the Import tab.
Follow on screen instructions to load the dump.

To use the CLI:

Place the dump file in the db-backups/ folder in your project directory.
Using the command line, navigate to the directory containing your docker-compose.yml:
```
cd path/to/my_project
```
Open an interactive shell to the db container:
```
docker-compose exec db /bin/bash
```
If the dump is uncompressed (*.sql) use the following command to load it:
```
mysql -C yourDatabaseName < /tmp/name_of_dump.sql
```

If the dump is compressed, use one of the following commands:

zcat /tmp/name_of_dump.sql.gz | mysql -C yourDatabaseName       # gzip
xzcat /tmp/name_of_dump.sql.lzo | mysql -C yourDatabaseName     # xs
lzopcat /tmp/name_of_dump.sql.lzo | mysql -C yourDatabaseName   # LZO

Updating Flightdeck

Like any set of Docker containers, you can update Flightdeck to the most recent version by pulling the new image from Docker Hub:

Using the command line, navigate to the directory containing your docker-compose.yml:
```
cd path/to/my_project
```
Stop Flightdeck.
Enter the following command to update the containers:
```
docker-compose pull
```
When finished, you can start the containers as normal.

The above will update all instances of Flightdeck on your system, so use with caution.

Making commands shorter

Many of the commands involved in using Flightdeck (and Docker in general) can be very long and annoying to type in. For that reason, you can use shell aliases to create shorter versions of the commands.

On macOS and Linux:

Using a text editor of your choice, edit the .bashrc, or .bash_profile file in your home directory.

Add the following at the end of the file:

alias docup='docker-compose pull && docker-compose up -d && docker-compose exec web /bin/bash'
alias docweb='docker-compose exec web /bin/bash'
alias docdb='docker-compose exec db /bin/bash'
alias dockill='docker-compose kill'

Save the file.

Once saved you can use the alias in place of the longer command. To update, start, and open an interactive shell, use docup:

cd path/to/my_project
docup