impress-2020/scripts/db/export/public-data.sh

yarn run --silent mysqldump openneo_impress species colors zones \
  > $(dirname $0)/../public-data-constants.sql \
&& yarn run --silent mysqldump openneo_impress alt_styles items item_translations \
  parents_swf_assets pet_states pet_types swf_assets \
  | gzip -c \
  > $(dirname $0)/../public-data-from-modeling.sql.gz
Stop referencing the {color,species,zone}_translations tables We're in the process of migrating away from translating these records, because Neopets hasn't supported non-English languages in many years, and it'll simplify our code and database lookups. In Main DTI, we already wrote code to copy these fields onto the main records and keep them in sync for now; now, once DTI 2020 isn't referencing them anymore, it should be safe for the main app to drop the tables altogether. Note that some Prettier changes got mixed in here and that's fine! I also wasn't suuuper careful testing these, most of them seem to be trivially testable by just loading the homepage or doing a few basic wardrobe actions, and the others are in Discord support log actions that aren't enabled in development mode, so I'm just like… ehh I'll do a couple support actions after deploy and see that they don't crash! 2024-02-03 08:05:15 -08:00			`yarn run --silent mysqldump openneo_impress species colors zones \`
Script to set up dev db with public DTI data Now, someone with production DB access can run `yarn db:export:public-data` to create `public-data-constants.sql` and `public-data-from-modeling.sql`. Then, someone setting up their dev database can run `yarn db:setup-dev:full` and get all the wearables data imported right into their dev database! I'm noticing just how poorly I'm keeping up with my own goals for finishing up DTI, and wondering if now is a good time to circle back to some old offers for code contributions I got last year… I also just figure that making this app Possible To Run with a backup of the basic public database is like. a pretty handy thing to have for archival's sake imo Note that, for this change, we also set up Git LFS (Large File Storage). Github should be automatically compatible with this! It's a way to not write the whole 30MB database dump into the repository history, and instead keep it in a secondary filestore, because Git's core algorithms aren't really built to handle large blobs of data very well. Users setting up their dev environment will therefore also need to have Git LFS installed for this script to work! (Otherwise, they'll see a "pointer" file in `public-data-from-modeling.sql.gz` that contains some metadata about the file state but not the data itself.) 2022-11-13 07:03:35 -08:00			`> $(dirname $0)/../public-data-constants.sql \`
Update public data SQL dump, mainly to add alt styles Note also the change to the public-data-constants, because we've started (but not finished) moving name fields into the rows themselves and deprecating the translations. 2024-02-01 02:01:50 -08:00			`&& yarn run --silent mysqldump openneo_impress alt_styles items item_translations \`
Script to set up dev db with public DTI data Now, someone with production DB access can run `yarn db:export:public-data` to create `public-data-constants.sql` and `public-data-from-modeling.sql`. Then, someone setting up their dev database can run `yarn db:setup-dev:full` and get all the wearables data imported right into their dev database! I'm noticing just how poorly I'm keeping up with my own goals for finishing up DTI, and wondering if now is a good time to circle back to some old offers for code contributions I got last year… I also just figure that making this app Possible To Run with a backup of the basic public database is like. a pretty handy thing to have for archival's sake imo Note that, for this change, we also set up Git LFS (Large File Storage). Github should be automatically compatible with this! It's a way to not write the whole 30MB database dump into the repository history, and instead keep it in a secondary filestore, because Git's core algorithms aren't really built to handle large blobs of data very well. Users setting up their dev environment will therefore also need to have Git LFS installed for this script to work! (Otherwise, they'll see a "pointer" file in `public-data-from-modeling.sql.gz` that contains some metadata about the file state but not the data itself.) 2022-11-13 07:03:35 -08:00			`parents_swf_assets pet_states pet_types swf_assets \`
			`\| gzip -c \`
			`> $(dirname $0)/../public-data-from-modeling.sql.gz`