Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/agco/dokku-registry
dokku-registry
https://github.com/agco/dokku-registry
Last synced: 23 days ago
JSON representation
dokku-registry
- Host: GitHub
- URL: https://github.com/agco/dokku-registry
- Owner: agco
- License: mit
- Created: 2014-10-10T19:09:42.000Z (about 10 years ago)
- Default Branch: master
- Last Pushed: 2016-08-10T22:06:03.000Z (over 8 years ago)
- Last Synced: 2024-11-04T10:43:29.533Z (about 1 month ago)
- Language: Shell
- Homepage:
- Size: 258 KB
- Stars: 30
- Watchers: 8
- Forks: 13
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
- License: LICENSE.txt
Awesome Lists containing this project
- awesome-starred - agco/dokku-registry - dokku-registry (others)
README
# dokku-registry [![Build Status](https://img.shields.io/travis/agco/dokku-registry.svg?branch=master "Build Status")](https://travis-ci.org/agco/dokku-registry)
The Docker registry plugin for [Dokku](https://github.com/progrium/dokku) adds support for managing application releases as part of a continuous delivery workflow.
On Heroku similar functionality is offered by the [heroku-labs pipeline feature](https://devcenter.heroku.com/articles/labs-pipelines), which allows you to promote builds across multiple environments (staging -> production)
## requirements
- dokku 0.4.0+
- docker 1.8.x## installation
```shell
# on 0.3.x
cd /var/lib/dokku/plugins
git clone https://github.com/agco/dokku-registry.git registry
dokku plugins-install# on 0.4.x
dokku plugin:install https://github.com/agco/dokku-registry.git registry
```## Commands
```
$ dokku help
registry:login Login to a docker registry
registry:push Clone a git url, exec buildstep and push the resulting Docker image to the logged on registry
registry:pull Pull a Docker image (produced with buildstep) from the logged on registry and deploy
```## Workflow
### Build machine
```
dokku registry:login —username= —password= —email=
```
This logs you in to the dockerhub registry
Other registries can be specified as well with using the optional server arg
Check the [docker login](https://docs.docker.com/reference/commandline/cli/#login) docs for more details```
dokku registry:push
```
This clones the code from a given git_url and builds it with buildstep
The resulting Docker is tagged as specified by the image_tag arg and pushed to the current logged-on Docker registry### Deploy target(s)
```
dokku registry:login —username= —password= —email=
``````
dokku registry:pull
```
This pulls the image tag from the current logged-on registry and deploys it to Dokku. The application will be auto-created in case it doesn't exist yet.### Quick example
Note : This is just to demonstrate syntax, replace credentials and registry image tag with your own values
```
dokku registry:login --username=myusername [email protected] --password=mypwd
dokku registry:push https://github.com/heroku/node-js-getting-started.git myusername/myapp:1.2.3
dokku registry:pull myapp myusername/myapp:1.2.3
```### Set config variables prior to application start
The workflow then looks something like the following
```
dokku registry:login --username=myusername [email protected] --password=mypwd
dokku create myapp
dokku config:set myapp FOO=BAR
dokku registry:pull myapp myusername/myapp:1.2.3
```An example on how to bootstrap this can be found here : https://github.com/agco-adm/dokku-provision-ALM-support