Go

Create a Clever Cloud account

The API of Clever Cloud uses OAuth 1 to perform authentication actions. There are two ways to signup to Clever Cloud: email or GitHub login.

Go to the Clever Cloud Console and select the method you prefer.

Email Authentication

This kind of auth requires a valid and non-temporary disposable e-mail, and a password having at least 6 characters. Do not forget to validate your email by clicking the link you will receive.

GitHub Authentication

The GitHub signup allows you to create an account or link your existing one to GitHub, in one click. This process asks the following permissions: 

• Read your Public Key
• Read User Repositories

The “repository permission” is used to deploy your GitHub apps directly to Clever Cloud, with a simple step.

If you need to give access to Clever Cloud’s API to a specific GitHub organization, you can do it here.

Two Factor Authentication (2FA)

Clever Cloud supports 2FA. You can enable it here: https://console.clever-cloud.com/users/me/authentication

Please, backup your recovery codes, we won’t be able to restore access to your account if you lose access to your regular codes.

You need to add a SSH key to your Clever Cloud’s account to deploy via Git. SSH keys are used to establish a secure connection between your computer and Clever Cloud. A user can have multiple SSH keys.

I need to create my SSH key

1. In your Terminal, enter the following bash line:

   ssh-keygen -t ed25519 -C "your_email@youremail.com"
   

   This command creates a new ssh key using the provided email, so that the owner of the key can be identified.

2. When prompted in which file you want to save the key, just press enter. If it says that the file already exists, enter n for no. Type ls, verify the presence of the file and jump to Add your SSH key on Clever Cloud.

3. When asked, enter a passphrase:

Generating public/private ed25519 key pair.
Enter file in which to save the key (/your_home_path/.ssh/id_ed25519):
# Now you should enter a passphrase.
Enter passphrase (empty for no passphrase): [Type a passphrase]
Enter same passphrase again: [Type passphrase again]

Which should give you something like this:

Your identification has been saved in /your_home_path/.ssh/id_ed25519.
Your public key has been saved in /your_home_path/.ssh/id_ed25519.pub.
The key fingerprint is:
01:0e:e5:2d:ab:98:d6:17:a1:6d:f0:68:9f:d0:a2:db your_email@youremail.com

I created my account with GitHub

If your account is linked to GitHub, a panel with your GitHub SSH keys will appear in the “SSH Keys” tab. You can add any key already present in your GitHub account by clicking on the import button next to it.

Add your SSH key on Clever Cloud

Public SSH Key

To declare your public SSH Key on Clever Cloud, in the left navigation bar, go in “Profile” and in the “SSH Keys” tab, add the key by entering a name and the public SSH key. The key is the entire content of the **id_[ed25519/rsa].pub** file including the id_ed25519/ssh-rsa part and your email.

Private SSH Key

If you want to clone a repository from a private repository, you can add a Private SSH Key to an application by creating a folder clevercloud at the root of your application and creating the file clevercloud/ssh.json with the following content:

{
    "privateKeyFile": "path/to/file"
}

Of course you need to provide a valid path to a file that contains a valid key and that you will push on the Clever Cloud git remote.

If you have trouble configuring this key you can refer to this extended documentation

Create an application on Clever Cloud

via the web console

1. Create a new app by clicking on the Add an Application button, in the sidebar.
2. Select a brand new instance (or a repository from GitHub if your account is linked).
3. Then select Go in the platform list.
4. Configure your scaling options.
5. Enter your application’s name and description and click “Next”. You can also select the region you want (North America or Europe).

Refer to the getting started for more details on application creation via the console.

via the Clever Tools CLI

1. Make sure you have clever-tools installed locally. Report to the getting started.
2. In your code folder, do clever create --type <type> <app-name> --region <zone> --org <org> where type is the type of technology you rely on, app-name the name you want for your application, zone deployment zone (par for Paris and mtl for Montreal), and org the organization ID the application will be created under.

Refer to the documentation for more details on application creation with Clever Tools.

Setting up environment variables on Clever Cloud

With the Clever Cloud console

1. Go to the Clever Cloud console, and find the app you want to fine tune under it’s organization.
2. Find the Environment variables menu and select it.
3. In this menu, you will see a form with VARIABLE_NAME and variable value fields. Fill them with the desired values then select Create.

With the Clever Tools CLI

1. Make sure you have clever-tools installed locally. Report to the getting started
2. In your code folder, do clever env set <variable-name> <variable-value>

Refer to environment variables reference for more details on available environment variables on Clever Cloud. You can of course create custom ones with the interface we just demonstrated, they will be available for your application.

Configure your Go application

Mandatory configuration

Be sure that:

• your application listens to the wild network 0.0.0.0, not only localhost or 127.0.0.1
• your application listens on port 8080
• put your main code in a file named main.go (If you do not do that, Go will generate a library and not an executable)

Apart from listening on port 8080, there is nothing to change on your application.

Go production build on Clever Cloud

• We automatically build and run your application, see Build the application.

