Jose Diaz-Gonzalez 353438dbd3 feat: allow builders to be detected based on repository contents
Rather than hardcode two builders, allow builders to specify a `builder-detect` trigger. This trigger can be used to specify if the builder should or should not be used for an application. Each builder takes stdin and can decide if it wants to emit it or emit it's own image source type.

If the final value is empty, then Dokku will default to herokuish (and cnb once that is stable). In addition, a future change may allow users to manually specify a builder in the case they wish to override the choice selected by Dokku.

This change enables users to build custom builder plugins and have those plugins used for building an image asset. By way of example, an enterprising user could create a `builder-lambda` based on lambci, and then pair this with a scheduler plugin that updates a lambda function on AWS. Alternatively, a user might decide they wish to place their Dockerfile in a specific directory for their applications - such as an `_infrastructure` directory - and create a plugin to override how that is detected within Dokku.
2021-02-28 16:19:41 -05:00
2021-02-28 04:47:37 -05:00
2021-02-28 07:40:27 +00:00
2021-02-28 04:47:37 -05:00
2018-12-29 21:21:17 -05:00
2021-02-21 03:12:57 -05:00
2021-02-28 07:40:27 +00:00
2014-02-03 22:53:56 -08:00
2021-02-28 04:47:37 -05:00
2021-02-28 07:40:27 +00:00
2021-02-28 04:47:37 -05:00

Dokku

Build Status Ubuntu Package Arch Package IRC Network Slack Group Documentation OpenCollective OpenCollective Patreon

Docker powered mini-Heroku. The smallest PaaS implementation you've ever seen.

Sponsors

Become a sponsor and get your logo on our README on Github with a link to your site. [Become a sponsor]

Backers

Support us with a monthly donation and help us continue our activities. [Become a backer]

Requirements

A fresh VM running any of the following operating systems:

  • Ubuntu 16.04/18.04/20.04 x64 - Any currently supported release
  • Debian 9+ x64
  • CentOS 7 x64 (experimental)
  • Arch Linux x64 (experimental)

An SSH keypair that can be used for application deployment. If this exists before installation, it will be automatically imported into dokku. Otherwise, you will need to import the keypair manually after installation using dokku ssh-keys:add.

Installation

To install the latest stable release, run the following commands as a user who has access to sudo:

wget https://raw.githubusercontent.com/dokku/dokku/v0.23.9/bootstrap.sh
sudo DOKKU_TAG=v0.23.9 bash bootstrap.sh

You can then proceed to the ip address or domain name associated with your server to complete the web-based installation.

If you wish for a more unattended installation method, see these docs.

Upgrade

View the docs for upgrading from an older version of Dokku.

Documentation

Full documentation - including advanced installation docs - are available online at https://dokku.com/docs/.

Support

You can use Github Issues, check Troubleshooting in the documentation, or join us on freenode in #dokku.

Contribution

After checking Github Issues, the Troubleshooting Guide or having a chat with us on freenode in #dokku, feel free to fork and create a Pull Request.

While we may not merge your PR as is, they serve to start conversations and improve the general Dokku experience for all users.

License

MIT License © Jeff Lindsay

Description
A docker-powered PaaS that helps you build and manage the lifecycle of applications dokku.com
Readme MIT 37 MiB
Languages
Shell 56.9%
Go 37.5%
Makefile 2%
Python 1.4%
HTML 0.7%
Other 1.2%