This PR is to solve two issues stemming from the fact that we track the /server/data folder:
It's hard to pull new versions of the website without deleting all local information, and
It's really easy for developers to accidentally commit personal information to the repo ;_;
To address these, this PR adds a /server/data-base folder. This is the starter version of any page. On startup, preload.ts is called in both the startup npm scripts. preload.ts checks over the /server/data-base folder. For any file or directory it sees in /server/data-base that it doesn't see in /data, it creates a copy in /data that can be freely edited without causing the issues outlined above.
I've removed functionality from DirectoryPrebuilder that duplicated this behaviour for simplicity.
There's a lot of files in the changeset here. I don't know why github is displaying it like it is ;-;. Almost all of them are unchanged, save for removing elections data and exec names.
This PR is to solve two issues stemming from the fact that we track the
/server/datafolder:To address these, this PR adds a
/server/data-basefolder. This is the starter version of any page. On startup,preload.tsis called in both the startup npm scripts.preload.tschecks over the/server/data-basefolder. For any file or directory it sees in/server/data-basethat it doesn't see in/data, it creates a copy in/datathat can be freely edited without causing the issues outlined above.I've removed functionality from
DirectoryPrebuilderthat duplicated this behaviour for simplicity.There's a lot of files in the changeset here. I don't know why github is displaying it like it is ;-;. Almost all of them are unchanged, save for removing elections data and exec names.