Multiple custom services


I’m new to drone and would like to try it out. But before I get into the nitty gritty of setup and what not I’d like to ask some questions.

  1. Can we run multiple services that are not common like Kong or even a custom written app and have it be fully configurable?
  2. What’s the difference between running this locally or getting enterprise?
  3. When running locally, how can you setup multiple workers? And does that mean builds will run faster?


Yes, drone will run any docker container as a service. It does not care what is running inside that container. If you are familiar with docker-compose, drone behaves similarly.

Sorry, I am not sure I understand what “locally” means in this context. We provide both a community edition and and enterprise edition of drone. You are responsible for hosting both versions on your own hardware. The enterprise edition is based on the community edition, but provides some extra features.

When you configure an agent, you provide it the server address. You can install agents on multiple server, and configure them to communicate with a central drone server. Having multiple agents does not make a build run faster per-se. Instead, having multiple agents allows you to process more builds concurrently. If you have too few agents, you will find that build jobs sit in queue, waiting for available agents.

Thanks @bradrydzewski!

On your note regarding enterprise and community, perhaps I should’ve asked the key difference for both.


On your note regarding enterprise and community, perhaps I should’ve asked the key difference for both.

The enterprise edition includes dedicated support via our private Slack channel and a number of extensions that are not available in the community edition. For a full list of extensions, please see the Enterprise Extensions section of the documentation

Please note the enterprise and community edition are distributed in the same official drone/drone docker image. If you provide the image with a license key it will unlock the enterprise feature. I therefore recommend you start with the community edition so that you can evaluate the product and ensure it meets your needs. You can then easily upgrade at a later time, simply by providing the key to your existing installation, if you decide you need these enterprise features.

@bradrydzewski awesome!

Yeah, I think I’ll try out the community version first. Is there a good guide how to go on about this? From setup to running a job?