DOC: section for troubleshooting and offline installation in setup readme

This is an update of the documentation as proposed in #142 (closed) .

I suggest to check and review:

• Please test whether the setup described in "Installation without or with restricted internet connection on the host system" actually works. I'm a bit sceptical that it solves all maven related issues. Can we maybe create a unit test for that?
• Is it ok to have external sources like stackoverflow, etc. in that document?
• I have never tried the CAP_NET_BIND_SERVICE setup. Has anyone? Is it worth exploring that option? Should it be mentioned there?
• Can we add a description for the iptables setup? (Maybe open a new issue for that.)

mentioned in issue #142 (closed)

mentioned in issue #158 (closed)

assigned to @henrik and unassigned @timm

removed review request for @daniel and @timm

mentioned in issue #162 (closed)

@henrik Any updates here? Is an issue missing for this task?

added 78 commits

• 3594edcb...d2946ed0 - 77 commits from branch dev
• 0b0f0b21 - Merge branch 'dev' into f-doc-troubleshooting

Compare with previous version

added 1 commit

• 5e5bbb6f - REVIEW: some minor changes in README_SETUP

Compare with previous version

marked the checklist item Please test whether the setup described in "Installation without or with restricted internet connection on the host system" actually works. I'm a bit sceptical that it solves all maven related issues. Can we maybe create a unit test for that? as completed

marked the checklist item Is it ok to have external sources like stackoverflow, etc. in that document? as completed

marked the checklist item I have never tried the CAP_NET_BIND_SERVICE setup. Has anyone? Is it worth exploring that option? Should it be mentioned there? as completed

marked the checklist item Can we add a description for the iptables setup? (Maybe open a new issue for that.) as completed

Final remarks:

1. Tested. Works
2. External resources are ok (esp. stackexchange)
3. We do not have the time to explore different solutions. One work-around is enough. When anyone cannot use it, they may add their recipe to the troubleshooting section though. This applies to ip-tables solutions, reverse-proxy solutions and CAP_NET_BIND_SERVICE.

mentioned in commit 6deab58a

merged

approved this merge request