Deploy Quarkus


If you have been customizing your existing project as you go, now is the time to ensure all code is committed to Git and to run git push to to your production branch. then builds your code, producing a read-only image of your application, and deploys it into a running cluster of containers.

You can view the process in the console or, if you aren't using a source integration, in your terminal after pushing. When the process is done, click the URL to see your site.

Data migration 

If you are moving an existing site to, then in addition to code you also need to migrate your data. That means your database and your files.

Importing the database 

First, obtain a database dump from your current site. If you are using MySQL/MariaDB, then the mysqldump command is all you need. Save your dump file as database.sql. (Or any name, really, as long as it’s the same as you use below.)

Next, import the database into your site. The easiest way to do so is with the CLI.

platform sql -e production < database.sql

That connects to the database service on the production environment, through an SSH tunnel, and runs the SQL import.

Importing files 

You first need to download your files from your current hosting environment, whatever that is. The easiest way is likely with rsync, but consult your old host’s documentation. This guide assumes that you have already downloaded all of your user files to your local files/user directory and your public files to files/public , but adjust accordingly for their actual locations.

The platform mount:upload command provides a straightforward way to upload an entire directory to your site at once. Under the hood, it uses an SSH tunnel and rsync, so it’s as efficient as possible. (There is also a platform mount:download command you can use to download files later.) Run the following from your local Git repository root (modifying the --source path if needed and setting <BRANCH_NAME> to the branch you are using).

$ platform mount:upload -e <BRANCH_NAME> --mount src/main/resources/files/user --source ./files/user
$ platform mount:upload -e <BRANCH_NAME> --mount src/main/resources/files/public --source ./files/public

Note that rsync is picky about its trailing slashes, so be sure to include those.

Your files and database are now loaded onto your production environment. When you make a new branch environment off of it, all of your data is fully cloned to that new environment so you can test with your complete dataset without impacting production.

Go forth and Deploy (even on Friday)!