diff --git a/HISTORY.md b/HISTORY.md index 20889c159..ed6badf20 100644 --- a/HISTORY.md +++ b/HISTORY.md @@ -1,5 +1,31 @@ # History +## 0.27.7 + +Install/update via the bootstrap script: + +```shell +wget https://raw.githubusercontent.com/dokku/dokku/v0.27.7/bootstrap.sh +sudo DOKKU_TAG=v0.27.7 bash bootstrap.sh +``` + +### Bug Fixes + +- #5238: @josegonzalez Respect dokku system user/group when setting storage permissions on installation + +### New Features + +- #5239: @josegonzalez Add builder-type and image-stage labels to all images + +### Documentation + +- #5241: @josegonzalez Clarify where logs are pulled from and general log shipping stance +- #5237: @josegonzalez Fix builder-pack:set command example + +### Other + +- #5235: @dependabot[bot] chore(deps-dev): bump heroku/heroku-buildpack-php from 220 to 221 in /tests/apps/php + ## 0.27.6 Install/update via the bootstrap script: diff --git a/README.md b/README.md index c7c78de54..6d99d535e 100644 --- a/README.md +++ b/README.md @@ -87,8 +87,8 @@ Otherwise, you will need to import the keypair manually after installation using To install the latest stable release, run the following commands as a user who has access to `sudo`: ```shell -wget https://raw.githubusercontent.com/dokku/dokku/v0.27.6/bootstrap.sh -sudo DOKKU_TAG=v0.27.6 bash bootstrap.sh +wget https://raw.githubusercontent.com/dokku/dokku/v0.27.7/bootstrap.sh +sudo DOKKU_TAG=v0.27.7 bash bootstrap.sh ``` You can then proceed to configure your server domain (via `dokku domains:set-global`) and user access (via `dokku ssh-keys:add`) to complete the installation. diff --git a/debian/control b/debian/control index 37b4ddfde..be84b16b8 100644 --- a/debian/control +++ b/debian/control @@ -1,5 +1,5 @@ Package: dokku -Version: 0.27.6 +Version: 0.27.7 Section: web Priority: optional Architecture: amd64 diff --git a/docs/advanced-usage/plugin-management.md b/docs/advanced-usage/plugin-management.md index 3a7694337..053b11420 100644 --- a/docs/advanced-usage/plugin-management.md +++ b/docs/advanced-usage/plugin-management.md @@ -35,35 +35,35 @@ dokku plugin:list ``` plugn: dev - 00_dokku-standard 0.27.6 enabled dokku core standard plugin - 20_events 0.27.6 enabled dokku core events logging plugin - app-json 0.27.6 enabled dokku core app-json plugin - apps 0.27.6 enabled dokku core apps plugin - build-env 0.27.6 enabled dokku core build-env plugin - buildpacks 0.27.6 enabled dokku core buildpacks plugin - certs 0.27.6 enabled dokku core certificate management plugin - checks 0.27.6 enabled dokku core checks plugin - common 0.27.6 enabled dokku core common plugin - config 0.27.6 enabled dokku core config plugin - docker-options 0.27.6 enabled dokku core docker-options plugin - domains 0.27.6 enabled dokku core domains plugin - enter 0.27.6 enabled dokku core enter plugin - git 0.27.6 enabled dokku core git plugin - logs 0.27.6 enabled dokku core logs plugin - network 0.27.6 enabled dokku core network plugin - nginx-vhosts 0.27.6 enabled dokku core nginx-vhosts plugin - plugin 0.27.6 enabled dokku core plugin plugin - proxy 0.27.6 enabled dokku core proxy plugin - ps 0.27.6 enabled dokku core ps plugin - repo 0.27.6 enabled dokku core repo plugin - resource 0.27.6 enabled dokku core resource plugin - scheduler-docker-local 0.27.6 enabled dokku core scheduler-docker-local plugin - shell 0.27.6 enabled dokku core shell plugin - ssh-keys 0.27.6 enabled dokku core ssh-keys plugin - storage 0.27.6 enabled dokku core storage plugin - tags 0.27.6 enabled dokku core tags plugin - tar 0.27.6 enabled dokku core tar plugin - trace 0.27.6 enabled dokku core trace plugin + 00_dokku-standard 0.27.7 enabled dokku core standard plugin + 20_events 0.27.7 enabled dokku core events logging plugin + app-json 0.27.7 enabled dokku core app-json plugin + apps 0.27.7 enabled dokku core apps plugin + build-env 0.27.7 enabled dokku core build-env plugin + buildpacks 0.27.7 enabled dokku core buildpacks plugin + certs 0.27.7 enabled dokku core certificate management plugin + checks 0.27.7 enabled dokku core checks plugin + common 0.27.7 enabled dokku core common plugin + config 0.27.7 enabled dokku core config plugin + docker-options 0.27.7 enabled dokku core docker-options plugin + domains 0.27.7 enabled dokku core domains plugin + enter 0.27.7 enabled dokku core enter plugin + git 0.27.7 enabled dokku core git plugin + logs 0.27.7 enabled dokku core logs plugin + network 0.27.7 enabled dokku core network plugin + nginx-vhosts 0.27.7 enabled dokku core nginx-vhosts plugin + plugin 0.27.7 enabled dokku core plugin plugin + proxy 0.27.7 enabled dokku core proxy plugin + ps 0.27.7 enabled dokku core ps plugin + repo 0.27.7 enabled dokku core repo plugin + resource 0.27.7 enabled dokku core resource plugin + scheduler-docker-local 0.27.7 enabled dokku core scheduler-docker-local plugin + shell 0.27.7 enabled dokku core shell plugin + ssh-keys 0.27.7 enabled dokku core ssh-keys plugin + storage 0.27.7 enabled dokku core storage plugin + tags 0.27.7 enabled dokku core tags plugin + tar 0.27.7 enabled dokku core tar plugin + trace 0.27.7 enabled dokku core trace plugin ``` > Warning: All plugin commands other than `plugin:list` and `plugin:help` require sudo access and must be run directly from the Dokku server. diff --git a/docs/assets/favicons/browserconfig.xml b/docs/assets/favicons/browserconfig.xml index c175ace8d..251b53e83 100644 --- a/docs/assets/favicons/browserconfig.xml +++ b/docs/assets/favicons/browserconfig.xml @@ -2,10 +2,10 @@ - - - - + + + + #da532c diff --git a/docs/assets/favicons/manifest.json b/docs/assets/favicons/manifest.json index f82f3586d..9f0ebd861 100644 --- a/docs/assets/favicons/manifest.json +++ b/docs/assets/favicons/manifest.json @@ -2,37 +2,37 @@ "name": "Dokku", "icons": [ { - "src": "https:\/\/cdn.jsdelivr.net\/dokku\/dokku@v0.27.6\/docs\/assets\/favicons\/android-chrome-36x36.png", + "src": "https:\/\/cdn.jsdelivr.net\/dokku\/dokku@v0.27.7\/docs\/assets\/favicons\/android-chrome-36x36.png", "sizes": "36x36", "type": "image\/png", "density": "0.75" }, { - "src": "https:\/\/cdn.jsdelivr.net\/dokku\/dokku@v0.27.6\/docs\/assets\/favicons\/android-chrome-48x48.png", + "src": "https:\/\/cdn.jsdelivr.net\/dokku\/dokku@v0.27.7\/docs\/assets\/favicons\/android-chrome-48x48.png", "sizes": "48x48", "type": "image\/png", "density": "1.0" }, { - "src": "https:\/\/cdn.jsdelivr.net\/dokku\/dokku@v0.27.6\/docs\/assets\/favicons\/android-chrome-72x72.png", + "src": "https:\/\/cdn.jsdelivr.net\/dokku\/dokku@v0.27.7\/docs\/assets\/favicons\/android-chrome-72x72.png", "sizes": "72x72", "type": "image\/png", "density": "1.5" }, { - "src": "https:\/\/cdn.jsdelivr.net\/dokku\/dokku@v0.27.6\/docs\/assets\/favicons\/android-chrome-96x96.png", + "src": "https:\/\/cdn.jsdelivr.net\/dokku\/dokku@v0.27.7\/docs\/assets\/favicons\/android-chrome-96x96.png", "sizes": "96x96", "type": "image\/png", "density": "2.0" }, { - "src": "https:\/\/cdn.jsdelivr.net\/dokku\/dokku@v0.27.6\/docs\/assets\/favicons\/android-chrome-144x144.png", + "src": "https:\/\/cdn.jsdelivr.net\/dokku\/dokku@v0.27.7\/docs\/assets\/favicons\/android-chrome-144x144.png", "sizes": "144x144", "type": "image\/png", "density": "3.0" }, { - "src": "https:\/\/cdn.jsdelivr.net\/dokku\/dokku@v0.27.6\/docs\/assets\/favicons\/android-chrome-192x192.png", + "src": "https:\/\/cdn.jsdelivr.net\/dokku\/dokku@v0.27.7\/docs\/assets\/favicons\/android-chrome-192x192.png", "sizes": "192x192", "type": "image\/png", "density": "4.0" diff --git a/docs/assets/style.css b/docs/assets/style.css index 16295ddc4..a96c2d281 100644 --- a/docs/assets/style.css +++ b/docs/assets/style.css @@ -42,13 +42,13 @@ h1 { font-size: 1.6em; } .header .navbar-brand a { - background-image: url(https://cdn.jsdelivr.net/gh/dokku/dokku@v0.27.6/docs/assets/dokku.png); + background-image: url(https://cdn.jsdelivr.net/gh/dokku/dokku@v0.27.7/docs/assets/dokku.png); text-indent: 40px; } .blurb { color: #424242; background-color: #ededed; - background-image: url(https://cdn.jsdelivr.net/gh/dokku/dokku@v0.27.6/docs/assets/gplaypattern.png); + background-image: url(https://cdn.jsdelivr.net/gh/dokku/dokku@v0.27.7/docs/assets/gplaypattern.png); padding: 45px 0; text-align: center; } diff --git a/docs/assets/versions.json b/docs/assets/versions.json index 3015ca1aa..f0c1f59c7 100644 --- a/docs/assets/versions.json +++ b/docs/assets/versions.json @@ -24,6 +24,6 @@ "0.24.10", "0.25.7", "0.26.8", - "0.27.6" + "0.27.7" ] } diff --git a/docs/deployment/builders/cloud-native-buildpacks.md b/docs/deployment/builders/cloud-native-buildpacks.md index 572a6d2c4..ebbb15768 100644 --- a/docs/deployment/builders/cloud-native-buildpacks.md +++ b/docs/deployment/builders/cloud-native-buildpacks.md @@ -84,7 +84,7 @@ dokku builder-pack:set --global projecttoml-path You can get a report about the app's storage status using the `builder-pack:report` command: ```shell -dokku app-json:report +dokku builder-pack:report ``` ``` diff --git a/docs/deployment/logs.md b/docs/deployment/logs.md index 1271ddde6..f4f2ce66c 100644 --- a/docs/deployment/logs.md +++ b/docs/deployment/logs.md @@ -20,6 +20,8 @@ You can easily get logs of an app using the `logs` command: dokku logs node-js-app ``` +Logs are pulled via integration with the scheduler for the specified application via "live tailing". As such, logs from previously running deployments are usually not available. Users that desire to see logs from previous deployments for debugging purposes should persist those logs to external services. Please see Dokku's [vector integration](deployment/logs.md#vector-logging-shipping) for more information on how to persist logs across deployments to ship logs to another service or a third-party platform. + #### Behavioral modifiers Dokku also supports certain command-line arguments that augment the `log` command's behavior. diff --git a/docs/deployment/schedulers/docker-local.md b/docs/deployment/schedulers/docker-local.md index df2048f78..5d50da590 100644 --- a/docs/deployment/schedulers/docker-local.md +++ b/docs/deployment/schedulers/docker-local.md @@ -91,7 +91,11 @@ Omitting or removing the entry will result in parallelism for that process type Note that increasing the value of `max_parallel` may significantly impact CPU utilization on your host as your app containers - and their respective processes - start up. Setting a value higher than the number of available CPUs is discouraged. It is recommended that users carefully set this value so as not to overburden their server. -## Implemented Triggers +## Scheduler Interface + +The following sections describe implemented scheduler functionality for the `docker-local` scheduler. + +### Implemented Commands and Triggers This plugin implements various functionality through `plugn` triggers to integrate with Docker for running apps on a single server. The following functionality is supported by the `scheduler-docker-local` plugin. @@ -105,11 +109,16 @@ This plugin implements various functionality through `plugn` triggers to integra - `ps:stop` - `run` -## Supported Resource Management Properties + +### Logging support + +App logs for the `logs` command are fetched from running containers via the `docker` cli. To persist logs across deployments, consider using Dokku's [vector integration](deployment/logs.md#vector-logging-shipping) to ship logs to another service or a third-party platform. + +### Supported Resource Management Properties The `docker-local` scheduler supports a minimal list of resource _limits_ and _reservations_. The following properties are supported: -### Resource Limits +#### Resource Limits - cpu: (docker option: `--cpus`), is specified in number of CPUs a process can access. - See the ["CPU" section](https://docs.docker.com/config/containers/resource_constraints/#cpu) of the Docker Runtime Options documentation for more information. @@ -120,7 +129,7 @@ The `docker-local` scheduler supports a minimal list of resource _limits_ and _r - nvidia-gpus: (docker option: `--gpus`), is specified in number of Nvidia GPUs a process can access. - See the ["GPU" section](https://docs.docker.com/config/containers/resource_constraints/#gpu) of the Docker Runtime Options documentation for more information. -### Resource Reservations +#### Resource Reservations - memory: (docker option: `--memory-reservation`) should be specified with a suffix of `b` (bytes), `k` (kilobytes), `m` (megabytes), `g` (gigabytes). Default unit is `m` (megabytes). - See the ["Memory" section](https://docs.docker.com/config/containers/resource_constraints/#memory) of the Docker Runtime Options documentation for more information. diff --git a/docs/deployment/schedulers/kubernetes.md b/docs/deployment/schedulers/kubernetes.md index 245f5857d..1d945bf88 100644 --- a/docs/deployment/schedulers/kubernetes.md +++ b/docs/deployment/schedulers/kubernetes.md @@ -2,13 +2,23 @@ > Warning: This scheduler is not in Dokku core and thus functionality may change over time as the API stabilizes. -The [Kubernetes Scheduler Plugin](https://github.com/dokku/dokku-scheduler-kubernetes) implements the following functionality: +The [Nomad Scheduler Plugin](https://github.com/dokku/dokku-scheduler-kubernetes) is available free as an external plugin. Please see the plugin's [issue tracker](https://github.com/dokku/dokku-scheduler-kubernetes/issues) for more information on the status of the plugin. + +For users that require additional functionality, please refer to the [Sponsoring Documentation](https://github.com/dokku/.github/blob/master/SPONSORING.md). + +## Scheduler Interface + +The following sections describe implemented scheduler functionality for the `docker-local` scheduler. + +### Implemented Commands and Triggers + +This plugin implements various functionality through `plugn` triggers to integrate with `kubectl` for running apps on a Kubernetes cluster. The following functionality is supported by the `scheduler-kubernetes` plugin. - `apps:destroy` - `deploy`: partial, does not implement failed deploy log capture - `logs`: partial, does not implement failure logs - `ps:stop` -Please see the plugin's [issue tracker](https://github.com/dokku/dokku-scheduler-kubernetes/issues) for more information on the status of the plugin. +### Logging support -For users that require additional functionality, please refer to the [Sponsoring Documentation](https://github.com/dokku/.github/blob/master/SPONSORING.md). +App logs for the `logs` command are fetched from running pods via the `kubectl` cli. To persist logs across deployments, consider using [Vector](https://vector.dev/docs/setup/installation/platforms/kubernetes/) or a similar tool to ship logs to another service or a third-party platform. diff --git a/docs/deployment/schedulers/nomad.md b/docs/deployment/schedulers/nomad.md index 380f92875..e043db3a9 100644 --- a/docs/deployment/schedulers/nomad.md +++ b/docs/deployment/schedulers/nomad.md @@ -2,12 +2,22 @@ > Warning: This scheduler is not in Dokku core and thus functionality may change over time as the API stabilizes. -The [Nomad Scheduler Plugin](https://github.com/dokku/dokku-scheduler-nomad) implements the following functionality: +The [Nomad Scheduler Plugin](https://github.com/dokku/dokku-scheduler-nomad) is available free as an external plugin. Please see the plugin's [issue tracker](https://github.com/dokku/dokku-scheduler-nomad/issues) for more information on the status of the plugin. + +For users that require additional functionality, please refer to the [Sponsoring Documentation](https://github.com/dokku/.github/blob/master/SPONSORING.md). + +## Scheduler Interface + +The following sections describe implemented scheduler functionality for the `docker-local` scheduler. + +### Implemented Commands and Triggers + +This plugin implements various functionality through `plugn` triggers to integrate with the `nomad` cli for running apps on a Nomad cluster. The following functionality is supported by the `scheduler-nomad` plugin. - `apps:destroy` - `deploy` - `ps:stop` -Please see the plugin's [issue tracker](https://github.com/dokku/dokku-scheduler-nomad/issues) for more information on the status of the plugin. +### Logging support -For users that require additional functionality, please refer to the [Sponsoring Documentation](https://github.com/dokku/.github/blob/master/SPONSORING.md). +> Warning: Fetching app logs for the `logs` command is currently not implemented. Please consider using [Vector](https://vector.dev/docs/setup/installation/platforms/kubernetes/) or a similar tool to ship logs to another service or a third-party platform. diff --git a/docs/development/release-process.md b/docs/development/release-process.md index fe3968161..07e397686 100644 --- a/docs/development/release-process.md +++ b/docs/development/release-process.md @@ -29,7 +29,7 @@ The workflow looks like this: ```shell # having dokku-arch in ../dokku-arch vagrant up build-arch -# wait for "==> build-arch: ==> Finished making: dokku 0.27.6-2 (Mon Feb 22 23:20:37 CET 2016)" +# wait for "==> build-arch: ==> Finished making: dokku 0.27.7-2 (Mon Feb 22 23:20:37 CET 2016)" cd ../dokku-arch git add PKGBUILD .SRCINFO git commit -m 'Update to dokku 0.9.9' diff --git a/docs/getting-started/install/docker.md b/docs/getting-started/install/docker.md index b7835a082..79ca309ad 100644 --- a/docs/getting-started/install/docker.md +++ b/docs/getting-started/install/docker.md @@ -3,7 +3,7 @@ Pull the dokku/dokku image: ```shell -docker pull dokku/dokku:0.27.6 +docker pull dokku/dokku:0.27.7 ``` Next, run the image. @@ -18,7 +18,7 @@ docker container run \ --publish 8443:443 \ --volume /var/lib/dokku:/mnt/dokku \ --volume /var/run/docker.sock:/var/run/docker.sock \ - dokku/dokku:0.27.6 + dokku/dokku:0.27.7 ``` The above command will start a new docker container that is ready when a message similar to `Runit started as PID 12345` appears. diff --git a/docs/getting-started/installation.md b/docs/getting-started/installation.md index 77d51f545..0e165319d 100644 --- a/docs/getting-started/installation.md +++ b/docs/getting-started/installation.md @@ -39,8 +39,8 @@ To install the latest stable version of Dokku, you can run the following shell c ```shell # for debian systems, installs Dokku via apt-get -wget https://raw.githubusercontent.com/dokku/dokku/v0.27.6/bootstrap.sh; -sudo DOKKU_TAG=v0.27.6 bash bootstrap.sh +wget https://raw.githubusercontent.com/dokku/dokku/v0.27.7/bootstrap.sh; +sudo DOKKU_TAG=v0.27.7 bash bootstrap.sh ``` The installation process takes about 5-10 minutes, depending upon internet connection speed. diff --git a/docs/home.html b/docs/home.html index 95a50b3af..6757bb921 100644 --- a/docs/home.html +++ b/docs/home.html @@ -10,30 +10,30 @@ Dokku - The smallest PaaS implementation you've ever seen - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + - - + + - + @@ -98,12 +98,12 @@

$ - wget https://raw.githubusercontent.com/dokku/dokku/v0.27.6/bootstrap.sh + wget https://raw.githubusercontent.com/dokku/dokku/v0.27.7/bootstrap.sh

$ - sudo DOKKU_TAG=v0.27.6 bash bootstrap.sh + sudo DOKKU_TAG=v0.27.7 bash bootstrap.sh

 # Configure your server domain via `dokku domains:set-global` diff --git a/docs/template.html b/docs/template.html index 2b64fbb48..cd74c2056 100644 --- a/docs/template.html +++ b/docs/template.html @@ -9,26 +9,26 @@ Dokku - {{DOC_TITLE}} - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + - - + + - +