On a fresh DigitalOcean deployment, the services looked all sad like this:
$ systemctl list-units forem*
UNIT LOAD ACTIVE SUB JOB DESCRIPTION
forem-imgproxy.service loaded active running Forem Imgproxy Service
forem-openresty.service loaded inactive dead start Forem OpenResty Service
forem-pod.service loaded active running Forem pod service
forem-postgresql.service loaded active running Forem Postgresql Service
forem-rails.service loaded inactive dead start Forem Rails Service
forem-redis.service loaded active running Forem Redis Service
forem-traefik.service loaded inactive dead start Forem Traefik Service
forem-worker.service loaded inactive dead start Forem Worker Service
forem.service loaded activating auto-restart start Forem Service
I was able to make them happy with:
sudo systemctl start forem-container.service
some time later...
$ systemctl list-units forem*
UNIT LOAD ACTIVE SUB DESCRIPTION
forem-imgproxy.service loaded active running Forem Imgproxy Service
forem-openresty.service loaded active running Forem OpenResty Service
forem-pod.service loaded active running Forem pod service
forem-postgresql.service loaded active running Forem Postgresql Service
forem-rails.service loaded active running Forem Rails Service
forem-redis.service loaded active running Forem Redis Service
forem-traefik.service loaded active running Forem Traefik Service
forem-worker.service loaded active running Forem Worker Service
forem.service loaded active exited Forem Service
Hi Ben!
On a fresh DigitalOcean deployment, the services looked all sad like this:
I was able to make them happy with:
some time later...
Then
sudo systemctl restart forem-traefik
worked.Woohoo it worked, let's garden!
Really great to see you around these parts Derek. β€οΈ