mirror of
https://github.com/dokku/dokku.git
synced 2025-12-29 00:25:08 +01:00
730e8f73d4
- reorder things to make it clearer to the user what they are filing - use headers for various sections - separate the `dokku report` section to increase its importance [ci skip]
1.8 KiB
1.8 KiB
If you need help figuring out how to use a specific buildpack, or are having issues using multiple buildpacks, please see our irc or slack channels. Issues pertaining to buildpacks may be closed and locked.
Description of problem
How reproducible
Steps to Reproduce
Actual Results
Expected Results
Environment Information
dokku report APP_NAME output
This is required! Issues missing this information may be closed
For problems affecting all applications, the report output for a broken application is useful for our debugging. You may also run
dokku reportwithout any arguments to display the top-level reporting information.
How (deb/make/rpm) and where (AWS, VirtualBox, physical, etc.) was Dokku installed?:
Additional information
docker inspect CONTAINER_ID(if applicable): (BEWARE:docker inspectwill 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(BEWARE:trace onwill 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):