cli | ||
client | ||
debian/drone | ||
plugin | ||
server | ||
shared | ||
.dockerignore | ||
.drone.yml | ||
.gitignore | ||
AUTHORS | ||
Dockerfile | ||
LICENSE | ||
Makefile | ||
README.md | ||
Vagrantfile |
System Requirements
- Docker
- AUFS
We highly recommend running Docker with the AUFS storage driver. You can verify Docker is using
the AUFS storage driver with the following command sudo docker info | grep Driver:
Installation
We have optimized the installation process for Ubuntu since that is what we test with internally. You can run the following commands to quickly download an install Drone on an Ubuntu machine.
wget downloads.drone.io/exp/drone.deb
sudo dpkg -i drone.deb
Database
By default, Drone will create a SQLite database. Drone also supports Postgres and MySQL databases. You can customize the database settings using the configuration options described in the Setup section.
Below are some example configurations that you can use as reference:
# to use postgres
[datasource]
driver="postgres"
source="host=172.17.0.2 user=postgres dbname=drone sslmode=disable"
# to use mysql
[datasource]
driver="mysql"
source="root@tcp(172.17.0.2:3306)/drone"
Setup
We are in the process of moving configuration out of the UI and into configuration files and/or environment variables (your choice which). If you prefer configuration files you can provide Drone with the path to your configuration file:
./drone --config=/path/to/drone.conf
The configuration file is in TOML format:
[server]
port=""
[server.ssl]
key=""
cert=""
[database]
driver=""
source=""
[registration]
open=true
[github]
client=""
secret=""
[github_enterprise]
client=""
secret=""
api=""
url=""
private_mode=false
[bitbucket]
client=""
secret=""
[gitlab]
url=""
[smtp]
host=""
port=""
from=""
user=""
pass=""
[worker]
nodes=[
"unix:///var/run/docker.sock",
"unix:///var/run/docker.sock"
]
Or you can use environment variables
# custom database settings
export DRONE_SERVER_PORT=""
export DRONE_SERVER_SSL_KEY=""
export DRONE_SERVER_SSL_CERT=""
# custom database settings
export DRONE_DATABASE_DRIVER=""
export DRONE_DATABASE_SOURCE=""
# enable users to self-register
export DRONE_REGISTRATION_OPEN=false
# github configuration
export DRONE_GITHUB_CLIENT=""
export DRONE_GITHUB_SECRET=""
# github enterprise configuration
export DRONE_GITHUB_ENTERPRISE_CLIENT=""
export DRONE_GITHUB_ENTERPRISE_SECRET=""
export DRONE_GITHUB_ENTERPRISE_API=""
export DRONE_GITHUB_ENTERPRISE_URL=""
export DRONE_GITHUB_ENTERPRISE_PRIVATE_MODE=false
# bitbucket configuration
export DRONE_BITBUCKET_CLIENT=""
export DRONE_BITBUCKET_SECRET=""
# gitlab configuration
export DRONE_GITLAB_URL=""
# email configuration
export DRONE_SMTP_HOST=""
export DRONE_SMTP_PORT=""
export DRONE_SMTP_FROM=""
export DRONE_SMTP_USER=""
export DRONE_SMTP_PASS=""
# worker nodes
# these are optional. If not specified Drone will add
# two worker nodes that connect to $DOCKER_HOST
export DRONE_WORKER_NODES="tcp://0.0.0.0:2375,tcp://0.0.0.0:2375"
Or a combination of the two:
DRONE_GITLAB_URL="https://gitlab.com" ./drone --config=/path/to/drone.conf
GitHub
In order to setup with GitHub you'll need to register your local Drone installation with GitHub (or GitHub Enterprise). You can read more about registering an application here: https://github.com/settings/applications/new
Below are example values when running Drone locally. If you are running Drone on a server
you should replace localhost
with your server hostname or address.
Homepage URL:
http://localhost:8000/
Authorization callback URL:
http://localhost:8000/api/auth/github.com
Compatibility Issues
WARNING
There were some fundamental changes to the application and we decided to introduce breaking changes to the dataabase. Migration would have been difficult and time consuming. Drone is an alpha product and therefore backward compatibility is not a primary goal until we hit a stable release. Apologizes for any inconvenience.