1. If you need to restart your server because patches, then you restart it. :)
2. Backups: AFAIK you can simply just backup /home/user that runs GitBucket. "To upgrade GitBucket, only replace gitbucket.war. All GitBucket data is stored in HOME/.gitbucket. So if you want to back up GitBucket data, copy this directory to the other disk."
3. "Since it's Java ... therefore security" yeah, you need to keep it updated, same goes for ALL software. Luckily I'm using an enterprise class distro which provides timely security updates and pays particular attention to Java (RHEL/CentOS).
Nothing is ever "simple", but running stuff yourself is not as hard as many people think, you just need to get a bit involved.
1. If you need to restart your server because patches, then you restart it. :)
2. Backups: AFAIK you can simply just backup /home/user that runs GitBucket. "To upgrade GitBucket, only replace gitbucket.war. All GitBucket data is stored in HOME/.gitbucket. So if you want to back up GitBucket data, copy this directory to the other disk."
3. "Since it's Java ... therefore security" yeah, you need to keep it updated, same goes for ALL software. Luckily I'm using an enterprise class distro which provides timely security updates and pays particular attention to Java (RHEL/CentOS).
Nothing is ever "simple", but running stuff yourself is not as hard as many people think, you just need to get a bit involved.