Asking for help

Note that it is our policy to close issues that:

• Cannot be replicated.
• Are issues caused by some non-standard configuration we cannot work around/support.
• Have not been responded to with more information in 1-3 weeks.

Keep in mind that while we will always work with our users to debug issues where possible, dokku is an open-source project with no official funding involved, and thus we may not always be able to help our users fully/as soon as they need help. That said, hopefully we can help with any and all issues, and at the same time improve the dokku experience both for existing and future users, as well as developers and maintainers.

Invariably, users will ask for help/support in our issue tracker. We've nominally decided that this one of the correct places to do so (the other being our irc channel). The following is a template to show users when they are asking for help but have not included all the information necessary. Please copy-paste this into issues and then label the issue as needs more info.

---

When reporting issues, the dokku team will need more information to help debug problems. If possible please follow the following template:

    Description of problem:


    Output of the following commands

    - `uname -a`:
    - `free -m`:
    - `docker version`:
    - `docker -D info`:
    - `docker run -ti gliderlabs/herokuish:latest herokuish version`:
    - `dokku version`:
    - `dokku plugin`:
    - `docker inspect CONTAINER_ID` (if applicable):
      (BEWARE: `docker inspect` will print environment variables for some commands, be sure you're not exposing any sensitive information when posting issues. You may replace these values with XXXXXXX):
    - `cat /home/dokku/<app>/nginx.conf` (if applicable):
    - Link to the exact repository being deployed (if possible/applicable):
    - If a deploy is failing:
      - the type of application being deployed (node, php, python, ruby, etc.)
      - whether or not you have a `Dockerfile` in the root of your repository
      - if using buildpacks, which custom buildpacks are in use
    - Output of failing dokku commands after running `dokku trace on`
      (BEWARE: `trace on` will print environment variables for some commands, be sure you're not exposing any sensitive information when posting issues. You may replace these values with XXXXXXX):

    Environment details (AWS, VirtualBox, physical, etc.):

    How was dokku installed?:

    How reproducible:


    Steps to Reproduce:
    1.
    2.
    3.

    Actual Results:


    Expected Results:


    Additional info: