@james @janl in web UI it should definitely be working, do you not see any new notifications, or is it just that they're not appearing real-time? Do the feeds update automatically in the web UI?
-
@james @janl in web UI it should definitely be working, do you not see any new notifications, or is it just that they're not appearing real-time? Do the feeds update automatically in the web UI?
It could be that the streaming server didn't restart properly, or if it's push notifications only, doing a `Web::PushSubscription.destroy_all` could be necessary
-
-
Jan Lehnardt :couchdb:replied to Emelia πΈπ» last edited by
@thisismissem @james thanks for the tips! I posted this right before going to bed last night and this morning I thought I try the simplest thing possible and restart all processes which I have done a few minutes ago and that seems to have fixed it, new notifications, like yours now, show up fine again. But the ones in the meantime have been lost (fine by me).
-
Emelia πΈπ»replied to Jan Lehnardt :couchdb: last edited by
-
Jan Lehnardt :couchdb:replied to Emelia πΈπ» last edited by
@thisismissem Iβm on elest.io which has an auto-update service that usually works great, but it botched my upgrade by not generating the new ActiveRecord security env vars. Once I fixed that, the docker containers auto-restarted and things looked to be working fine except using existing auth keys from Ivory. Thatβs when I found the pending migrations message. I ran the migrations and then Ivory worked again and I left it at that. My assumption is that I should have restarted after migrating.
-
Emelia πΈπ»replied to Jan Lehnardt :couchdb: last edited by
@janl yeah, restart your Services *after* you've run normal migration, but *before* running post-migrations.
-
Jan Lehnardt :couchdb:replied to Emelia πΈπ» last edited by
@thisismissem heh I only found one type of migration. The whole reason Iβm using this service is so I donβt have to worry about the ins-and-outs of this all
-
Emelia πΈπ»replied to Jan Lehnardt :couchdb: last edited by
@janl there's two:
SKIP_POST_DEPLOYMENT_MIGRATIONS=true RAILS_ENV=production bundle exec rails db:migrate
And
RAILS_ENV=production bundle exec rails db:migrate
-
Jan Lehnardt :couchdb:replied to Emelia πΈπ» last edited by
@thisismissem ah cool, I only ran the latter, that does everything then?
-
Emelia πΈπ»replied to Jan Lehnardt :couchdb: last edited by
@janl yeah, but can cause issues for running processes.