• By default, we consider that your repository contains a single application. We put your application in ${GOPATH}/src/{app_id} and then run go get {app_id}. Refer to clevercloud/go.json settings if you want to override this behaviour.

• By default, we deploy your application as a Go project named “<app_id>”. You can find the app_id of your application under the environment variable APP_ID. Please refer to environment injection to know how to query it in your application.

• The executable is run with the application’s root as its current path. So if your application has a static folder at its root, it will be accessible via ./static in your application.

Build the application

To build your application, you can use one of the three methods available:

• go modules
• go build
• go get (default)

Go modules

If your project is compatible with go modules, be sure that the go.mod file is in your git tree. Note that it must be at the root of your application (see the APP_FOLDER environment variable if it isn’t

For now, you have to add the environment variable CC_GO_BUILD_TOOL=gomod to build using the go modules. In a future release, we will automatically build with go modules if the go.mod file is present at the root of your git tree.

Your project’s entrypoint should be in the same folder as the go.mod file and be named main.go. If it isn’t, you have to specify it using the following environment variable: CC_GO_PKG=./path/to/entrypoint.go

Go build

If your project does not support go modules, it may include your vendored dependencies. In this case, go build must be used.

To use go build, you have to set the CC_GO_BUILD_TOOL=gobuild environment variable. We will then deploy your project in a classic GOPATH hierarchy using go build.

The CC_GO_PKG environment variable can be used to define the main file of your application. Defaults to main.go.

Go get

• If your application has submodules and imports them with their full path or your main project is an external package hosted, for instance on GitHub (like GitHub.com/me/myproject), you can define the environment variable CC_GO_PKG=GitHub.com/me/myproject. We will now run go get ${CC_GO_PKG} instead of go get <app_id>.

Also, go get requires that you put your main code in a file named main.go. If you do not do that, go will generate a library and not an executable. So if you get a Nothing listening on port 8080, please check that your main file is named main.go.

You can also force the use of go get by setting the environment variable CC_GO_BUILD_TOOL=goget. This is currently the default.

Note: if you get a Nothing listening on port 8080 error, please check that your main file is named main.go.

Customize build using environment variables

clevercloud/go.json optional configuration

If you want to configure precisely your dependencies (e.g. have private libraries, or specific versions of some libraries), here is the way:

1. Make your repository have a GOPATH structure:

./
   src/
      myapp/
      foo/
         module1/
         module2/
      module3/

Here you have the modules myapp, foo/module1, foo/module2 and module3.

2. Create a clevercloud/go.json file at the top of your repository:

./
   clevercloud/
      go.json
   src/
      myapp/
      ...

3. In the go.json file, put the following:

{
    "deploy": {
        "appIsGoPath": true,
        "main": "myapp"
    }
}

If appIsGoPath is present and equals true, then we consider that your repo root is the GOPATH. the main field then becomes mandatory and must be the name of the module you want to run. e.g. if you want to run module1, main must be foo/module1.

4. (Optional) Add a “execDir” field to the “deploy” object:

{
    "deploy": {
        "appIsGoPath": true,
        "main": "myapp"
        "execDir": "src/myapp"
    }
}

The execDir value must be relative to the root of your repo. In the example above, we will run the application in the src/myapp directory.

Environment injection

Clever Cloud injects environment variables from your application settings as mentioned in setting up environment variables and is also injecting in your application production environment, those from your linked add-ons.

To access environment variables from your code, just get them from the environment with PATH: os.Getenv("MY_VARIABLE").

Git Deployment on Clever Cloud

You need git on your computer to deploy via this tool. Here is the official website of Git to get more information: git-scm.com

Setting up your remotes

1. The “Information” page of your app gives you your git deployment URL. It looks like this: git+ssh://git@push.clever-cloud.com/<your_app_id>.git. Copy it in your clipboard.

2. Locally, under your code folder, type in git init to set up a new git repository or skip this step if you already have one.

3. Add the deploy URL with git remote add <name> <your-git-deployment-url>.

4. Add your files via git add <files path> and commit them via git commit -m <your commit message>.

5. Now push your application on Clever Cloud with git push <name> master

Refer to the quickstart for more details on git deployments.

Linking a database or any other add-on to your application

By linking an application to an add-on, the application has the add-on environment variables in its own environment by default.

On add-on creation

Many add-ons do exist on Clever Cloud, please refer to the full list and check add-ons dedicated pages for full instructions.

During add-on creation, you will see Applications screen, with a list of your applications. You can toggle the button to Link and click next. If you finish the process of add-on creation, the application will automatically be linked to it.

Add-on already exists

In the Clever Cloud console, under the Service Dependencies menu of your application, you can use the Link addons dropdown menu to select the name of the add-on you want to link and use the add button to finish the process.

You can also link another application from the same page in the Clever Cloud console, using the Link applications dropdown menu.

More configuration

Need more configuration? To run a script at the end of your deployment? To add your private SSH key to access private dependencies? Go check the Common configuration page.

You may want to have an advanced usage of your application, in which case we recommend you to read the Administrate documentation section.

If you can’t find something or have a specific need like using a non supported version of a particular software, please reach out to the support.