Deploy an Application with Kontainers


This article demonstrates how to deploy a Ruby on Rails application with EYK. The process involves creating a Cluster, configuring the Dockerfile and Procfile in your project, and pushing your code from your repository to the remote EYK target. Your application will be available immediately and can be managed and scaled with the EYK Web Console.


  • Prior to pushing your code, you need to have the following items in place:
    • Cluster: To deploy an application, you need to have a Cluster to deploy it on. You can create multiple Clusters and each Cluster can run multiple applications. The steps for creating a Cluster are part of the solution below and can be skipped if you already have a Cluster configured.
    • Dockerfile: Your Dockerfile is a text file in the root of your project that contains the commands executed to assemble your image. EYK builds the container image for you when you push your code to the eyk remote target. You can create this file yourself, or generate it using the CLI 'eyk init' command.
    • Procfile: Your Procfile is a text file in the root of your project that declares named processes, or process types. Each line in the Procfile specifies the name of the process type followed by the specific command to run. EYK creates a group of containers for each process type which can be individually scaled and configured based on their role and requirements. The process type is an alphanumeric string. The ‘web’ process type is special as it is the only process type that will receive HTTP traffic from the EYK router. Other process types can be named arbitrarily. The ‘web’ process is used to run web applications such as a Ruby on Rails server. The ‘cmd’ process is used to execute non-web related processes, such as calling an asynchronous process. Each process will use the same container image defined in the Dockerfile of the project. You can create this file yourself, or generate it using the CLI 'eyk init' command.

Deploy an Application Step-by-Step

  1. Access the EYK Web Console with your Engine Yard account:
    • Navigate to: to login and access the EYK Web Console
  2. Create a Cluster for your Application:
    1. Click Clusters from the menu bar at the top

    2. Click the '+ Add Cluster' button to create a new Cluster
    1. Cluster Name: Assign a name to your cluster which will become part of the default application URL
    2. Region: Select the AWS Region where you want your Cluster to reside
    3. Organization: Most EYK users will have just one selection here. However, if you are a consultant who has done work for multiple Engine Yard customers, you may have more than one selection here and will need to select the appropriate Organization to associate the cluster with.
    4. Click the Create Cluster button to create your new Cluster
      You will be returned to the Applications page after creating your Cluster
  3. Login to EYK:
    • Enter: eyk ssologin eyk.<cluster-name>.<organization-name>
  4. Prepare your code for the push to EYK:
    • Enter: git clone <URL>
  5. Prepare your Dockerfile and Procfile: You can provide your own Dockerfile and Procfile, or follow these steps for the EYK CLI Tool to create them for you:
    1. Enter: eyk apps:init [-a --app=<app>] ruby-<Version>, for example, to deploy a Ruby 2.7 application, eyk apps:init ruby-2.7

      InformationEYK supports Ruby versions 2.0, 2.1, 2.2, 2.3, 2.4, 2.5, 2.6, and 2.7 

      The expected response is:
      The following files have been created, run git add to have them
      under version control:
      .eyk/config/secrets.yml.erb .eyk/migrations/ Also, relevant entries to run web, sidekiq, cronjobs, and db:migrate have been added to Procfile in a disabled form. In order to enable any of them, do uncomment the relevant line. And don't forget to commit files to version control!!!
    2. Structure your code: In addition to your typical Rails application structure, you will place the Dockerfile and Procfile in the root of your application, as in this example:
      ├── app
      ├── bin
      ├── config
      ├── db
      ├── doc
      ├── Dockerfile
      ├── Gemfile
      ├── lib
      ├── log
      ├── Procfile
      ├── public
      ├── Rakefile
      ├── script
      ├── test
      └── vendor
  6. Create your application in EYK:
    • Enter: eyk create <your-app-name>
  7. Use a git push to deploy your application to EYK:.
    • Enter: git push eyk <branch_name>
  8. Test your application: Validate that your application is up and running by connecting to your application’s URL. This command opens the application in your default browser.
    • Enter: eyk open

Adding Environment Variables with the EYK CLI Tool

You can set any environment variables that need to be engaged for your application’s runtime environment one of two ways, using the config:set command or by using the config:push command, which uses your local config file to build all environment variables into the instance at once. Environment Variables can also be configured in the EYK Web Console. For details, see the Configure Environment Variables with the Kontainers Web Console article.

  1. Configure individual Environment Variables
    1. Enter: eyk config:set <var_1_name>=<var_1_value> <var_2_name>=<var_2_value>--app=<app_name>
  • In the EYK CLI Use config:set Do this for each environment variable you need to set for your application.
  • OR Configure multiple Environment Variables from a file
    1. Create your configuration file as a text file with the extension .env, following this example:
    2. Enter: eyk config:push --app=<app_name> --path=<my_custom_path>
    3. Enter: eyk config:list --app=<app_name>
    • In the EYK CLI Use config:push Use this method when your environment variables contain sensitive information, such as passwords, or in cases where you have several environment variables that need to be set.
    • In the EYK CLI Check your Environment Variables: In order to verify all of the environment variables in your application’s environment, use the config:list command:

    Back to top

    Related Articles

    Back to top


    Article is closed for comments.