1. View Tsuru Dashboard
After receiving your Tsuru login credentials from the help desk, sign into your private Tsuru Dashboard. You'll only see one app defined - the Dashboard app - which itself runs on Tsuru. In the top-right corner, notice the settings icon. There, you can change your password and upload your public SSH key (if you are deploying via git).

2. Install the CLI
Next, install the Tsuru CLI (aka command line interface) on your local machine to allow you to remotely interact with your Tsuru.


brew tap tsuru/homebrew-tsuru
brew install tsuru --devel

For other operating systems, download directly from the repository's releases page.

3. Login with the CLI
Configure your Tsuru CLI to point to your Tsuru Dashboard server. The values in <...> were supplied to you via the help desk ticket.

tsuru target-add default https://<tsuru-api-address>:8080 --set-current
tsuru login <tsuru-login-info>

Having problems on this step? If you cannot connect, check your login credentials. If you still cannot connect, perhaps your whitelisted IP address has changed. Create a new help desk ticket for assistance.

4. Preparing your app for deployment

Tsuru supports three different deployment approaches: using git push, deploying from a local directory, or deploying an existing Docker image. See this page for more details.

Depending on which deployment approach you choose, you will need to enable a specific "platform" in Tsuru. To see the current list of installed platforms, do tsuru platform-list. If you are trying to emulate a Heroku / Dokku deployment approach, use the "buildpack" platform. For all other deployment approaches, you might need to install another platform as described here.

Instead of embedding production settings in your code, you can use environment variables. More info here.

To tell Tsuru how to run your application after it is deployed, you'll need to define a Procfile. More info here.

Depending on your deployment strategy, you might want to run specific actions after your application is compiled but before it is running. For example, compiling assets, migrating a database, notifying a Slack webhook. These actions can be enabled using a custom tsuru.yml file. More info here.

5. Post-deployment tasks

To view your application's details, deployment status, and URL, do:

tsuru app-info -a <my app name>

To view application logs, do:

tsuru app-log -a <my app name>

See logging reference for additional commands.

6. Additional tasks

Register an SSL certificate by running this command. Users will be automatically redirected to HTTPS for every request. If you'd like to configure a free certificate from LetsEncrypt.org, please create a help desk ticket.

Add a domain name with this command. Don't forget to update your third-party DNS service to point your domain name to your HCB server. You'll need to create a CNAME record set to <app name>.<machine id>.healthcareblocks.com.

Create teams, add team members, and manage permissions.