Open KonradHoeffner opened 9 months ago
I am not sure how we could integrate this into the current setup. The frontend is deployed as a standalone Docker image and therefore requires a built-in web server. And Caddy is used to provide a single endpoint to access all the TOP services.
Perhaps we could replace Nginx in the frontend image with Caddy, drop the additional Caddy service and mount a modified Caddyfile into the frontend?
Perhaps we could replace Nginx in the frontend image with Caddy, drop the additional Caddy service and mount a modified Caddyfile into the frontend?
This would make the frontend mandatory for the deployment of the backend.
Wouldn't it be much simpler, more elegant, more stable and easier to debug if we just had one webserver instead of using nginx for the Frontend and then redirecting that with Caddy? Can we just use Caddy to serve the frontend directly?