2018/01/14

From Mew
< 2018
Revision as of 17:54, 14 January 2018 by Woozle (talk | contribs) (rearranged order slightly)
Jump to navigation Jump to search

2018-01-14

My current plan is:

  1. create new system user "tootcat"
  2. create a new Postgres db for toot.cat's Mastodon
  3. migrate the data there
  4. install Mastodon under user "tootcat"
  5. run Mastodon's schema upgrade rake task
  6. test the result as https://new.toot.cat (get it working)
  7. write a script to automate the data migration
  8. in close succession:
    1. run the migration script
    2. reconfigure nginx to point to the new instance

revisions

  • Decided it would simplify things if I went ahead and created the "tootcat" system user first.

Notes

Inside /root/backups:

su - postgres -c 'pg_dump mastodon' > tootcat.sql

Upgrading Mastodon: official

I'm calling the new db tootcat-masto-r1 (toot.cat Mastodon db revision 1) (possibly with '-' replaced by '_').

Probably just need to do this next: CREATE DATABASE tootcat-masto-r1;

...or, rather: createdb --owner=tootcat tootcat-masto-r1 -- except do I need to create "tootcat" as a system user first? Or a db user?