Files
dokku/ISSUE_TEMPLATE.md

48 lines
1.4 KiB
Markdown
Raw Normal View History

2016-02-17 12:58:35 -05:00
Description of problem:
Output of the following commands
2017-01-16 18:25:20 +10:30
<!-- If you're running 0.4.10+ just use dokku report-->
2016-02-17 12:58:35 -05:00
- `uname -a`:
- `free -m`:
- `docker version`:
- `docker -D info`:
2016-02-14 18:43:40 -08:00
- `sigil -v`:
2016-02-17 12:58:35 -05:00
- `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 or behaving unexpectedly:
- Application name
- The type of application being deployed (node, php, python, ruby, etc.)
- If using buildpacks, which custom buildpacks are in use
- If using a `Dockerfile`, the contents of that file
- If it exists, the contents of your `Procfile`.
- Output of failing Dokku commands after running `dokku trace on`
2016-02-17 12:58:35 -05:00
(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?:
2016-02-17 12:58:35 -05:00
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual Results:
Expected Results:
Additional info: