View Source Deploy to Fly.io

Once you have a Beacon site up and running locally, you can deploy it on Fly.io by following this guide.

Fly.io CLI

First, install the fly cli tool, as described at Install flyctl. You'll need it to deploy your site.

Sign in or sign up

Don't have an account yet? Sign up by running:

fly auth signup
copy

Or sign in to your existing account:

fly auth login
copy

Dockerfile

Fly applications run in containers. Let's generate a Dockerfile and make a couple of changes:

Run:

mix phx.gen.release --docker
copy

Edit the generated Dockerfile and make some changes:

1. Install npm by adding it into the apt-get install list:

It should look like this:

RUN apt-get update -y && apt-get install -y build-essential git npm \ # <-- add npm herecopy

2. Add the following code before RUN mix assets.deploy:

RUN mix tailwind.install --no-assets
RUN npm install --prefix assetscopy

3. Add the following code before USER nobody:

# Copy the tailwind-cli binary used to compile stylesheets for pages
RUN mkdir -p ./bin/_build
COPY --from=builder --chown=nobody:root /app/_build/tailwind-* ./bin/_build/copy

Launch

With your account in place and all files updated, it's time to launch your application. Run:

fly launch
copy

When asked if you would like to set up a PostgreSQL database, answer YES and choose the most appropriate configuration for your site.

When asked if you would like to deploy, answer YES or run fly deploy afterwards when you're ready to deploy.

Deploy

Beacon is designed to minimize deployments as much as possible, but eventually you can trigger new deployments by running:

fly deploy
copy

Open

Finally, if you followed the guides to setup your site, run the following command to see it live:

fly open /
copy

If you have created a custom page, simply replace / in the above command to match its path

More commands

You can find all available commands in the Fly.io docs and also find more tips on the official Phoenix Deploying on Fly.io guide.

Troubleshooting

The default config file created by fly launch defines min_machines_running = 0 so Fly will auto stop machines that receive no traffic for a period of time. You might want to change this value to 1 otherwise it will look like your app is not working, when in fact it's just Fly proxy doing its job.