How to deploy a wolkenkit application to digital ocean?

Currently I’m working on a project using wolkenkit (https://www.wolkenkit.io/).
Everything works fine locally on my machine (it comes with a docker container). Now I want to deploy it to digital ocean to go one step further.

In the official documentation there are a few lines about assigning a docker machine (https://docs.wolkenkit.io/1.0.1/reference/configuring-an-application/assigning-a-docker-machine/).

  • Why would a service that works locally be getting kill signals frequently in docker?
  • Docker - all-spark-notebook - Mounting local drive
  • Docker container data goes blank when mapped with host data directory
  • Why does bash script work depend on the size of the terminal window?
  • Docker ADD vs VOLUME
  • Can't install awscli to docker VM
  • Are there any guides/advices/tutorials addressing this topic in a more detail way suitable for digital ocean?

  • Docker container not able to ping my remote machine
  • artifactory oss docker 5.0.0 upgraded to 5.1.0 now it won't start
  • Matched between Docker container and Linux host?
  • LDAP-Server with official docker support
  • Eureka can not work with docker? What is different between eureka and consul?
  • Why does docker run -t keep the bash process from exiting and stopping the container
  • One Solution collect form web for “How to deploy a wolkenkit application to digital ocean?”

    Disclaimer: I am one of the developers of wolkenkit, so please take my answer with a grain of salt.

    Basically, it first depends on how you have created the machine: As you basically need a machine that runs Docker, the easiest way is to use docker-machine to set it up. For details on this see the Docker documentation.

    Once you have done this, you have two options of how to proceed:

    1. You can use the docker-machine env command to select the DigitalOcean machine is the currently active machine, and then run wolkenkit start as usual. Since the selected machine is stored within a number of environment variables such as DOCKER_HOST, the wolkenkit CLI tool uses these information to access the Docker host.

    2. The second option is to add a new environment to your wolkenkit application’s package.json file as described here. Generally, all you need to do is to provide the name of the docker-machine machine that you have created. In this case, the wolkenkit CLI will take care of configuring the connection automatically, so you don’t have to do this manually. You then start your application using wolkenkit start --env production, assuming that your environment is called production.

    The first approach works best if you don’t often change your machines. The second is best if you to work locally most of the times, and rarely deploy to the cloud. The latter approach also enables you to define multiple environments, such as production, staging, test, … and deploy to one or the other, depending on a command-line flag.

    Please note that you may also use the WOLKENKIT_ENV environment variable to define a default environment other than default (which is the CLI’s default value).

    Hope this helps 🙂

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.