Fahar - when you run
bench start you are within the process launched by the command and can see all *nix stdout/stderr output. When using the production install, bench uses
supervisor to manage processes. Logs are stored in
path/to/frappe-bench/logs as far as I can tell. You could tail the logs using
tail -f log_file_1 log_file_2 to monitor the logs and see output.
Alternatively, you could stop supervisor processes with
supervisorctl stop all if this is only a testing server and run
bench start manually.
The workflow we are following and one I would recommend is:
- Do all code/doctype development on a local development machine and monitor
bench start output for messages
- Push all code to git
- On the deployment server, use
bench get-app git_url to get app and install requirements +
bench --site site_name install-app app_name to install the app to a site