Idea #17344
Updated by Tom Clegg almost 2 years ago
Resolve outstanding issues: * Add Workbench2 (should be optional for @arvados-server boot@, like #17343) * Install and activate systemd unit as part of @arvados-server init@ * Avoid leaving system in inconvenient state if @arvados-server init@ doesn't go well * Set up arvados/jobs docker image so diagnostics container can run Add symlinks /usr/local/bin/arvados-* → /var/lib/arvados/bin/arvados-* * Document firewall / accessible port requirements * Sanity-check dns/firewall early Configure Nginx to use TLS certificates in @arvados-server init@ * Remove setup roadblocks (e.g., use PAM instead of Google API keys) /var/lib/acme/, if they exist