You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been using Umami deployed on Fly.io for a while now, using this thread as a guide.
Just reporting that the migration from v1 to v2 went well once I figured out how to get the migration script running via the [deploy]section Fly's fly.toml configuration file. The script non-interactively in that case, though, so dropping v1 tables needed to be done manually. Actually, the only issue running the migration script was that my Fly app had too little memory. I just temporarily boosted the memory with fly scale memory 2048 (probably overkill), then:
fly ssh console
cd app
npx @umami/migrate-v1-v2@latest
Umami no longer successfully runs its database checks with the Fly app set to 256 mb RAM, so mine is now running on 512.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I've been using Umami deployed on Fly.io for a while now, using this thread as a guide.
Just reporting that the migration from v1 to v2 went well
once I figured out how to get the migration script running via theActually, the only issue running the migration script was that my Fly app had too little memory. I just temporarily boosted the memory with[deploy]
section Fly'sfly.toml
configuration file. The script non-interactively in that case, though, so dropping v1 tables needed to be done manually.fly scale memory 2048
(probably overkill), then:Umami no longer successfully runs its database checks with the Fly app set to 256 mb RAM, so mine is now running on 512.
Beta Was this translation helpful? Give feedback.
All reactions