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
This release changes deployment to fly.io quite significantly. Based on feedback from them we're making the first deploy use fly launch instead of the previously documented approach. The changes also set us up for more easily supporting your own domain / custom subdomains for a hosted version.
If you have an existing deployment and you want to keep the data in your database and reuse it, there's a bit of work to do as documented below. Sorry about this! We don't anticipate any more changes that would require this much work. In the future, updating will be a case of just a couple of commands.
How to upgrade an existing PostOwl installation for this releae.
# make sure you're in your PostOwl directory
fly ssh console
sqlite3 data/db.sqlite3 ".backup data/backup-db.sqlite3"
# ctrl+d to exit console
fly sftp get data/backup-db.sqlite3 data/backup-db.sqlite3
Get the latest version of PostOwl and clean up files:
git fetch --tags
git checkout tags/v0.1.2
# or you can git pull if you want to get the latest changes on main
rm Dockerfile fly.toml
Update .env.production with the new format from .env.production.example
Destroy your existing app and launch a replacment:
fly apps destroy appname
fly launch
Respond to the prompts. You can reuse the appname you previously had or choose a new one. If you reuse the appname it can take an hour or two to be available again while DNS records sort themselves out.
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
-
This release changes deployment to fly.io quite significantly. Based on feedback from them we're making the first deploy use
fly launch
instead of the previously documented approach. The changes also set us up for more easily supporting your own domain / custom subdomains for a hosted version.If you're deploy PostOwl for the first time, follow the deployment documentation.
If you have an existing deployment and you want to keep the data in your database and reuse it, there's a bit of work to do as documented below. Sorry about this! We don't anticipate any more changes that would require this much work. In the future, updating will be a case of just a couple of commands.
How to upgrade an existing PostOwl installation for this releae.
Update
.env.production
with the new format from.env.production.example
Destroy your existing app and launch a replacment:
Respond to the prompts. You can reuse the appname you previously had or choose a new one. If you reuse the appname it can take an hour or two to be available again while DNS records sort themselves out.
fly launch
:In
fly.toml
after[base]
add:In
Dockerfile
, replaceRUN npm run build
withRUN mkdir /data && npm run build
Run
fly deploy
Restore your database:
You should now be up and running. In the future updaing will be just a couple of commands.
This discussion was created from the release v0.1.2.
Beta Was this translation helpful? Give feedback.
All reactions