Setting up the Vapor TIL app for Vapor Cloud 2 is fairly simple.
To get started on Vapor Cloud 2, setup a new account here.
After you have created your account, and signed in, you will see something like this:
!!! note During the Alpha, you will see various parts of the dashboard as "Under construction".
Git keys give you access to Vapor Cloud's private Git server. To setup git keys, you need to get the contents of your public SSH file. It's usually located at ~/.ssh/id_rsa.pub, but my vary.
To get the content you can run the following command:
cat ~/.ssh/id_rsa.pubAlternately on macOS you can get the content of the key directly on your clipboard:
pbcopy < ~/.ssh/id_rsa.pubIt's only one line. Copy the entire output.
Next, in the dashboard, navigate to the Settings page using the main menu. Then, click the + button in the SSH keys section.
Give your SSH key a recognizable name and paste the contents of the key. Then, click create.
!!! note This might take a few seconds to create.
After this you should be able to verify access by running.
ssh git@git.code.vapor.cloudThe output will look something like this:
PTY allocation request failed on channel 0
Hi jonas@vapor.codes, You've successfully authenticated to Vapor Cloud Git
R W night-long-14474
R W sun-ancient-43997
Connection to git.code.vapor.cloud closed.
For more info and troubleshooting, please see the Git basics page
Start by downloading the web.Dockerfile into your project. From the project folder, run the following command:
curl -O https://raw.githubusercontent.com/joscdk/vapor-til/master/web.Dockerfile
Then update your configure.swift like in this commit: https://github.com/joscdk/vapor-til/commit/9e36e77f65e0a913ac8c18ce24ad027a92112bd3
After this push the updates to the Vapor Cloud Git
git push cloud master
Next, we need to create a new application in Vapor Cloud to host our project. Go to the Applications page using the main menu, then click the + icon to create a new application.
For Name, let's let Vapor Cloud generate a unique name for our application by selecting Generated. Choose a plan and region to host your application in, then click create.
You can now see your application:
Click the "More" icon on the Git card, and view the instructions for configuring Git.
After you have pushed your code to Vapor Cloud's private git server, you can start the deployment. Click the Deploy button on the Git card. By default the deployment will use the environment's Default Branch (master). If you want to deploy another branch, you can select Custom Branch, or create a new environment.
When you start the deployment, you automatically get all output from the deploy, making debugging easy. The last part of the deploy is Launching. This will wait until the application is online. If booting the app fails, you will get the log output so you can see what failed.
To setup a database, go to the application page, and click the + create icon in the top right corner. And click Database
After that select Plan, Engine and Region
After creating the database, it's up and ready for being used.
!!! warning Your web replicas will reboot since it will add a config variable to the app. No deployment is necessary to update the config.
On the database card, you can see the TOKEN you can use in the database. You can also click the More button, and connection details, to see details giving you access to connect to the database from a Tool of your choice (CLI, GUI tool etc.)
Tokens are the one you connect to the database from your Vapor app. These are named like:
DB_<ENGINE> e.g. DB_POSTGRESQL if you have two databases of the same engine they will be named DB_POSTGRESQL and DB_POSTGRESQL2
After deploying your app for the first time, you must scale the application to one or more replicas to bring it online. Subsequent deployments will not require you to re-scale your application.
On the Replica card, click scale, and scale your app to 1.
After this you should be able to access your application on <app-slug>.v2.vapor.cloud
!!! note During Alpha apps will be available on v2.vapor.cloud we will be switching to vapor.cloud during Alpha
!!! note As we do have limited resources during Alpha, we advice you to keep your replicas small, if possible try to keep them at the free plan.
Free plans in Cloud 2 provides 64mb memory, which should be enough for most use cases.