Fixed read only mode feature

[ConnorSheremeta]

Fixed read only mode feature by adding system account if needed

[murny]

This isn't a complete 1 to 1 port of the code that's currently in master. Any reason why to leave out certain things (like setting system api key and setting system boolean to true, etc)?

https://github.com/ualbertalib/jupiter/blob/master/db/migrate/20200305210657_add_system_account_if_needed.rb

Is it just cause this branch is a bit behind and missing some of this code (system boolean/api key/etc)?

Also we will have some wrestling to do when we get production on master.

Do we have plans on merging this old-master-fedora branch back into Master in the future or just let it die? (if we merging it, then we will have two of these migrations doing similar things sitting around which is probably not ideal).

Finally when we do get production on Master, our system user could be missing the system boolean and api key generated for this from the old migration and we need to remember to add these things onto the system user

But you might have a plan for all this and if so ignore me 😄

[mbarnett]

Those columns (system api key, and system boolean) don't exist on this branch. So this is kind of the minimal version of what happens over on master, that won't interfere with master, without having to back port a bunch of that API work just to create this account.

I don't really plan on porting this over to master? It just gets current production to a known state that master can then continue forward from without breaking, without having to do a bunch of backporting from master->old master and then old master -> master

[murny]

Sounds good 👍 .