Merge pull request #4444 from dokku/update-rewrites
Uuse updated links for documentation
This commit is contained in:
@@ -5,10 +5,10 @@ several ways to help out:
|
|||||||
|
|
||||||
* Create an [issue](https://github.com/dokku/dokku/issues) on GitHub, if you
|
* Create an [issue](https://github.com/dokku/dokku/issues) on GitHub, if you
|
||||||
have found a bug
|
have found a bug
|
||||||
* Write [test cases](http://dokku.viewdocs.io/dokku/development/testing/) for open bug issues
|
* Write [test cases](https://dokku.com/docs/development/testing/) for open bug issues
|
||||||
* Write patches for open bug/feature issues, preferably with test cases
|
* Write patches for open bug/feature issues, preferably with test cases
|
||||||
included
|
included
|
||||||
* Contribute to the [documentation](http://dokku.viewdocs.io/dokku/)
|
* Contribute to the [documentation](https://dokku.com/docs/)
|
||||||
* Come up with new ways, non-commercial to show off our [lovely logo](https://avatars1.githubusercontent.com/u/13455795)
|
* Come up with new ways, non-commercial to show off our [lovely logo](https://avatars1.githubusercontent.com/u/13455795)
|
||||||
* Blog about different ways you are using dokku
|
* Blog about different ways you are using dokku
|
||||||
* Sponsor the Dokku project financially on [OpenCollective](https://opencollective.com/dokku#support) or [Patreon](https://www.patreon.com/dokku)
|
* Sponsor the Dokku project financially on [OpenCollective](https://opencollective.com/dokku#support) or [Patreon](https://www.patreon.com/dokku)
|
||||||
@@ -45,7 +45,7 @@ encounter an issue. We always appreciate a well-written, thorough bug report,
|
|||||||
and will thank you for it!
|
and will thank you for it!
|
||||||
|
|
||||||
Sometimes Dokku is missing a feature you need. In some cases, those features can
|
Sometimes Dokku is missing a feature you need. In some cases, those features can
|
||||||
be found in pre-existing [plugins](http://dokku.viewdocs.io/dokku/plugins/),
|
be found in pre-existing [plugins](https://dokku.com/docs/plugins/),
|
||||||
and we encourage our users to create and contribute such packages. From time to
|
and we encourage our users to create and contribute such packages. From time to
|
||||||
time, we will also pull plugins into the Dokku core when the task they solve is
|
time, we will also pull plugins into the Dokku core when the task they solve is
|
||||||
a common one for our users.
|
a common one for our users.
|
||||||
@@ -129,7 +129,7 @@ requests:
|
|||||||
|
|
||||||
### Running tests locally
|
### Running tests locally
|
||||||
|
|
||||||
Please read the [testing docs](http://dokku.viewdocs.io/dokku/development/testing/),
|
Please read the [testing docs](https://dokku.com/docs/development/testing/),
|
||||||
which contains test setup information as well as tips for running tests.
|
which contains test setup information as well as tips for running tests.
|
||||||
|
|
||||||
# Additional Resources
|
# Additional Resources
|
||||||
|
|||||||
20
HISTORY.md
20
HISTORY.md
@@ -2905,8 +2905,8 @@ This release is a minor bugfix to fix an issue with ssl support for spdy-enabled
|
|||||||
|
|
||||||
The big-six-o. This release is largely comprised of new features that should allow for easier management of dokku. The highlights of this release are:
|
The big-six-o. This release is largely comprised of new features that should allow for easier management of dokku. The highlights of this release are:
|
||||||
|
|
||||||
- The proxy plugin has been enhanced to allow users to map container ports to host ports. In the 0.5.0 release, we changed the semantics of how Dockerfile `EXPOSE` calls work to better follow Docker's lead, which ended up breaking how some applications were deployed to dokku. Please read our documentation surrounding [port management](http://dokku.viewdocs.io/dokku/proxy/) for more details.
|
- The proxy plugin has been enhanced to allow users to map container ports to host ports. In the 0.5.0 release, we changed the semantics of how Dockerfile `EXPOSE` calls work to better follow Docker's lead, which ended up breaking how some applications were deployed to dokku. Please read our documentation surrounding [port management](https://dokku.com/docs/proxy/) for more details.
|
||||||
- Zero-downtime deploys can be disabled on a per-app and per-process basis. This can be used to speed up deploys when there are non-web processes being deployed, or when a user wishes to completely avoid any such waiting period. Please see the [checks documentation](http://dokku.viewdocs.io/dokku/checks-examples/) for further information.
|
- Zero-downtime deploys can be disabled on a per-app and per-process basis. This can be used to speed up deploys when there are non-web processes being deployed, or when a user wishes to completely avoid any such waiting period. Please see the [checks documentation](https://dokku.com/docs/deployment/zero-downtime-deploys/) for further information.
|
||||||
|
|
||||||
Thanks to all the contributors who helped with this release, and a special thanks to @michaelshobbs for ferrying the majority of our new functionality to it's current state!
|
Thanks to all the contributors who helped with this release, and a special thanks to @michaelshobbs for ferrying the majority of our new functionality to it's current state!
|
||||||
|
|
||||||
@@ -3026,7 +3026,7 @@ Thanks to all the contributors who helped with this release!
|
|||||||
|
|
||||||
Release 0.5.5 is mostly a documentation release, further clarifying how our default proxy implementation (nginx) interacts with Dockerfiles. Note that we also updated how ssl certificates interact with application domains, so please check out our domains and ssl documentation.
|
Release 0.5.5 is mostly a documentation release, further clarifying how our default proxy implementation (nginx) interacts with Dockerfiles. Note that we also updated how ssl certificates interact with application domains, so please check out our domains and ssl documentation.
|
||||||
|
|
||||||
We've also added a small section to the [dokku homepage](http://dokku.viewdocs.io/dokku/) that lists the current core team. Feel free to look at their beautiful faces and imagine yourself contributing to Dokku and joining our core team. There are [quite a few ways to contribute](https://github.com/dokku/dokku/blob/master/CONTRIBUTING.md) - even without code/documentation - so feel more than free to jump on the bandwagon!
|
We've also added a small section to the [dokku homepage](https://dokku.com/docs/) that lists the current core team. Feel free to look at their beautiful faces and imagine yourself contributing to Dokku and joining our core team. There are [quite a few ways to contribute](https://github.com/dokku/dokku/blob/master/CONTRIBUTING.md) - even without code/documentation - so feel more than free to jump on the bandwagon!
|
||||||
|
|
||||||
Finally, we've started an [Official Dokku Blog](https://dokku.github.io/), where we will post about dokku internals, roadmaps, potential use-cases, etc. An rss feed is available [here](https://dokku.github.io/feed.xml).
|
Finally, we've started an [Official Dokku Blog](https://dokku.github.io/), where we will post about dokku internals, roadmaps, potential use-cases, etc. An rss feed is available [here](https://dokku.github.io/feed.xml).
|
||||||
|
|
||||||
@@ -3125,9 +3125,9 @@ This is our largest, most feature-packed release in the history of the dokku pro
|
|||||||
|
|
||||||
- Support for docker 1.10/1.11. You *must* have docker 1.9.1+ to install dokku.
|
- Support for docker 1.10/1.11. You *must* have docker 1.9.1+ to install dokku.
|
||||||
- Revamped documentation website
|
- Revamped documentation website
|
||||||
- [Deployment Tasks](http://dokku.viewdocs.io/dokku/deployment/deployment-tasks/)
|
- [Deployment Tasks](https://dokku.com/docs/advanced-usage/deployment-tasks/)
|
||||||
- Heroku-style management of [dockerfile processes](http://dokku.viewdocs.io/dokku/deployment/dockerfiles/#procfiles-and-multiple-processes)
|
- Heroku-style management of [dockerfile processes](https://dokku.com/docs/deployment/methods/dockerfiles/#procfiles-and-multiple-processes)
|
||||||
- Official [persistent storage plugin](http://dokku.viewdocs.io/dokku/dokku-storage/)
|
- Official [persistent storage plugin](https://dokku.com/docs/advanced-usage/persistent-storage/)
|
||||||
|
|
||||||
We'd also love it if you welcomed a few new core developers:
|
We'd also love it if you welcomed a few new core developers:
|
||||||
|
|
||||||
@@ -3621,9 +3621,9 @@ One new feature is colorized logging output, which should make it easier to debu
|
|||||||
|
|
||||||
This is our first minor release in almost a year. Many new features and removals have occurred, so here is a neat summary:
|
This is our first minor release in almost a year. Many new features and removals have occurred, so here is a neat summary:
|
||||||
|
|
||||||
- Plugins are now triggered via `plugn`. Notably, you'll need add a `plugin.toml` to describe the plugin as well as use `plugn trigger` instead of `pluginhook` to trigger plugin callbacks. Please see the [plugin creation documentation](http://dokku.viewdocs.io/dokku/development/plugin-creation/) for more details.
|
- Plugins are now triggered via `plugn`. Notably, you'll need add a `plugin.toml` to describe the plugin as well as use `plugn trigger` instead of `pluginhook` to trigger plugin callbacks. Please see the [plugin creation documentation](https://dokku.com/docs/development/plugin-creation/) for more details.
|
||||||
- A few new official plugins have been added to the core, including [image tagging](http://dokku.viewdocs.io/dokku/application-deployment/), [certificate management](http://dokku.viewdocs.io/dokku/deployment/ssl-configuration/), a tar-based deploy solution, and much more. Check out the *New Features* section for more details.
|
- A few new official plugins have been added to the core, including [image tagging](https://dokku.com/docs/deployment/application-deployment/), [certificate management](https://dokku.com/docs/configuration/ssl/), a tar-based deploy solution, and much more. Check out the *New Features* section for more details.
|
||||||
- We've removed a few deprecated plugin callbacks. Please see the [plugin triggers documentation](http://dokku.viewdocs.io/dokku/development/plugin-triggers/) to see what is available.
|
- We've removed a few deprecated plugin callbacks. Please see the [plugin triggers documentation](https://dokku.com/docs/development/plugin-triggers/) to see what is available.
|
||||||
- [Official datastorage plugins](https://github.com/dokku) have been created for the most commonly used datastores. If you previously used/maintained a community contributed plugin, please check these out. We'll be adding more official plugins as time goes on.
|
- [Official datastorage plugins](https://github.com/dokku) have been created for the most commonly used datastores. If you previously used/maintained a community contributed plugin, please check these out. We'll be adding more official plugins as time goes on.
|
||||||
|
|
||||||
Thanks to the *many* contributors for making this release our best release so far, and special thanks to both @michaelshobbs and @Flink for pushing along the `0.4.0` release!
|
Thanks to the *many* contributors for making this release our best release so far, and special thanks to both @michaelshobbs and @Flink for pushing along the `0.4.0` release!
|
||||||
@@ -3732,7 +3732,7 @@ This release is a bugfix release covering dokku packaging.
|
|||||||
|
|
||||||
## 0.3.23
|
## 0.3.23
|
||||||
|
|
||||||
This release is a bugfix release mostly covering installation and nginx issues. As well, we launched a nicer documentation site [here](http://dokku.viewdocs.io/dokku/). Thanks to all of our contributors for making this a great release!
|
This release is a bugfix release mostly covering installation and nginx issues. As well, we launched a nicer documentation site [here](https://dokku.com/docs/). Thanks to all of our contributors for making this a great release!
|
||||||
|
|
||||||
### Bug Fixes
|
### Bug Fixes
|
||||||
|
|
||||||
|
|||||||
@@ -2,7 +2,7 @@
|
|||||||
>
|
>
|
||||||
> If you'd like to sponsor specific functionality, see the project's [Sponsoring](https://github.com/dokku/.github/blob/master/SPONSORING.md) document.
|
> If you'd like to sponsor specific functionality, see the project's [Sponsoring](https://github.com/dokku/.github/blob/master/SPONSORING.md) document.
|
||||||
>
|
>
|
||||||
> If you need help figuring out how to use a specific buildpack, are seeing an issue in during the buildpack process, or are having issues using multiple buildpacks, please see our [slack channels or github discussion board](http://dokku.viewdocs.io/dokku/getting-started/where-to-get-help/#monitored-locations). Issues pertaining to buildpacks may be closed and locked.
|
> If you need help figuring out how to use a specific buildpack, are seeing an issue in during the buildpack process, or are having issues using multiple buildpacks, please see our [slack channels or github discussion board](https://dokku.com/docs/getting-started/where-to-get-help/#monitored-locations). Issues pertaining to buildpacks may be closed and locked.
|
||||||
>
|
>
|
||||||
> If you need support for a version of Dokku that is more than a year old, your issue may be closed without an answer. Please upgrade to a recent version.
|
> If you need support for a version of Dokku that is more than a year old, your issue may be closed without an answer. Please upgrade to a recent version.
|
||||||
|
|
||||||
|
|||||||
12
README.md
12
README.md
@@ -5,7 +5,7 @@
|
|||||||
[](https://aur.archlinux.org/packages/dokku/)
|
[](https://aur.archlinux.org/packages/dokku/)
|
||||||
[](https://webchat.freenode.net/?channels=dokku)
|
[](https://webchat.freenode.net/?channels=dokku)
|
||||||
[](https://glider-slackin.herokuapp.com/)
|
[](https://glider-slackin.herokuapp.com/)
|
||||||
[](http://dokku.viewdocs.io/dokku/)
|
[](https://dokku.com/docs/)
|
||||||
[](#sponsors)
|
[](#sponsors)
|
||||||
[](#backers)
|
[](#backers)
|
||||||
[](https://www.patreon.com/dokku/)
|
[](https://www.patreon.com/dokku/)
|
||||||
@@ -105,23 +105,23 @@ sudo DOKKU_TAG=v0.23.8 bash bootstrap.sh
|
|||||||
|
|
||||||
You can then proceed to the ip address or domain name associated with your server to complete the web-based installation.
|
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](http://dokku.viewdocs.io/dokku/getting-started/install/debian/#unattended-installation) docs.
|
If you wish for a more unattended installation method, see [these](https://dokku.com/docs/getting-started/install/debian/#unattended-installation) docs.
|
||||||
|
|
||||||
### Upgrade
|
### Upgrade
|
||||||
|
|
||||||
[View the docs](http://dokku.viewdocs.io/dokku/getting-started/upgrading/) for upgrading from an older version of Dokku.
|
[View the docs](https://dokku.com/docs/getting-started/upgrading/) for upgrading from an older version of Dokku.
|
||||||
|
|
||||||
## Documentation
|
## Documentation
|
||||||
|
|
||||||
Full documentation - including advanced installation docs - are available online at [http://dokku.viewdocs.io/dokku/](http://dokku.viewdocs.io/dokku/).
|
Full documentation - including advanced installation docs - are available online at [https://dokku.com/docs/](https://dokku.com/docs/).
|
||||||
|
|
||||||
## Support
|
## Support
|
||||||
|
|
||||||
You can use [Github Issues](https://github.com/dokku/dokku/issues), check [Troubleshooting](http://dokku.viewdocs.io/dokku/getting-started/troubleshooting/) in the documentation, or join us on [freenode in #dokku](https://webchat.freenode.net/?channels=%23dokku).
|
You can use [Github Issues](https://github.com/dokku/dokku/issues), check [Troubleshooting](https://dokku.com/docs/getting-started/troubleshooting/) in the documentation, or join us on [freenode in #dokku](https://webchat.freenode.net/?channels=%23dokku).
|
||||||
|
|
||||||
## Contribution
|
## Contribution
|
||||||
|
|
||||||
After checking [Github Issues](https://github.com/dokku/dokku/issues), the [Troubleshooting Guide](http://dokku.viewdocs.io/dokku/getting-started/troubleshooting/) or having a chat with us on [freenode in #dokku](https://webchat.freenode.net/?channels=%23dokku), feel free to fork and create a Pull Request.
|
After checking [Github Issues](https://github.com/dokku/dokku/issues), the [Troubleshooting Guide](https://dokku.com/docs/getting-started/troubleshooting/) or having a chat with us on [freenode in #dokku](https://webchat.freenode.net/?channels=%23dokku), 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.
|
While we may not merge your PR as is, they serve to start conversations and improve the general Dokku experience for all users.
|
||||||
|
|
||||||
|
|||||||
@@ -35,7 +35,7 @@ ensure-environment() {
|
|||||||
FREE_MEMORY=$(grep MemTotal /proc/meminfo | awk '{print $2}')
|
FREE_MEMORY=$(grep MemTotal /proc/meminfo | awk '{print $2}')
|
||||||
if [[ "$FREE_MEMORY" -lt 1003600 ]]; then
|
if [[ "$FREE_MEMORY" -lt 1003600 ]]; then
|
||||||
echo "For dokku to build containers, it is strongly suggested that you have 1024 megabytes or more of free memory"
|
echo "For dokku to build containers, it is strongly suggested that you have 1024 megabytes or more of free memory"
|
||||||
echo "If necessary, please consult this document to setup swap: http://dokku.viewdocs.io/dokku/getting-started/advanced-installation/#vms-with-less-than-1-gb-of-memory"
|
echo "If necessary, please consult this document to setup swap: https://dokku.com/docs/getting-started/advanced-installation/#vms-with-less-than-1-gb-of-memory"
|
||||||
fi
|
fi
|
||||||
}
|
}
|
||||||
|
|
||||||
@@ -101,7 +101,7 @@ install-dokku-from-source() {
|
|||||||
local DOKKU_CHECKOUT="$1"
|
local DOKKU_CHECKOUT="$1"
|
||||||
|
|
||||||
if ! command -v apt-get &>/dev/null; then
|
if ! command -v apt-get &>/dev/null; then
|
||||||
log-fail "This installation script requires apt-get. For manual installation instructions, consult http://dokku.viewdocs.io/dokku/advanced-installation/"
|
log-fail "This installation script requires apt-get. For manual installation instructions, consult https://dokku.com/docs/getting-started/advanced-installation/"
|
||||||
fi
|
fi
|
||||||
|
|
||||||
apt-get -qq -y --no-install-recommends install sudo git make software-properties-common
|
apt-get -qq -y --no-install-recommends install sudo git make software-properties-common
|
||||||
@@ -125,7 +125,7 @@ install-dokku-from-package() {
|
|||||||
install-dokku-from-rpm-package "$@"
|
install-dokku-from-rpm-package "$@"
|
||||||
;;
|
;;
|
||||||
*)
|
*)
|
||||||
log-fail "Unsupported Linux distribution. For manual installation instructions, consult http://dokku.viewdocs.io/dokku/advanced-installation/"
|
log-fail "Unsupported Linux distribution. For manual installation instructions, consult https://dokku.com/docs/getting-started/advanced-installation/"
|
||||||
;;
|
;;
|
||||||
esac
|
esac
|
||||||
}
|
}
|
||||||
|
|||||||
@@ -341,7 +341,7 @@ PAGE = """
|
|||||||
<div class="form-group">
|
<div class="form-group">
|
||||||
<label for="key">Public SSH Keys</label><br />
|
<label for="key">Public SSH Keys</label><br />
|
||||||
<textarea class="form-control" name="keys" rows="5" id="key" placeholder="Begins with 'ssh-rsa', 'ssh-dss', 'ssh-ed25519', 'ecdsa-sha2-nistp256', 'ecdsa-sha2-nistp384', or 'ecdsa-sha2-nistp521'">{ADMIN_KEYS}</textarea>
|
<textarea class="form-control" name="keys" rows="5" id="key" placeholder="Begins with 'ssh-rsa', 'ssh-dss', 'ssh-ed25519', 'ecdsa-sha2-nistp256', 'ecdsa-sha2-nistp384', or 'ecdsa-sha2-nistp521'">{ADMIN_KEYS}</textarea>
|
||||||
<small class="form-text text-muted">Public keys allow users to ssh onto the server as the <code>dokku</code> user, as well as remotely execute Dokku commands. They are currently auto-populated from: <code>{AUTHORIZED_KEYS_LOCATION}</code>, and can be changed later via the <a href="http://dokku.viewdocs.io/dokku/deployment/user-management/" target="_blank"><code>dokku ssh-keys</code></a> plugin.</small>
|
<small class="form-text text-muted">Public keys allow users to ssh onto the server as the <code>dokku</code> user, as well as remotely execute Dokku commands. They are currently auto-populated from: <code>{AUTHORIZED_KEYS_LOCATION}</code>, and can be changed later via the <a href="https://dokku.com/docs/deployment/user-management/" target="_blank"><code>dokku ssh-keys</code></a> plugin.</small>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
@@ -352,7 +352,7 @@ PAGE = """
|
|||||||
<div class="form-group">
|
<div class="form-group">
|
||||||
<label for="hostname">Hostname</label>
|
<label for="hostname">Hostname</label>
|
||||||
<input class="form-control" type="text" id="hostname" name="hostname" value="{HOSTNAME}" placeholder="A hostname or ip address such as {HOSTNAME}" />
|
<input class="form-control" type="text" id="hostname" name="hostname" value="{HOSTNAME}" placeholder="A hostname or ip address such as {HOSTNAME}" />
|
||||||
<small class="form-text text-muted">This will be used as the default host for all applications, and can be changed later via the <a href="http://dokku.viewdocs.io/dokku/configuration/domains/" target="_blank"><code>dokku domains:set-global</code></a> command.</small>
|
<small class="form-text text-muted">This will be used as the default host for all applications, and can be changed later via the <a href="https://dokku.com/docs/configuration/domains/" target="_blank"><code>dokku domains:set-global</code></a> command.</small>
|
||||||
</div>
|
</div>
|
||||||
<div class="form-check">
|
<div class="form-check">
|
||||||
<input class="form-check-input" type="checkbox" id="vhost" name="vhost" value="true">
|
<input class="form-check-input" type="checkbox" id="vhost" name="vhost" value="true">
|
||||||
@@ -406,7 +406,7 @@ PAGE = """
|
|||||||
result.classList.add("text-success");
|
result.classList.add("text-success");
|
||||||
result.textContent = "Success! Redirecting in 3 seconds. .."
|
result.textContent = "Success! Redirecting in 3 seconds. .."
|
||||||
setTimeout(function() {
|
setTimeout(function() {
|
||||||
window.location.href = "http://dokku.viewdocs.io/dokku~{VERSION}/deployment/application-deployment/";
|
window.location.href = "https://dokku.com/docs~{VERSION}/deployment/application-deployment/";
|
||||||
}, 3000);
|
}, 3000);
|
||||||
})
|
})
|
||||||
.catch(function (error) {
|
.catch(function (error) {
|
||||||
|
|||||||
@@ -32,7 +32,7 @@ To extract the backup onto another server, copy the backup to the server and ext
|
|||||||
sudo tar -xzvf path/to/dokku/backup.tar.gz -C /
|
sudo tar -xzvf path/to/dokku/backup.tar.gz -C /
|
||||||
```
|
```
|
||||||
|
|
||||||
At this point, all datastores should be individually started and checked for data integrity. Once this is complete, individual applications can be rebuilt. Please consult the [process management documentation](/docs/deployment/process-management.md#rebuilding-apps) for more information on how to rebuild applications.
|
At this point, all datastores should be individually started and checked for data integrity. Once this is complete, individual applications can be rebuilt. Please consult the [process management documentation](/docs/processes/process-management.md#rebuilding-apps) for more information on how to rebuild applications.
|
||||||
|
|
||||||
## Caveats
|
## Caveats
|
||||||
|
|
||||||
|
|||||||
@@ -33,7 +33,7 @@ More information on supported Docker options can be found here: https://docs.doc
|
|||||||
|
|
||||||
### Add Docker options
|
### Add Docker options
|
||||||
|
|
||||||
Add some options for the deployed/running app and when executing [`dokku run`](/docs/deployment/one-off-processes.md):
|
Add some options for the deployed/running app and when executing [`dokku run`](/docs/processes/one-off-tasks.md):
|
||||||
|
|
||||||
```shell
|
```shell
|
||||||
# Mount a host volume in a Docker container: "-v /host/path:/container/path"
|
# Mount a host volume in a Docker container: "-v /host/path:/container/path"
|
||||||
|
|||||||
@@ -40,7 +40,7 @@ dokku storage:mount node-js-app /var/lib/dokku/data/storage/node-js-app:/storage
|
|||||||
Dokku will then mount the shared contents of `/var/lib/dokku/data/storage/node-js-app` to `/storage` inside the container.
|
Dokku will then mount the shared contents of `/var/lib/dokku/data/storage/node-js-app` to `/storage` inside the container.
|
||||||
|
|
||||||
Once you have mounted persistent storage, you will also need to restart the application. See the
|
Once you have mounted persistent storage, you will also need to restart the application. See the
|
||||||
[process scaling documentation](/docs/deployment/process-management.md) for more information.
|
[process scaling documentation](/docs/processes/process-management.md) for more information.
|
||||||
|
|
||||||
```shell
|
```shell
|
||||||
dokku ps:restart app-name
|
dokku ps:restart app-name
|
||||||
|
|||||||
@@ -22,4 +22,4 @@
|
|||||||
|
|
||||||
- Dockerfiles with `EXPOSE` clauses will get [all **tcp** ports proxied by default](/docs/deployment/methods/dockerfiles.md#exposed-ports)
|
- Dockerfiles with `EXPOSE` clauses will get [all **tcp** ports proxied by default](/docs/deployment/methods/dockerfiles.md#exposed-ports)
|
||||||
- Note that nginx will proxy the same port numbers to listen publicly
|
- Note that nginx will proxy the same port numbers to listen publicly
|
||||||
- UDP ports can be exposed by disabling the [nginx proxy](/docs/advanced-usage/proxy-management.md) with `dokku proxy:disable node-js-app`
|
- UDP ports can be exposed by disabling the [nginx proxy](/docs/networking/proxy-management.md) with `dokku proxy:disable node-js-app`
|
||||||
|
|||||||
@@ -12,11 +12,11 @@
|
|||||||
## Proxy port mapping
|
## Proxy port mapping
|
||||||
|
|
||||||
- You can now configure host -> container proxy port mappings
|
- You can now configure host -> container proxy port mappings
|
||||||
- The UI is handled by the [proxy](/docs/advanced-usage/proxy-management.md) interface plugin by setting the `DOKKU_PROXY_PORT_MAP` config variable in the format of `scheme:host-port:container-port`. The default `nginx-vhosts` proxy plugin supports both the `http` and `https` schemes.
|
- The UI is handled by the [proxy](/docs/networking/proxy-management.md) interface plugin by setting the `DOKKU_PROXY_PORT_MAP` config variable in the format of `scheme:host-port:container-port`. The default `nginx-vhosts` proxy plugin supports both the `http` and `https` schemes.
|
||||||
- Default port mappings
|
- Default port mappings
|
||||||
- buildpack apps will be set to `http:80:5000` and will also include `https:443:5000` if SSL is enabled.
|
- buildpack apps will be set to `http:80:5000` and will also include `https:443:5000` if SSL is enabled.
|
||||||
- dockerfile apps with explicitly exposed ports (i.e. using the `EXPOSE` directive) will be configured with a listener on each exposed port that proxies to the same port of the deployed application container.
|
- dockerfile apps with explicitly exposed ports (i.e. using the `EXPOSE` directive) will be configured with a listener on each exposed port that proxies to the same port of the deployed application container.
|
||||||
- You may override this behavior with the [`proxy:ports-*` commands](/docs/advanced-usage/proxy-management.md) or by directly setting `DOKKU_PROXY_PORT_MAP` with the `config:set` command
|
- You may override this behavior with the [`proxy:ports-*` commands](/docs/networking/proxy-management.md) or by directly setting `DOKKU_PROXY_PORT_MAP` with the `config:set` command
|
||||||
- dockerfile apps without explicitly exposed ports will behave the same as a buildpack app
|
- dockerfile apps without explicitly exposed ports will behave the same as a buildpack app
|
||||||
- NOTE: These defaults **are not** automatically changed on subsequent pushes and must be manipulated with the aforementioned commands
|
- NOTE: These defaults **are not** automatically changed on subsequent pushes and must be manipulated with the aforementioned commands
|
||||||
|
|
||||||
|
|||||||
@@ -6,7 +6,7 @@ We should now properly handle file ownership for mounted directories. This was e
|
|||||||
|
|
||||||
## Restart Policies
|
## Restart Policies
|
||||||
|
|
||||||
If you previously managed container restart policies via docker-options, these can now be managed natively via the built-in `ps` plugin. There is no migration necessary. See the [restart policy documentation](/docs/deployment/process-management.md#restart-policies) for more details.
|
If you previously managed container restart policies via docker-options, these can now be managed natively via the built-in `ps` plugin. There is no migration necessary. See the [restart policy documentation](/docs/processes/process-management.md#restart-policies) for more details.
|
||||||
|
|
||||||
## SSH Keys
|
## SSH Keys
|
||||||
|
|
||||||
|
|||||||
@@ -91,7 +91,7 @@ The following config variables have special meanings and can be set in a variety
|
|||||||
| `DOKKU_EVENTS_LOGFILE` | `$DOKKU_LOGS_DIR/events.log` | `/etc/environment` <br /> `~dokku/.dokkurc` <br /> `~dokku/.dokkurc/*` | Where the events log file is written to. |
|
| `DOKKU_EVENTS_LOGFILE` | `$DOKKU_LOGS_DIR/events.log` | `/etc/environment` <br /> `~dokku/.dokkurc` <br /> `~dokku/.dokkurc/*` | Where the events log file is written to. |
|
||||||
| `DOKKU_APP_NAME` | none | `--app APP` flag | Name of application to work on. Respected by core plugins. |
|
| `DOKKU_APP_NAME` | none | `--app APP` flag | Name of application to work on. Respected by core plugins. |
|
||||||
| `DOKKU_APPS_FORCE_DELETE` | none | `--force` flag | Whether to force delete an application. Also used by other plugins for destructive actions. |
|
| `DOKKU_APPS_FORCE_DELETE` | none | `--force` flag | Whether to force delete an application. Also used by other plugins for destructive actions. |
|
||||||
| `DOKKU_CHECKS_URL` | `http://dokku.viewdocs.io/dokku/deployment/zero-downtime-deploys/` | `/etc/environment` <br /> `~dokku/.dokkurc` <br /> `~dokku/.dokkurc/*` | Url displayed during deployment when no CHECKS file exists. |
|
| `DOKKU_CHECKS_URL` | `https://dokku.com/docs/deployment/zero-downtime-deploys/` | `/etc/environment` <br /> `~dokku/.dokkurc` <br /> `~dokku/.dokkurc/*` | Url displayed during deployment when no CHECKS file exists. |
|
||||||
| `DOKKU_DETACH_CONTAINER` | none | `--detach` flag | Whether to detach a container started via `dokku run`. |
|
| `DOKKU_DETACH_CONTAINER` | none | `--detach` flag | Whether to detach a container started via `dokku run`. |
|
||||||
| `DOKKU_QUIET_OUTPUT` | none | `--quiet` flag | Silences certain header output for `dokku` commands. |
|
| `DOKKU_QUIET_OUTPUT` | none | `--quiet` flag | Silences certain header output for `dokku` commands. |
|
||||||
| `DOKKU_RM_CONTAINER` | none | `dokku config:set` <br /> `--rm-container` flag <br /> `--rm` flag | Whether to keep `dokku run` containers around or not. |
|
| `DOKKU_RM_CONTAINER` | none | `dokku config:set` <br /> `--rm-container` flag <br /> `--rm` flag | Whether to keep `dokku run` containers around or not. |
|
||||||
|
|||||||
@@ -18,7 +18,7 @@ certs:update <app> CRT KEY # Update an SSL Endpoint on an app. Can
|
|||||||
dokku nginx:import-ssl <app> < certs.tar
|
dokku nginx:import-ssl <app> < certs.tar
|
||||||
```
|
```
|
||||||
|
|
||||||
> Adding an ssl certificate before deploying an application will result in port mappings being updated. This may cause issues for applications that use non-standard ports, as those may not be automatically detected. Please refer to the [proxy documentation](/docs/advanced-usage/proxy-management.md) for information as to how to reconfigure the mappings.
|
> Adding an ssl certificate before deploying an application will result in port mappings being updated. This may cause issues for applications that use non-standard ports, as those may not be automatically detected. Please refer to the [proxy documentation](/docs/networking/proxy-management.md) for information as to how to reconfigure the mappings.
|
||||||
|
|
||||||
## Per-application certificate management
|
## Per-application certificate management
|
||||||
|
|
||||||
|
|||||||
@@ -125,7 +125,7 @@ If you need to redeploy or restart your app:
|
|||||||
dokku ps:rebuild ruby-getting-started
|
dokku ps:rebuild ruby-getting-started
|
||||||
```
|
```
|
||||||
|
|
||||||
See the [process scaling documentation](/docs/deployment/process-management.md) for more information on how to manage your app processes.
|
See the [process scaling documentation](/docs/processes/process-management.md) for more information on how to manage your app processes.
|
||||||
|
|
||||||
### Deploying with private Git submodules
|
### Deploying with private Git submodules
|
||||||
|
|
||||||
|
|||||||
@@ -225,7 +225,7 @@ dokku buildpacks:set node-js-app https://github.com/heroku/heroku-buildpack-node
|
|||||||
|
|
||||||
### Specifying commands via Procfile
|
### Specifying commands via Procfile
|
||||||
|
|
||||||
While many buildpacks have a default command that is run when a detected repository is pushed, it is possible to override this command via a Procfile. A Procfile can also be used to specify multiple commands, each of which is subject to process scaling. See the [process scaling documentation](/docs/deployment/process-management.md) for more details around scaling individual processes.
|
While many buildpacks have a default command that is run when a detected repository is pushed, it is possible to override this command via a Procfile. A Procfile can also be used to specify multiple commands, each of which is subject to process scaling. See the [process scaling documentation](/docs/processes/process-management.md) for more details around scaling individual processes.
|
||||||
|
|
||||||
A Procfile is a file named `Procfile`. It should be named `Procfile` exactly, and not anything else. For example, `Procfile.txt` is not valid. The file should be a simple text file.
|
A Procfile is a file named `Procfile`. It should be named `Procfile` exactly, and not anything else. For example, `Procfile.txt` is not valid. The file should be a simple text file.
|
||||||
|
|
||||||
@@ -246,7 +246,7 @@ worker: env QUEUE=* bundle exec rake resque:work
|
|||||||
importantworker: env QUEUE=important bundle exec rake resque:work
|
importantworker: env QUEUE=important bundle exec rake resque:work
|
||||||
```
|
```
|
||||||
|
|
||||||
The `web` process type holds some significance in that it is the only process type that is automatically scaled to `1` on the initial application deploy. See the [process scaling documentation](/docs/deployment/process-management.md) for more details around scaling individual processes.
|
The `web` process type holds some significance in that it is the only process type that is automatically scaled to `1` on the initial application deploy. See the [process scaling documentation](/docs/processes/process-management.md) for more details around scaling individual processes.
|
||||||
|
|
||||||
|
|
||||||
### `curl` build timeouts
|
### `curl` build timeouts
|
||||||
|
|||||||
@@ -78,7 +78,7 @@ dokku tags:deploy node-js-app v1
|
|||||||
-----> Deploying node-js-app (dokku/node-js-app:v1)...
|
-----> Deploying node-js-app (dokku/node-js-app:v1)...
|
||||||
-----> Running pre-flight checks
|
-----> Running pre-flight checks
|
||||||
For more efficient zero downtime deployments, create a file CHECKS.
|
For more efficient zero downtime deployments, create a file CHECKS.
|
||||||
See http://dokku.viewdocs.io/dokku/deployment/zero-downtime-deploys/ for examples
|
See https://dokku.com/docs/deployment/zero-downtime-deploys/ for examples
|
||||||
CHECKS file not found in container: Running simple container check...
|
CHECKS file not found in container: Running simple container check...
|
||||||
-----> Waiting for 10 seconds ...
|
-----> Waiting for 10 seconds ...
|
||||||
-----> Default container check successful!
|
-----> Default container check successful!
|
||||||
@@ -168,4 +168,4 @@ ssh my.dokku.host "dokku tags:create test-app previous; dokku tags:deploy test-a
|
|||||||
## Related articles
|
## Related articles
|
||||||
- [Setting up persistent storage](/docs/advanced-usage/persistent-storage.md)
|
- [Setting up persistent storage](/docs/advanced-usage/persistent-storage.md)
|
||||||
- [Defining environment variables](/docs/configuration/environment-variables.md)
|
- [Defining environment variables](/docs/configuration/environment-variables.md)
|
||||||
- [Setting up the ports](/docs/advanced-usage/proxy-management.md)
|
- [Setting up the ports](/docs/networking/proxy-management.md)
|
||||||
|
|||||||
@@ -217,19 +217,19 @@ dokku checks:run APP
|
|||||||
-----> Running pre-flight checks
|
-----> Running pre-flight checks
|
||||||
-----> Running checks for app (APP.web.1)
|
-----> Running checks for app (APP.web.1)
|
||||||
For more efficient zero downtime deployments, create a file CHECKS.
|
For more efficient zero downtime deployments, create a file CHECKS.
|
||||||
See http://dokku.viewdocs.io/dokku/checks-examples.md for examples
|
See https://dokku.com/docs/deployment/zero-downtime-deploys/ for examples
|
||||||
CHECKS file not found in container: Running simple container check...
|
CHECKS file not found in container: Running simple container check...
|
||||||
-----> Waiting for 10 seconds ...
|
-----> Waiting for 10 seconds ...
|
||||||
-----> Default container check successful!
|
-----> Default container check successful!
|
||||||
-----> Running checks for app (APP.web.2)
|
-----> Running checks for app (APP.web.2)
|
||||||
For more efficient zero downtime deployments, create a file CHECKS.
|
For more efficient zero downtime deployments, create a file CHECKS.
|
||||||
See http://dokku.viewdocs.io/dokku/checks-examples.md for examples
|
See https://dokku.com/docs/deployment/zero-downtime-deploys/ for examples
|
||||||
CHECKS file not found in container: Running simple container check...
|
CHECKS file not found in container: Running simple container check...
|
||||||
-----> Waiting for 10 seconds ...
|
-----> Waiting for 10 seconds ...
|
||||||
-----> Default container check successful!
|
-----> Default container check successful!
|
||||||
-----> Running checks for app (APP.worker.1)
|
-----> Running checks for app (APP.worker.1)
|
||||||
For more efficient zero downtime deployments, create a file CHECKS.
|
For more efficient zero downtime deployments, create a file CHECKS.
|
||||||
See http://dokku.viewdocs.io/dokku/checks-examples.md for examples
|
See https://dokku.com/docs/deployment/zero-downtime-deploys/ for examples
|
||||||
CHECKS file not found in container: Running simple container check...
|
CHECKS file not found in container: Running simple container check...
|
||||||
-----> Waiting for 10 seconds ...
|
-----> Waiting for 10 seconds ...
|
||||||
-----> Default container check successful!
|
-----> Default container check successful!
|
||||||
@@ -245,7 +245,7 @@ dokku checks:run node-js-app worker
|
|||||||
-----> Running pre-flight checks
|
-----> Running pre-flight checks
|
||||||
-----> Running checks for app (APP.worker.1)
|
-----> Running checks for app (APP.worker.1)
|
||||||
For more efficient zero downtime deployments, create a file CHECKS.
|
For more efficient zero downtime deployments, create a file CHECKS.
|
||||||
See http://dokku.viewdocs.io/dokku/checks-examples.md for examples
|
See https://dokku.com/docs/deployment/zero-downtime-deploys/ for examples
|
||||||
CHECKS file not found in container: Running simple container check...
|
CHECKS file not found in container: Running simple container check...
|
||||||
-----> Waiting for 10 seconds ...
|
-----> Waiting for 10 seconds ...
|
||||||
-----> Default container check successful!
|
-----> Default container check successful!
|
||||||
@@ -261,7 +261,7 @@ dokku checks:run node-js-app web.2
|
|||||||
-----> Running pre-flight checks
|
-----> Running pre-flight checks
|
||||||
-----> Running checks for app (APP.web.2)
|
-----> Running checks for app (APP.web.2)
|
||||||
For more efficient zero downtime deployments, create a file CHECKS.
|
For more efficient zero downtime deployments, create a file CHECKS.
|
||||||
See http://dokku.viewdocs.io/dokku/checks-examples.md for examples
|
See https://dokku.com/docs/deployment/zero-downtime-deploys/ for examples
|
||||||
CHECKS file not found in container: Running simple container check...
|
CHECKS file not found in container: Running simple container check...
|
||||||
-----> Waiting for 10 seconds ...
|
-----> Waiting for 10 seconds ...
|
||||||
-----> Default container check successful!
|
-----> Default container check successful!
|
||||||
|
|||||||
@@ -4,7 +4,7 @@ If you’re stuck, there are a number of places you can get help:
|
|||||||
|
|
||||||
## The Official Dokku Website
|
## The Official Dokku Website
|
||||||
|
|
||||||
- [http://dokku.viewdocs.io/dokku/](/docs/)
|
- [https://dokku.com/docs/](/docs/)
|
||||||
|
|
||||||
The Official Dokku website is always a great place to visit. It features links to oft-used developer tools, community plugins, and guides on using Dokku.
|
The Official Dokku website is always a great place to visit. It features links to oft-used developer tools, community plugins, and guides on using Dokku.
|
||||||
|
|
||||||
|
|||||||
@@ -136,7 +136,7 @@ For buildpack deployments, your application *must* respect the `PORT` environmen
|
|||||||
|
|
||||||
> Changed as of 0.5.0
|
> Changed as of 0.5.0
|
||||||
|
|
||||||
Dokku's default proxy implementation - nginx - supports HTTP and GRPC request proxying. At this time, we do not support proxying plain TCP or UDP ports. UDP ports can be exposed by disabling the nginx proxy with `dokku proxy:disable myapp`. If you would like to investigate alternative proxy methods, please refer to our [proxy management documentation](/docs/advanced-usage/proxy-management.md).
|
Dokku's default proxy implementation - nginx - supports HTTP and GRPC request proxying. At this time, we do not support proxying plain TCP or UDP ports. UDP ports can be exposed by disabling the nginx proxy with `dokku proxy:disable myapp`. If you would like to investigate alternative proxy methods, please refer to our [proxy management documentation](/docs/networking/proxy-management.md).
|
||||||
|
|
||||||
#### Applications using EXPOSE
|
#### Applications using EXPOSE
|
||||||
|
|
||||||
|
|||||||
@@ -217,8 +217,6 @@
|
|||||||
</dd>
|
</dd>
|
||||||
</dl>
|
</dl>
|
||||||
<hr>
|
<hr>
|
||||||
|
|
||||||
Free document hosting provided by <a href="http://progrium.viewdocs.io/viewdocs/">Viewdocs</a>.
|
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
|
|
||||||
|
|||||||
@@ -65,7 +65,7 @@ scheduler-docker-local-pre-deploy-precheck() {
|
|||||||
|
|
||||||
dokku_log_info2 "Processing deployment checks"
|
dokku_log_info2 "Processing deployment checks"
|
||||||
if [[ ! -s "${CHECKS_FILE}" ]]; then
|
if [[ ! -s "${CHECKS_FILE}" ]]; then
|
||||||
local CHECKS_URL="${DOKKU_CHECKS_URL:-http://dokku.viewdocs.io/dokku/deployment/zero-downtime-deploys/}"
|
local CHECKS_URL="${DOKKU_CHECKS_URL:-https://dokku.com/docs/deployment/zero-downtime-deploys/}"
|
||||||
dokku_log_verbose "No CHECKS file found. Simple container checks will be performed."
|
dokku_log_verbose "No CHECKS file found. Simple container checks will be performed."
|
||||||
dokku_log_verbose "For more efficient zero downtime deployments, create a CHECKS file. See ${CHECKS_URL} for examples"
|
dokku_log_verbose "For more efficient zero downtime deployments, create a CHECKS file. See ${CHECKS_URL} for examples"
|
||||||
fi
|
fi
|
||||||
|
|||||||
@@ -6,7 +6,7 @@
|
|||||||
"express",
|
"express",
|
||||||
"testing"
|
"testing"
|
||||||
],
|
],
|
||||||
"website": "http://dokku.viewdocs.io/dokku/",
|
"website": "https://dokku.com/docs/",
|
||||||
"repository": "https://github.com/dokku/dokku",
|
"repository": "https://github.com/dokku/dokku",
|
||||||
"logo": "https://raw.githubusercontent.com/dokku/dokku/master/docs/assets/dokku.png",
|
"logo": "https://raw.githubusercontent.com/dokku/dokku/master/docs/assets/dokku.png",
|
||||||
"scripts": {
|
"scripts": {
|
||||||
|
|||||||
@@ -1,7 +1,7 @@
|
|||||||
{
|
{
|
||||||
"name": "Sample go app",
|
"name": "Sample go app",
|
||||||
"description": "Used in dokku's test suite",
|
"description": "Used in dokku's test suite",
|
||||||
"website": "http://dokku.viewdocs.io/dokku/",
|
"website": "https://dokku.com/docs/",
|
||||||
"repository": "https://github.com/dokku/dokku",
|
"repository": "https://github.com/dokku/dokku",
|
||||||
"logo": "https://raw.githubusercontent.com/dokku/dokku/master/docs/assets/dokku.png",
|
"logo": "https://raw.githubusercontent.com/dokku/dokku/master/docs/assets/dokku.png",
|
||||||
"scripts": {
|
"scripts": {
|
||||||
|
|||||||
@@ -1,7 +1,7 @@
|
|||||||
{
|
{
|
||||||
"name": "Sample go app",
|
"name": "Sample go app",
|
||||||
"description": "Used in dokku's test suite",
|
"description": "Used in dokku's test suite",
|
||||||
"website": "http://dokku.viewdocs.io/dokku/",
|
"website": "https://dokku.com/docs/",
|
||||||
"repository": "https://github.com/dokku/dokku",
|
"repository": "https://github.com/dokku/dokku",
|
||||||
"logo": "https://raw.githubusercontent.com/dokku/dokku/master/docs/assets/dokku.png",
|
"logo": "https://raw.githubusercontent.com/dokku/dokku/master/docs/assets/dokku.png",
|
||||||
"scripts": {
|
"scripts": {
|
||||||
|
|||||||
@@ -6,7 +6,7 @@
|
|||||||
"express",
|
"express",
|
||||||
"testing"
|
"testing"
|
||||||
],
|
],
|
||||||
"website": "http://dokku.viewdocs.io/dokku/",
|
"website": "https://dokku.com/docs/",
|
||||||
"repository": "https://github.com/dokku/dokku",
|
"repository": "https://github.com/dokku/dokku",
|
||||||
"logo": "https://raw.githubusercontent.com/dokku/dokku/master/docs/assets/dokku.png",
|
"logo": "https://raw.githubusercontent.com/dokku/dokku/master/docs/assets/dokku.png",
|
||||||
"scripts": {
|
"scripts": {
|
||||||
|
|||||||
Reference in New Issue
Block a user