@Robert_Johnson you can just change the name. I’m using ghost:6-alpine. You can continue using your nginx frontend (npm?) but you’ll need to add 3 custom location blocks to forward to the upstream activitypub service at ap.ghost.org.
@andrecalil if you’re using coolify, you’ll need to add extra routing definitions to your traefik or caddy config. Here’s what I used for traefik: Question: How to define custom location block (e.g. /.ghost/*) via Traefik instead of Caddy? - #3 by eddywashere
Ignore the following, I missed the fact that there is the traffic-analytics service actually running.
I have not added the analytics to my setup, but maybe sharing my plan will help. Portainer and Coolify don’t really handle one off tasks well but you could add a separate stack for just the analytics tasks that need to be run. From there you can enable or disable each service and command to run for a one-off deployment or run of the task. I believe each service block will need a restart policy set to no or restart: no. From there, you can comment out the blocks not needed or set the depends on in a way to run properly.