Restart server
You can do this simply by:
| Code Block |
|---|
./install.sh |
Or by hand by:
| Code Block |
|---|
| Info |
You can not use "docker-compose up" as install.sh will merge two docker-compose file into one depending on the setup you have defined in piplanning.cfg |
Stop the server
| Code Block |
|---|
docker-compose down |
Update configuration (piplanning.cfg)
- Update the configuration file piplanning.cfg
Code Block ./install.sh
Inspect log-files
Log files are stored in the logs folder under the pi-server (docker). You can follow them by tail -f <logfile>.
- crossbar/node.log : Logs of the crossbar node.Check this log if communication between the micro-services fails
- authserver.log
- pi-jira-listener.log : If you have trouble with Jira-webhooks and you think they do not reach the piplanninserver, check here for errors.
- piplanningserver.log
If you want closer details what a specific team was doing check out data/authserver/actionlogsTo inspect the logs you can grab the logs of the individual containers by
| Code Block |
|---|
docker logs -f <container-name or ID> |
To check for errors regarding the ALM-sync:
- pialmsync container
Data storage / backups
All data and settings from the teams will be saved in the data folder. This data persists over updates.
| Info |
|---|
Make sure you do regularly backups of the data folder. |
