Remove deprecated calls

This commit is contained in:
Jose Diaz-Gonzalez
2015-09-07 13:41:05 -04:00
committed by Jose Diaz-Gonzalez
parent aaae9adac3
commit b3ddcbed53
8 changed files with 12 additions and 53 deletions

View File

@@ -21,10 +21,10 @@ Enabling dokku events logger
Dokku will then write log entries to ``/var/log/syslog`` as well as a Dokku-specific logs sub-directory ``/var/log/dokku/events.log``, which can be easily displayed with the command `dokku events`:
```
Jul 3 16:09:48 dokku.me dokku[127630]: INVOKED: pre-release-buildstep( pythonapp )
Jul 3 16:09:48 dokku.me dokku[127630]: INVOKED: pre-release-buildpack( pythonapp )
Jul 3 16:10:02 dokku.me dokku[128095]: INVOKED: docker-args-run( rubyapp )
Jul 3 16:10:02 dokku.me dokku[128114]: INVOKED: docker-args-run( nhl )
Jul 3 16:10:03 dokku.me dokku[128136]: INVOKED: post-release-buildstep( pythonapp )
Jul 3 16:10:03 dokku.me dokku[128136]: INVOKED: post-release-buildpack( pythonapp )
Jul 3 16:10:03 dokku.me dokku[128195]: INVOKED: pre-deploy( pythonapp )
Jul 3 16:10:23 dokku.me dokku[129253]: INVOKED: docker-args-deploy( pythonapp )
Jul 3 16:10:24 dokku.me dokku[129337]: INVOKED: bind-external-ip( pythonapp )
@@ -47,10 +47,10 @@ docker-args-build
pre-delete
post-deploy
receive-app
pre-release-buildstep
pre-release-buildpack
nginx-pre-reload
docker-args-deploy
post-build-buildstep
post-build-buildpack
post-domains-update
post-release-dockerfile
check-deploy
@@ -63,10 +63,10 @@ bind-external-ip
pre-deploy
post-delete
dependencies
pre-build-buildstep
pre-build-buildpack
docker-args-run
pre-build-dockerfile
post-release-buildstep
post-release-buildpack
post-build-dockerfile
pre-release-dockerfile
update

View File

@@ -13,9 +13,6 @@ ps:start <app> Start app container(s)
ps:stop <app> Stop app container(s)
```
*NOTE*: As of v0.3.14, `dokku deploy:all` in now deprecated by `ps:restartall` and will be removed in a future version.
## Scaling
Dokku allows you to run multiple process types at different container counts. For example, if you had an app that contained 1 web app listener and 1 background job processor, dokku can, spin up 1 container for each process type defined in the Procfile. By default we will only start the web process. However, if you wanted 2 job processors running simultaneously, you can modify this behavior in a few ways.