Describe the bug
Documentation is very lacking. 'Custom installation' starts with building Go applications and then there are references to files that do not exist and after that it goes to instruct using files and parameters that were used for PgWatch2. Neither code nor --help doesn't reveal what parameters should be used to set up non-docker installations.
To Reproduce
Steps to reproduce the behavior:
- Go to 'Custom installation'
- Try to follow or set up using it
Expected behavior
Documentation to have correct information.
Additional context
Sample startup scripts can be found at /etc/pgwatch/startup-scripts/pgwatch.service or online here. Note that they are OS agnostic and might need some light adjustment of paths, etc - so always test them out.
Nope, nope, nope. Just doesn't exist in those locations.
Describe the bug
Documentation is very lacking. 'Custom installation' starts with building Go applications and then there are references to files that do not exist and after that it goes to instruct using files and parameters that were used for PgWatch2. Neither code nor --help doesn't reveal what parameters should be used to set up non-docker installations.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Documentation to have correct information.
Additional context
Nope, nope, nope. Just doesn't exist in those locations.