Update the "Updating your instance" docs #361
No reviewers
Labels
No labels
approved, awaiting change
bug
configuration
documentation
duplicate
enhancement
extremely low priority
feature request
Fix it yourself
help wanted
invalid
mastodon_api
needs docs
needs tests
not a bug
planned
pleroma_api
privacy
question
static_fe
triage
wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: AkkomaGang/akkoma#361
Loading…
Reference in a new issue
No description provided.
Delete branch "norm/akkoma:update-updating-docs"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This makes them consistent with the update instructions that are in the
release announcements.
Also adds in the command to update the frontend as well.
actually is it good to recommend shutting down the instance before migrating? i've always ran
ecto.migrate
in the foreground while my instance was running, and then restarting it only took a couple of secondsthis way adds downtime
and also as far as i'm aware
ecto.migrate
executescompile
if that's not already been doneso really you only need
deps.get -> ecto.migrate -> restart
I'm not really too sure. I've done live migrations on FoundKey without issues but I haven't tried with akkoma so far.
it avoids any potential race conditions involving attempting to insert data into a post-migrate database
hm
well at least could compiling be done live? it takes a while
0034373241
to73c53ccc92
Updated the docs to only stop akkoma when doing migrations and updating the frontend
that seems fine
thank