Add guidance on how to deploy to Fly.io

For more info see #515

This is splitting out that PR into multiple parts. This is part 4 - Fly.io

org-cyf/content/guides/deployment/flyio/_index.md

@@ -0,0 +1,10 @@
+---
+emoji: 🚀
+title: Deploying to Fly.io
+description: Learn how to deploy your website to Fly.io
+weight: 8
+---
+
+[Fly.io](https://fly.io/) is a provider allowing you to deploy backend applications that are converted into docker containers. It also allows one to start up a small PostgreSQL database on their system. By making sure that the [frontend is served through the backend]({{< ref "/guides/deployment/flyio/serving-frontend" >}}) you can therefore easily deploy your entire stack on fly.io.
+
+The main drawback of fly.io that it's free trial only allows you to deploy exactly two systems. For a full stack application this would be the backend (which is also serving the frontend), and the database, meaning you would only be able to deploy a single project freely.

org-cyf/content/guides/deployment/flyio/database-access.md

@@ -0,0 +1,40 @@
+---
+emoji: 🚀
+title: Accessing fly.io databases
+description: Learn how you can access the fly.io PostgreSQL database
+weight: 3
+---
+
+## Accessing database
+
+If you have been following the setup guides you would have both a backend and a database system running under fly.io.
+
+Your database can hold data for multiple applications, so first you need to get a list of them:
+
+```bash
+flyctl postgres db list -a YOURNAME-PROJECTNAME-db
+```
+
+(Make sure you use your database's name after the `-a` that you have set up before)
+
+On the list you will find under the NAME column three values: `postgres`, `repmgr` and finally the name of your application's datastore. It will be something like `YOURNAME_PROJECTNAME` - same as your application name but all of the dashes are replaced with underscores.
+
+Take a note of this name as you will need it later.
+
+## Uploading database
+
+To connect to the database you will need to use `flyctl`:
+
+```bash
+flyctl postgres connect -a YOURNAME-PROJECTNAME-db -d YOURNAME_PROJECTNAME
+```
+
+Where the first value is the name of the database you set up in level 150, and the second value if the datastore name you obtained in the last section.
+
+The command above will start you up with a proper `psql` console where you can run commands.
+
+You can also pipe in SQL files. For example if you have an `initdb.sql` file containing SQL commands to initiate a database you can do:
+
+```bash
+flyctl postgres connect -a YOURNAME-PROJECTNAME-db -d YOURNAME_PROJECTNAME < initdb.sql
+```

org-cyf/content/guides/deployment/flyio/serving-frontend.md

@@ -0,0 +1,38 @@
+---
+emoji: 🚀
+title: Serving frontend from your backend
+description: Learn how to add support for serving frontend files to Express.JS backends
+weight: 2
+---
+
+Fly.io doesn't have a built-in CDN for serving static frontend files directly, so if you wish to deploy your frontend you need to do it through your backend.
+
+Express.JS has fortunately a built-in middleware just to do that. You only need to set the location of your frontend files, and it will take care of serving the contents for you.
+
+For example if you add the following middleware inside your `/server/app.js`:
+
+```js
+const staticDir = path.join(__dirname, "..", "static");
+app.use(express.static(staticDir));
+```
+
+Then anything under the `/static` directory will be served as-is.
+
+{{<note type="warning" title="TL;DR">}}
+Express.JS will not compile these files for you, so if you have Javascript files that need compilation, like React JSX files you need to do that separately.
+{{</note>}}
+
+If you have a React application and you wish it to support React Routes you also need to make sure that every request that doesn't correspond to a real file gets routed to your main website. You can do that with adding a code like the following:
+
+```js
+app.use((req, res, next) => {
+	if (req.method === "GET" && !req.url.startsWith("/api")) {
+		return res.sendFile(path.join(staticDir, "index.html"));
+	}
+	next();
+});
+```
+
+This will point any request that was not yet handled in a previous middleware, and are not starting with `/api` to your `index.html` allowing React Router to handle it internally.
+
+You can find a full `app.js` example showing static file serving [here](https://github.com/sztupy/Full-Stack-Project-Assessment/blob/main/server/app.js).

org-cyf/content/guides/deployment/flyio/setup/index.md

@@ -0,0 +1,144 @@
+---
+emoji: 🚀
+title: Setup
+description: Learn how to set up fly.io
+weight: 1
+---
+
+## Install `flyctl`
+
+Fly.io relies on a command line utility to launch and deploy applications. You need to download and install it. You can find installation instructions here: https://fly.io/docs/hands-on/install-flyctl/
+
+After installing you might need to close your terminal and reopen it to be able to access `flyctl`
+
+## Signing up
+
+To sign up for a fly.io account go to their sign up page at https://fly.io/app/sign-up Make sure you register using the "Sign up using GitHub", as otherwise you won't get added to the Trial package!
+
+![Sign up using GitHub](signup.png)
+
+Once signed up you need to log in locally. Type in the following on your terminal then follow the instructions:
+
+```
+flyctl auth login
+```
+
+## Application setup
+
+Once signed up you can now launch your application. Go to the root of your project and type
+
+```
+flyctl launch
+```
+
+Once you enter this command it will provide you with a prompt like the following:
+
+```
+We're about to launch your NodeJS app on Fly.io. Here's what you're getting:
+
+Organization: [email protected]        (fly launch defaults to the personal org)
+Name:         full-stack-project-assessment (derived from your directory name)
+Region:       Amsterdam, Netherlands        (this is the fastest region for you)
+App Machines: shared-cpu-1x, 1GB RAM        (most apps need about 1GB of RAM)
+Postgres:     <none>                        (not requested)
+Redis:        <none>                        (not requested)
+
+? Do you want to tweak these settings before proceeding? (y/N)
+```
+
+Make sure you enter `Y` on the prompt as the default settings are not going to use the free tier!
+
+Once you enter `Y` and press enter you will be redirected to a website where you need to fill in the details as follows:
+
+- Name: Use `YOURNAME-PROJECTNAME`, example `john-smith-videorec`
+- Region: Pick `lhr - London`.
+- VM size: Pick `shared-cpu-1x`. Anything else is not included in the free tier!
+- VM memory: Pick `256Mb`. Anything else is not included in the free tier!
+- Database: `Fly Postgres`
+- DB Name: `YOURNAME-PROJECTNAME-db`, example: `john-smith-videorec-db`
+- Configuration: `Development - Single Node`. Anything else here is not included in the free tier!
+- Redis: `None`
+
+Once you fill in the details click "Confirm Settings"
+
+This will set up your database and a machine for running your backend. If everything is successful you should get something like:
+
+```
+Now: run 'flyctl deploy' to deploy your Node app.
+```
+
+Once everything is in order you can see that new files have been added by `fly launch` to your repository. These include a `Dockerfile` and a fly settings file called `fly.toml`. Make sure you commit both into your git repository, they will be needed during further deployments!
+
+## Application deployment
+
+Finally you are now ready for deployment:
+
+```
+flyctl deploy
+```
+
+This command will send your current repository to fly, build a docker image of your code then deploy that image to the Fly.io infrastructure.
+
+Note: if you are on the Trial Tier the deployer will return an error message saying it could only deploy your app to one machine instead of two because of the Trial Tier limitations:
+
+```
+Creating a second machine to increase service availability
+
+Error: error creating a new machine: failed to launch VM: To create more than 1 machine per app please add a payment method.
+```
+
+This is okay, as one machine is enough for our deployment. Actually if you are not on the Trial Tier, then the deployer will create two machines. If you don't wish to pay for both then you can decrease them to a single one by using the following command:
+
+```
+flyctl scale count 1
+```
+
+If everything else goes well (as mentioned the error message above can be ignored) your application will be available on
+
+```
+https://YOURNAME-PROJECTNAME.fly.dev
+```
+
+Make sure to check that it works as expected!
+
+## Automated Deployments
+
+Note that fly.io doesn't have access to your GitHub account so it will not deploy your application whenever it changes. Either you need to run `fly deploy` from your computer every time you want to push a change, or you need to set up GitHub to do this for you.
+
+In order to do this there are two steps: You need to give GitHub access to your fly.io account, and then also need to set up a workflow that runs the deploy command every time you push changes to the `main` branch.
+
+For the first one you need to run the following command:
+
+```
+flyctl tokens create deploy -x 999999h
+```
+
+This will create a token that can be used by flyctl to run deployments. Make sure you save the result as you will need it later. It looks like a very-very long string starting with something like `FlyV1 fm2_lJPECAAAAAAAA...`.
+
+Next go to your GitHub repository on GitHub, and click Settings. On the left hand side scroll down to "Secrets and variables" and select "Actions". One the page that shows up scroll down to "Repository secrets", and click "New repository secret"
+
+Set the Name to `FLY_API_TOKEN` and the value to the full results of the previous call.
+
+Now you have given GitHub access to your fly.io account. You also need to let GitHub know that you want to run a deployment every time your `main` branch changes. First create a file called `.github/workflows/fly-deploy.yml`, with the following content:
+
+```yaml
+name: Fly Deploy
+on:
+  push:
+    branches:
+      - main
+
+jobs:
+  fly-deploy:
+    name: Deploy app
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+      - uses: superfly/flyctl-actions/setup-flyctl@master
+      - run: flyctl deploy --remote-only
+        env:
+          FLY_API_TOKEN: ${{ secrets.FLY_API_TOKEN }}
+```
+
+
+Once you commit this file and push it to your `main` branch, GitHub will automatically run `flyctl deploy` against whatever is in the `main` branch.