[{"_1":2,"_173":-5,"_174":-5},"loaderData",{"_3":4,"_17":18,"_25":26,"_148":149},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7,"_13":14,"_15":16},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","theme","system","contrast","normal","routes/_layout",{"_19":-5,"_20":21,"_22":21,"_23":11,"_24":21},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.r.$namespace.$reponame",{"_27":28,"_29":-5,"_30":11,"_31":11,"_32":33,"_34":35,"_36":-5,"_37":11,"_38":39,"_88":-5,"_89":90,"_137":-5,"_138":11,"_139":21,"_140":11,"_141":-5,"_142":11,"_143":-5,"_144":145,"_146":91,"_147":-7},"canonicalUrl","https://hub.docker.com/r/fteychene/dokku-alt/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","fteychene","reponame","dokku-alt","cloudBuildSource","isAutobuildsAvailable","repo",{"_40":41,"_42":43,"_45":46,"_47":48,"_49":11,"_50":51,"_52":53,"_54":55,"_57":35,"_32":33,"_58":59,"_60":-5,"_61":62,"_63":64,"_65":66,"_67":-5,"_68":62,"_69":70,"_71":11,"_72":33,"_73":74,"_79":21,"_80":81,"_85":33,"_86":87},"categories",[],"content_types",[44],"image","date_registered","2015-12-21T21:38:47.135004Z","description","Dokku-alt migrated to docker-engine instead of lxc-docker","is_private","last_updated","2016-05-11T20:35:55.221792Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[56],"application/vnd.docker.distribution.manifest.v1+prettyjws","name","pull_count",1283,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","# Dokku Alternative\n\n[![Join the chat at https://gitter.im/dokku-alt/dokku-alt](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/dokku-alt/dokku-alt?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)\n\nDocker powered mini-Heroku. The smallest PaaS implementation you've ever seen. It's a fork of the original [dokku](https://github.com/progrium/dokku). The idea behind this fork is to provide complete solution with plugins covering most use-cases which are stable and well tested.\n\n## Features\n\n* Debian-based installation and upgrade!\n* Git deploy\n* Built-in support for MariaDB, PostgreSQL, MongoDB and Redis databases\n* Built-in support for Dockerfile\n* Built-in support for service-only applications\n* Built-in support for domains and redirects\n* Built-in support for TLS and wildcard certificates\n* Built-in support for Docker-args and container persistent volumes\n* Built-in support for container's TOP\n* Built-in support for foreman-based Procfile\n* Data volumes with host-based volumes\n* Preboot / zero-downtime deploy\n* Enter and exec commands in already running containers\n* Access-control: deploy only keys\n* Create-only application\n* HTTP-Basic Auth support\n* Simple SSL commands\n* SPDY and HSTS\n* Configure NGINX listen address and proxy read timeout\n* Custom buildstep image\n* Support better image tagging (yet compatible with dokku)\n* Support for running buildstep-based applications as non-root user\n* Integration with dokku-alt-manager (https://github.com/romaninsh/dokku-alt-manager)\n* Run dokku-alt in service in docker container (BETA)\n\n### Planned features:\n\n* Nginx proxy in container with automatic service reload\n* Support for RabbitMQ and Memcached\n* Support for custom nginx templates\n* Support for application scaling\n* Support for `CHECKS` as described in https://labnotes.org/zero-downtime-deploy-with-dokku/\n* Full and incremental backup\n* Application migration\n\n## Requirements\n\nAssumes that you use Ubuntu 14.04 LTS right now. Ideally, you should have a domain ready to point to your host. It's designed for and is probably best to use a fresh VM. The debian package will install everything it needs.\n\n## Installing\n\n $ sudo bash -c \"$(curl -fsSL https://raw.githubusercontent.com/dokku-alt/dokku-alt/master/bootstrap.sh)\"\n\n## Installing (with force-yes)\n\nSometimes you may want to install dokku-alt in a completely non-interactive way. Now you can do it. Simply boostrap.sh without terminal:\n\n $ sudo bash -c \"$(curl -fsSL https://raw.githubusercontent.com/dokku-alt/dokku-alt/master/bootstrap.sh)\" < /dev/null\n\n## Configuring\n\nIf you use the bootstrap script from above, at the end it will fireup ruby installation script. Point your browser to `http://:2000/` and finish configuration.\n\nThat's it!\n\n### Manual configuration\n\nSet up a domain and a wildcard domain pointing to that host. Make sure `/home/dokku/VHOST` is set to this domain. By default it's set to whatever hostname the host has. This file is only created if the hostname can be resolved by dig (`dig +short $(hostname -f)`). Otherwise you have to create the file manually and set it to your preferred domain. If this file still is not present when you push your app, dokku will publish the app with a port number (i.e. `http://example.com:49154` - note the missing subdomain).\n\nYou'll have to add a public key associated with a username by doing something like this from your local machine:\n\n $ cat ~/.ssh/id_rsa.pub | ssh dokku.me sudo dokku access:add\n\n## Upgrade and beta releases\n\nUnlike `dokku`, this script uses the debian packaging system (deb). To upgrade to the latest version, simply execute: `sudo apt-get update && sudo apt-get install dokku-alt`.\n\nAlongside the normal (stable) releases we distribute as well beta (bleeding edge). To switch to beta simply execute: `sudo apt-get update && sudo apt-get install dokku-alt-beta`. It will replace the stable dokku-alt and switch to beta.\n\n## Migration from dokku\n\nIt should be possible, it should mostly work, but it's not tested and advised. VPS's are very cheap this days so fire-up new machine and setup `dokku-alt` from scratch.\n\n## Deploy an App\n\nNow you can deploy apps on your Dokku. Let's deploy the [Heroku Node.js sample app](https://github.com/heroku/node-js-sample). All you have to do is add a remote to name the app. It's created on-the-fly. Note that you must use the username **dokku**@yourhostname.com:your-repository-name if you used the boostrap.sh script to install dokku-alt.\n\n $ git clone https://github.com/heroku/node-js-sample\n $ cd node-js-sample\n $ git remote add dokku dokku@dokku-alt.com:node-js-app\n $ git push dokku master\n Counting objects: 296, done.\n Delta compression using up to 4 threads.\n Compressing objects: 100% (254/254), done.\n Writing objects: 100% (296/296), 193.59 KiB, done.\n Total 296 (delta 25), reused 276 (delta 13)\n -----> Building node-js-app ...\n Node.js app detected\n -----> Resolving engine versions\n\n ... blah blah blah ...\n\n -----> Application deployed:\n http://node-js-app.progriumapp.com\n\nYou're done!\n\nRight now Buildstep supports buildpacks for Node.js, Ruby, Python, [and more](https://github.com/progrium/buildstep#supported-buildpacks). It's not hard to add more, [go add more](https://github.com/progrium/buildstep#adding-buildpacks)!\nPlease check the documentation for your particular build pack as you may need to include configuration files (such as a Procfile) in your project root.\n\n## Dokku-alt-manager\n\nIt's a web interface to easily manage your dokku-alt instance. To install manager, simply run:\n\n dokku manager:install\n\nYou can enable or disable it anytime:\n\n dokku manager:enable\n dokku manager:disable\n\nOr even uninstall if you prefer command line access (it will also wipe used database):\n\n dokku manager:uninstall\n\n## Dokku-alt as service in Docker container (BETA)\n\nDokku-alt can be run using Docker-in-Docker approach (https://github.com/jpetazzo/dind). It requires you to run the dokku-alt container in privileged mode (with full access to host), because dokku-alt uses its own Docker daemon to serve applications. It's still considered beta, but should be pretty safe solution and robust. It's best to use for play with dokku-alt on other not-supported systems (CentOS, RedHat, Debian) or by simply trying how it works.\n\nAll dokku-alt services (SSH, Nginx, Dokku daemon) are run in container.\n\n### Create persistent data storage\n\n docker run --volume=/home/dokku --volume=/var/lib/docker --name=dokku-alt-data busybox:latest\n\n### Start `dokku-alt` service in container\n\n docker run -d --name=dokku-alt --hostname=my-domain.com --volumes-from=dokku-alt-data --publish=22:22 --publish=80:80 --publish=443:443 --privileged ayufan/dokku-alt:latest\n\nYou can adjust the exposed ports as described in Docker documentation.\n\n### Check `dokku-alt` logs to see if anything started correctly:\n\n docker logs dokku-alt-demo\n\nAt the end, you should see something like this:\n\n dokku.1 | SSH Login:\n dokku.1 | user: root\n dokku.1 | password: lfMUjxYEvqpRRLY6\n dokku.1 | ip: 10.0.42.1 172.17.2.213\n dokku.1 | Starting dokku daemon...\n\nThis is a temporary `root` password to access the container and add your access keys (using `dokku access:add` as described). This password changes every container restart.\n\nTo enter the container shell from the server's terminal (the same which is running `docker` with `dokku-alt`) run ssh:\n\n ssh root@172.17.2.213\n\nIf everything was done right, you should see the container's prompt. By exposing ports in `docker run` to the outside world you can also access `dokku-alt` externally.\n\n### To upgrade container to newer version simply kill old container and rerun your `docker run` command:\n\n docker kill dokku-alt\n docker pull ayufan/dokku-alt:latest\n docker run -d --name=dokku-alt --hostname=my-domain.com --volumes-from=dokku-alt-data --publish=22:22 --publish=80:80 --publish=443:443 --privileged ayufan/dokku-alt:latest\n\n## Dockerfile images\n\nThe key feature of `dokku-alt` is built-in support for Dockerfiles, the docker build process. It allows you to create more advanced and more repetitive application environments.\nTo use `Dockerfile` simply put `Dockerfile` in root of the application, `dokku-alt` will detect it and build application according to specification in `Dockerfile`.\n\nDockerfile-based application can (but not required) expose a web-application port. `dokku-alt` will check if port 80, 8080 or 5000 is exposed. If it is, it will update the assigned vhost and reconfigure nginx to forward all incoming traffic.\n\nUsing Dockerfile, you can build service-only applications. Simply don't expose any public facing ports.\n\nExample Dockerfile application: https://github.com/ayufan/dokku-alt-phpmyadmin\n\n## Nginx and redirects\n\nDokku-alt has built-in support for additional domains and url redirects. By specifying redirects, any client using that address will automatically be redirected to the first domain assigned to the application.\n\n## Remote commands\n\nDokku commands can be run over ssh. Anywhere you would run `dokku `, just run `ssh -t dokku@progriumapp.com `\nThe `-t` is used to request a pty. It is highly recommended to do so.\nTo avoid the need to type the `-t` option each time, simply create/modify a section in the `.ssh/config` on the client side, as follows :\n\n Host progriumapp.com\n RequestTTY yes\n\n## Run a command in the app environment\n\nIt's possible to run commands in the environment of the deployed application:\n\n $ dokku run node-js-app ls -alh\n $ dokku run \n\n## Removing a deployed app\n\nSSH onto the server, then execute:\n\n $ dokku delete myapp\n\n## Create-only application\n\nDokku-alt allows you to create an application before pushing it. It can be useful when you want to specify additional config variables or assign databases. Simply execute:\n\n $ dokku create mynewapp\n\nIt's also possible to disable auto-application creation on push. Add to `~/dokkurc`:\n\n export DOKKU_DISABLE_AUTO_APP_CREATE=1\n\nFrom now on you will have to do `dokku create` before pushing.\n\n## Allowing push-access (deploy only) access for dokku\n\nDokku-alt allows you to add additional public keys to applications. The specific case is to add special deploy-only key, used for example by Countinous Integration (ie. Jenkins). Key added as deploy-only can only be used to `git push` specific application. It will not allowed to execute any `dokku` commands. You can add an ssh key and give it explicit access to one or many applications.\n\nAdd locally:\n\n $ cat .ssh/id_rsa.pub | dokku deploy:allow myapp\n\nAdd key remotely:\n\n $ cat .ssh/id_rsa.pub | ssh dokku@dokku deploy:allow myapp\n\nTo later revoke key execute:\n\n $ dokku deploy:revoke myapp FINGERPRINT\n\nYou can also list all fingerprints allowed to deploy an application:\n\n $ dokku deploy:list myapp\n\nAdd a new admin user:\n\n $ cat .ssh/id_rsa.pub | dokku access:add\n\nRevoke permissions for admin user:\n\n $ dokku access:revoke FINGERPRINT\n\n## Environment variable management\n\nTypically, an application will require some environment variables to run properly. Environment variables may contain private data, such as passwords or API keys, so it is not recommend to store them in your application's repository.\n\nThe `config` plugin provides the following commands to manage your variables:\n```\nconfig - display the config vars for an app \nconfig:get KEY - display a config value for an app \nconfig:set KEY1=VALUE1 [KEY2=VALUE2 ...] - set one or more config vars\nconfig:unset KEY1 [KEY2 ...] - unset one or more config vars\n```\n\n### Available environment variables\n\n* `DOKKU_NGINX_PROXY_READ_TIMEOUT` - allows to override `nginx proxy_read_timeout`. Default value is set to '60s'. For more info please refer to: http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_read_timeout.\n* `DOKKU_ENABLE_HTTP_HOST` - when set to 1, the application will also serve content on HTTP if HTTPS is enabled\n* `DOKKU_BUILDSTEP_IMAGE` - allows you to set a custom buildstep image on per app basis. Image has to be compatible with https://github.com/progrium/buildstep or https://github.com/dokku-alt/progrium-buildstep-dockerfiles. If the images was forked from https://github.com/progrium/buildstep, there might be a small incompatibility: the image is run with `/start` instead of `/start web` as in orginal `dokku`.\n* `DOKKU_START_CMD` - allows you to set a custom start command. The default value is `/start` for buildstep images and ` ` otherwise.\n\n## Image tagging\n\nWhen you successfully deploy an app, you can tag it with a name/version. This lets you quickly roll back to that image in the event of failure in a later deployment.\n\n $ dokku tag:add gitlab v6.9.0\n =====> Tagged latest image of dokku/gitlab as v6.9.0\n $ dokku tag:list gitlab\n REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE\n dokku/gitlab build fc3baf1216d2 4 weeks ago 954.9 MB\n dokku/gitlab latest fc3baf1216d2 4 weeks ago 954.9 MB\n dokku/gitlab release fc3baf1216d2 4 weeks ago 954.9 MB\n dokku/gitlab v6.9.0 fc3baf1216d2 4 weeks ago 954.9 MB\n $ dokku deploy gitlab release <-- it will deploy GIT head\n $ dokku deploy gitlab v6.9.0 <-- it will deploy tagged image\n\n## Databases\n\nDokku-alt has built-in support for all modern database engines: MariaDB (former MySQL), PostgreSQL and MongoDB. The database image will be downloaded and provisioned when first used.\n\nFirst create a database:\n\n $ dokku mariadb:create test-db\n -----> MariaDB database created: test-db\n\nSecond link the database to an app:\n\n $ dokku mariadb:link node-js-sample test-db\n -----> Releasing node-js-sample ...\n -----> Deploying node-js-sample ...\n -----> Shutting down old containers\n =====> Application deployed:\n http://node-js-sample.ayufan.eu\n\nVerify the application environment variables:\n\n $ dokku config node-js-sample\n === node-js-sample config vars ===\n DATABASE_URL: mysql2://node-js-sample:random-password@mariadb:3306/test-db\n\nTo use a different database engine, simply replace `mariadb` with `postgresql` or `mongodb`.\n\n## Preboot / zero-downtime boot\n\nSimilar to functionality provided by https://devcenter.heroku.com/articles/labs-preboot `dokku-alt` supports zero-downtime. To enable zero-downtime deployment, execute command: `dokku preboot:enable APP`. Alongside with preboot, there's a `checks` plugin based on https://labnotes.org/zero-downtime-deploy-with-dokku/. For now, it simply checks if the application started serving requests. If the checks module fails, it will not replace the application.\n\nPreboot and checks can be configured using a few environment variables:\n\n* PREBOOT_WAIT_TIME - number of seconds to wait for container boot (default 5s)\n* PREBOOT_COOLDOWN_TIME - number of seconds to wait finish container request processing (default 30s)\n* DOKKU_CHECKS_WAIT - number of seconds to wait before request retries (default 10s)\n* DOKKU_CHECKS_TIMEOUT - number of seconds to wait for each response (default 20s)\n* DOKKU_CHECKS_RETRY - number of retries (default 3)\n\n## Data volumes\n\nDocker allows you to have persistent data storage. Dokku-alt exposes this feature as Data Volumes. You can create unlimited number of data volumes and any data volume can be attached to unlimited number of apps. Simply create a data volume and specify container paths which you want to be persistant.\n\nFirst, create a data volume:\n\n $ dokku volume:create shared-test-volume /app/logs /app/tmp /app/uploads\n -----> Volume created: volume_data_shared-test-volume\n\nSecond, link the volume to an app:\n\n $ dokku volume:link node-js-sample shared-test-volume\n -----> Volume shared-test-volume linked to an aplication: node-js-sample\n -----> Releasing node-js-sample ...\n -----> Deploying node-js-sample ...\n -----> Shutting down old containers\n =====> Application deployed:\n http://node-js-sample.ayufan.eu\n\nIt is just simple as this.\n\n### Host-based volumes\n\nDokku-alt allows you to bind host-based volumes in a very simple manner. To use this feature, you have to be logged as `root` and then simply type:\n\n dokku volume:create host-based-volume /path/to/host/volume:/path/to/volume/in/container\n\n## HTTP-Basic Auth support\n\nDokku-alt allows you to secure any application with HTTP-Basic Auth. There are a few commands that makes it happen:\n\n htpasswd:add Add http-basic auth user\n htpasswd:disable Remove http-basic Auth\n htpasswd:remove Remove user\n\nIf you want to enable and add a new user, simply type the command below and when prompted, type your password twice:\n\n dokku htpasswd:add myapp myuser\n\nYou can also pipe the password:\n\n echo mypass | dokku htpasswd:add myapp myuser\n\nTo revoke user's permission:\n\n dokku htpasswd:remove myapp\n\nTo remove HTTP-Basic Auth completely:\n\n dokku htpasswd:disable myapp\n\n## TLS support\n\nDokku provides easy TLS support out of the box. To enable TLS connection to your application, copy the `.crt` and `.key` files into the `/home/dokku/:app/ssl` folder (notice, file names should be `server.crt` and `server.key`, respectively). Redeployment of the application will be needed to apply TLS configuration. Once it's redeployed, the application will be accessible by `https://` (redirection from `http://` is applied as well).\n\n## TLS support\n\nDokku-alt extends this even further by allowing you to use command line interface for certificates:\n\n ssl:generate Generate certificate signing request for an APP\n ssl:certificate Pipe signed certifcate with all intermediates for an APP\n ssl:forget Wipes certificate for an APP\n ssl:info Show info about certifcate and certificate request\n ssl:key Pipe private key for an APP\n\nFirst use: `dokku ssl:generate myapp` to generate certificate signing request (CSR). At the end of process you will receive `BEGIN CERTIFICATE REQUEST` which you can ten copy-n-paste to your SSL signer (ie. http://startssl.com).\n\nWhen you receive your signed certificate pipe it with **ALL INTERMEDIATES** to `dokku ssl:certificate myapp`. If done correctly you have SSL enabled for your site.\n\n cat mycert.pem intermediate.pem ca.pem | dokku ssl:certificate myapp\n\nIf it happens that you have already created certificate you can use it, by piping your **UNENCRYPTED** your certificate and your private key:\n\n cat mycert.pem intermediate.pem ca.pem | dokku ssl:certificate myapp\n cat mycert.key | dokku ssl:key myapp\n\nTo view asigned certificate:\n\n dokku ssl:info myapp\n\n## HSTS support\n\nHTTP Strict Transport Security (HSTS) is a web security policy mechanism whereby a web server declares that complying user agents (such as a web browser) are to interact with it using only secure HTTPS connections. Once enabled all further communication will be done over TLS only, there's no revert mechanism. As this is additional security feature you have to do it by hand. To enable HSTS for site use:\n\n dokku config:set myapp DOKKU_ENABLE_HSTS=1\n\n## Serve an app over HTTP as well\n\nBy default `dokku-alt` for all TLS-enabled apps will create redirects which requires user to use `https://`. In some cases it maybe required to allow `http://` access which is potentially insecure. To enable simulatenous HTTP and HTTPS set specific config:\n\n dokku config:set myapp DOKKU_ENABLE_HTTP_HOST=1\n\n## dokkurc Configuration\n\nYou can fine-tune some aspects of Dokku behaviour and its plugins by setting variables in `dokkurc` file placed in Dokku root directory – usually `/home/dokku`. `dokkurc` is sourced by the main `dokku` script.\n\nExample:\n\n export DOKKU_DISABLE_AUTO_APP_CREATE=1\n export BUILDSTEP_IMAGE=\"ayufan/dokku-alt-buildstep:foreman\"\n\n\n### Known configuration variables\n\n* `DOKKU_DISABLE_AUTO_APP_CREATE` – when set to `1`, applications won't be automatically created on push; [see Create only application](#create-only-application).\n* `BUILDSTEP_IMAGE` – buildstep image to be used by Docker, defaults to [`ayufan/dokku-alt-buildstep:foreman`](https://registry.hub.docker.com/u/ayufan/dokku-alt-buildstep/).\n* `MARIADB_IMAGE` – Docker image to be used for MariaDB plugin, defaults to [`ayufan/dokku-alt-mariadb`](https://registry.hub.docker.com/u/ayufan/dokku-alt-mariadb/).\n* `MONGODB_IMAGE` – Docker image to be used for MongoDB plugin, defaults to [`ayufan/dokku-alt-mongodb`](https://registry.hub.docker.com/u/ayufan/dokku-alt-mongodb/).\n* `POSTGRESQL_IMAGE` – Docker image to be used for PostgreSQL plugin, defaults to [`ayufan/dokku-alt-postgresql`](https://registry.hub.docker.com/u/ayufan/dokku-alt-postgresql/).\n* `REDIS_IMAGE` – Docker image to be used for Redis plugin, defaults to [`ayufan/dokku-alt-redis`](https://registry.hub.docker.com/u/ayufan/dokku-alt-redis/).\n* `DOKKU_LISTEN_IPV4` - Set the IPV4 address on which NGINX will listen for requests\n* `DOKKU_LISTEN_IPV6` - Set the IPV6 address on which NGINX will listen for requests\n* `DOKKU_FORCE_ENABLE_HSTS` - Force to enable HSTS header (validity for one year) for all TLS-enabled apps\n* `DOKKU_DISABLE_NGINX_X_FORWARDED` - Disable setting of `X-Forwarded` headers by nginx, useful for CDN installations.\n\n#### MariaDB specific\n\nThese parameters should only be changed when you are using a MariaDB image that has a different setup.\n\n* `MARIADB_PORT` - MariaDB listen port, defaults to `3306`\n* `MARIADB_COMMAND` - MariaDB startup command for Docker, defaults to `/usr/bin/start_mariadb.sh`\n* `MARIADB_CONTAINER_VOLUME` - Where the data volume gets mounted in the MariaDB container, defaults to `/opt/mysql`\n* `MARIADB_CONTAINER_PASSWORD` - Where the password file gets mounted in the MariaDB container, defaults to `/opt/mysql_password`\n\n#### MongoDB specific\n\nThese parameters should only be changed when you are using a MongoDB image that has a different setup.\n\n* `MONGODB_PORT` - MongoDB listen port, defaults to `27017`\n* `MONGODB_COMMAND` - MongoDB startup command for Docker, defaults to `/usr/bin/start_mariadb.sh`\n* `MONGODB_CONTAINER_VOLUME` - Where the data volume gets mounted in the MongoDB container, defaults to `/opt/mongodb`\n* `MONGODB_CONTAINER_PASSWORD` - Where the password file gets mounted in the MongoDB container, defaults to `/opt/mongodb_password`\n\n#### PostgreSQL specific\n\nThese parameters should only be changed when you are using a PostgreSQL image that has a different setup.\n\n* `POSTGRESQL_USER` - PostgreSQL admin user, defaults to `root`\n* `POSTGRESQL_PORT` - PostgreSQL listen port, defaults to `5432`\n* `POSTGRESQL_COMMAND` - PostgreSQL startup command for Docker, defaults to `/usr/bin/start_pgsql.sh`\n* `POSTGRESQL_CONTAINER_VOLUME` - Where the data volume gets mounted in the PostgreSQL container, defaults to `/opt/postgresql`\n* `POSTGRESQL_CONTAINER_PASSWORD` - Where the password file gets mounted in the PostgreSQL container, defaults to `/opt/postgresql_password`\n\n#### Redis specific\n\nThese parameters should only be changed when you are using a Redis image that has a different setup.\n\n* `REDIS_PORT` - Redis listen port, defaults to `6379`\n* `REDIS_COMMAND` - Redis startup command for Docker, defaults to `/usr/bin/start_redis.sh`\n* `REDIS_CONTAINER_VOLUME` - Where the data volume gets mounted in the Redis container, defaults to `/var/lib/redis`\n\n## Help\n\n $ dokku help\n apps:disable Disable specific app\n apps:enable Re-enable specific app\n apps:list List app\n apps:restart Restart specific app (not-redeploy)\n apps:start Stop specific app\n apps:status Status of specific app\n apps:stop Stop specific app\n apps:top [args...] Show running processes\n backup:export [file] Export dokku configuration files\n backup:import [file] Import dokku configuration files\n config display the config vars for an app\n config:get KEY display a config value for an app\n config:set KEY1=VALUE1 [KEY2=VALUE2 ...] set one or more config vars\n config:unset KEY1 [KEY2 ...] unset one or more config vars\n delete Delete an application\n domains:get

fteychene/dokku-alt

Tags for fteychene/dokku-alt