mirror of
https://github.com/harness/drone.git
synced 2025-09-04 19:37:44 +00:00
238e916fa0
In our current drone setup, we are not using a proxy, thus letting drone handle SSL termination. In addition, we are not exposing port 80 (effectively disabling insecure drone access). When new engineers join and attempt to access drone, they are not sent a 301 and often complain that they either do not have access or that drone is broken (when in reality they are just accessing drone via the incorrect protocol/port). This commit changes the default behavior when running drone with a server-cert by only sending redirects on port 80 rather than allowing both secure and insecure access.
Drone is a Continuous Delivery system built on container technology. Drone uses a simple YAML configuration file, a superset of docker-compose, to define and execute Pipelines inside Docker containers.
Sample Pipeline Configuration:
pipeline:
backend:
image: golang
commands:
- go get
- go build
- go test
frontend:
image: node:6
commands:
- npm install
- npm test
publish:
image: plugins/docker
repo: octocat/hello-world
tags: [ 1, 1.1, latest ]
registry: index.docker.io
notify:
image: plugins/slack
channel: developers
username: drone
Documentation and Other Links:
- Setup Documentation docs.drone.io/installation
- Usage Documentation docs.drone.io/getting-started
- Plugin Index plugins.drone.io
- Getting Help docs.drone.io/getting-help