Yet another development stack? Seriously?

Cloudogu is not just another software development stack - it is an open platform, which lets you choose how and where your team creates great software. Each service or tool is delivered as a Dōgu, a Docker container, that can be easily integrated in your environment just by pulling it from our registry. We have a growing number of ready-to-use Dōgus, e.g. SCM-Manager, Jenkins, Nexus, SonarQube, Redmine and many more. Every Dōgu can be tailored to your specific needs. You can even bring along your own Dōgus! Take advantage of a central authentication service, a dynamic navigation, that lets you easily switch between the web UIs and a smart configuration magic, which automatically detects and responds to dependencies between Dōgus. Cloudogu is open source and it runs either on-premise or in the cloud. So, what are you waiting for?

Like what you see here? Get Cloudogu on Github and start developing now.

Quick start

Setting up a running Cloudogu EcoSystem is easy and takes just a couple of minutes. At the moment the software is in a public beta phase and it is strongly recommended NOT to use it in a production environment. The software comes as a Vagrant box for playing around with the features and contributing to the development. Because it is a virtual machine it runs on Linux, Windows and MacOS.

  • Step 1: Install Vagrant, Virtualbox and Git on your machine.
  • Step 2: Open a terminal (or command prompt) and clone the ecosystem repository:
      $ git clone
  • Step 3: Start the Vagrant box:
      $ cd ecosystem
      $ vagrant up
  • Step 4: Choose your network interface by entering the corresponding number from the list (internet connection is mandatory), e.g.:
      $ ==> default: Available bridged network interfaces:
      $ 1) en0: WLAN (AirPort)
      $ 2) en4: Thunderbolt-Ethernet
      $ ==> default: When choosing an interface, it is usually the one that is
      $ ==> default: being used to connect to the internet.
      $ default: Which interface should the network bridge to? 1
  • Step 5: After the first part of the setup has finished, copy the setup URL from the console output and paste it to your browser's address bar. You find this URL in the second last line of the log messages, e.g.:
      ==> default: the setup daemon has started and can be accessed at
      ==> default: The setup runs in background and writes its logs to /var/log/upstart/ces-setup.log
  • Step 6: The second part of the setup will guide you through an intuitive setup wizard. Fill in any required fields and finish the setup wizard in your browser. It is recommended to install the Dōgu User Management and at least one of the Dōgus SCM-Manager, Redmine, Jenkins, SonarQube or Cockpit.
  • Step 6b (optional): It can take some time until the system is available, even if the setup wizard says it has finished. Calling the ecosystem URL may result in error messages like "502 Bad gateway". This is a normal behaviour and is caused by docker containers which are still starting. Just wait a few minutes and try again. You can watch the activities of the starting containers in the logs:
      $ vagrant ssh
      Welcome to Ubuntu 14.04.4 LTS (GNU/Linux 4.2.0-27-generic x86_64)
       * Documentation:
      Development Environment
      vagrant@ces:~$ sudo -s
      root@ces:~$ tail -f /var/log/upstart/ces-setup.log
    or alternatively /var/log/upstart/ces-<container name>.log for each container.
  • Step 7: Login with the admin user you created during setup and have fun with Cloudogu EcoSystem! A good starting point is the User Management. Create a new user and give him the role "universalAdmin". Then logout and login again with your new user and start exploring the features of the system.