Fly.io deployment with mounts does not work anymore about picoshare HOT 2 CLOSED

Is it possible it's a Fly outage and not a PicoShare issue? In the logs, PicoShare is serving successfully:

2024-01-02T15:59:26.419 app[148e5996b5d598] arn [info] 2024/01/02 15:59:26 migrations.go:33: migration counter: 7/7
2024-01-02T15:59:26.420 app[148e5996b5d598] arn [info] 2024/01/02 15:59:26 main.go:64: listening on 8080

Is the config you're using intended to sync with Litestream? It's currently creating its own local database and not syncing to Litestream:

2024-01-02T15:59:26.390 app[148e5996b5d598] arn [info] + echo 'Starting without litestream'

If you're troubleshooting this, I recommend either turning off the volume or turning off Litestream entirely to prevent a newly-created DB from overwriting the replicated snapshots through Litestream. When you've got it working again, use a fresh Fly volume so that the DB on your pico_data volume isn't going to overwrite the replicated data on Litestream.

from picoshare.

Yeah, I saw that picoshare has started listening, but I assumed the problem was with healthchecks, since fly.io "couldn't find a healthy load balancer". However, I redeployed today again and it seems to work, so might be a transient fly.io problem

from picoshare.