Deployment with Fly.io¶

Follow these steps to deploy your application using Fly.io:

Install the Fly CLI.

Attention

Either

copy the deploy/fly.toml file to your project root directory
or append -c deploy/fly.toml to every fly command.

Change your app name in the fly.toml file to something unique, e.g. your-unique-app to avoid conflicts with other people using the same name.
Initialize your Fly.io app:
```
fly launch --no-deploy --ha=false --copy-config
```
This creates a new app on Fly.io without deploying it yet. The --ha=false flag disables high availability mode, otherwise two machines are started. When going through the setup process, answer no to all question by pressing Enter.
Import your environment variables. It is best to define a production .env.prod file, where all production related variables are set, including DEBUG=FALSE. This way you you have a clean separation between local development and production deployment.
```
fly secrets import < .env.prod
```
This command imports all variables from your .env.prod file as secrets in Fly.io.
Verify your secrets:
```
fly secrets list
```
This lists all the secrets set for your Fly.io app.
If you want to access your site using the fly.io domain, make sure to add the domain to ALLOWED_HOSTS (or simply change the DOMAIN variable to the fly.io domain). If not, follow the instructions in the Custom domain section.
config/settings.py
```
ALLOWED_HOSTS = [DOMAIN, 'your-unique-app.fly.dev']
CSRF_TRUSTED_ORIGINS = [DOMAIN_URL, 'https://your-unique-app.fly.dev']
```
Deploy your application:
```
fly deploy
```
This command builds and deploys your application to Fly.io based on the fly.toml file.

After completing these steps, your application should be live on Fly.io. You can access it using the URL provided by Fly.io in the terminal after deployment, or you can run fly open to open the app in your browser.

Note

If you want to deploy to a different region, change the primary_region in the fly.toml file, e.g. to dfw for Dallas, Texas (US).

Custom domain¶

To use a custom domain, you need to have a domain name and point it to the Fly.io domain.

Create a CNAME record in your DNS settings of your domain name:

Type Name Content

CNAME @ your-unique-app.fly.dev
Create a certificate for your domain name:
```
fly certs add yourdomain.com
```
The cli will tell you to create a CNAME record that looks something like this:

Type Name Content

CNAME _acme-challenge.yourdomain.com yourdomain.com.y1yzi5.flydns.net.

Info

If you are using clouflare, do not proxy the _acme-challenge record, otherwise the certificate will not be issued.
Wait for the certificate to be issued. You can check the status with:
```
fly certs show yourdomain.com
```
Look for the Issued row. It should say true.
Done.

Continuous Deployment¶

DjipFast comes with a GitHub Actions worfklow to automate the deployment of your app.

The workflow is defined in .github/workflows/fly-deploy.yml. It expects a FLY_API_TOKEN to be set in the GitHub Actions environment.

Push your code to a private GitHub repository, if not already done.
To create your FLY_API_TOKEN, run the following command in the terminal:
```
fly tokens create deploy -x 999999h
```
Copy the output, including the FlyV1 and space at the beginning.
Go to your newly-created repository on GitHub and select Settings.
Under Secrets and variables, select Actions, and then create a new repository secret called FLY_API_TOKEN with the value of the token from step 2.
Done.

This workflow is triggered on every push to the main branch. It can also be triggered manually by going to Actions, clicking Fly Deploy, and then Run workflow.

It builds the CSS, installs the dependencies and deploys the app to Fly.io.