Automate setup

[erbridge]

• Clarify Postgresql via Docker is optional
• Use bin scripts for setup and updates

[kimadactyl]

Few quick notes/qs as I log off

• We don't use seed migration gem any more - our seeds need a total rethink how they work. It should probably be purged for now.
• Does the js setup need to also set nvm version?
• Importing events can take a long time - wonder if this is too much to throw into the main setup script
• Will this update bundler and yarn every time it runs? Those messages do get annoying!
• How is ruby version set?
• We have a script for syncing the db from the main/staging server private notion instructions here - not sure where this should live

[ivan-kocienski-gfsc]

Does this have a ticket associated with it? I think it is studio policy that any PR has a ticket that describes the issue.

Not that I am going to insist on it this time but I'd like to see this in future. (Or maybe I am out of line, apologies)

[ivan-kocienski-gfsc]

This looks okay to me.

[erbridge]

@ivan-kocienski-gfsc I think there's value in tickets when there's extended work involved in something. I think for small tech debt improvements, creating a matching ticket is overkill and process for the sake of process. Like writing a ticket for this would have taken longer than the work to fix it.

Please do tell me if you think I'm wrong about that, though.

[erbridge]

@kimadactyl All good questions, but remember: this is just about making the already documented stuff automatic instead of needing copy-paste. There are some assumptions built in here that you've done your environment set up correctly (using RVM or rbenv, have Postgresql running, etc), that making work in a platform agnostic way would be painful. I did consider printing a bunch of "do this first" stuff to surface those requirements, but decided against it at this point.

[erbridge]

Will this update bundler and yarn every time it runs?

Yes, but you only run this very infrequently. bin/setup is to be run when you first set up the project or want to restore it after being away for a while. bin/update is to be run when you pull some new changes down that might have changed some of how the project is set up.

[erbridge]

Re event importing, we should take a look at the best thing to do, but probably at another time. This PR is about automating the existing set up, not innovating on it. Also the event import was pretty quick for me.

[erbridge]

@kimadactyl Could you write a ticket about the database sync stuff, please? I'm not sure I have enough context to at this point.