Deploy script failure

[stobot]

I was able to follow the directions to set this up until the yarn run deploy part. the script fails and this is what I see. This is a bit out of my league so have limited ability to debug but am VERY excited to try and get this working. Any ideas? The only thing that didn't happen exactly like the directions said they would was that the config.json file has a line for: "databaseURL": "https://peterneumark-com.firebaseio.com" , but there wasn't something to replace it with in Firebase.

PS C:\Users\stobb\tw5-firebase> yarn run deploy
yarn run v1.22.17
$ ./scripts/build.sh && ./scripts/deploy.sh
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

[stobot]

As a follow-up, working with some people to solve this over at talk.tiddlywiki https://talk.tiddlywiki.org/t/anyone-using-firebase/1502

[dfjerstad]

Here were the problems that I ran into deploying this:

1. The Firebase config seen here (https://raw.githubusercontent.com/neumark/tw5-firebase/master/static/img/doc/fb_app_config.png) wasn't in JSON format as the keys were not enclosed in double quotes. That means when I copied it to config.json it wasn't interpreted correctly. I added double quotes around the keys.
2. config.json, keys.json, and service-account-key.json were all supposed(?) to have ".staging" in the file name, so I renamed them all to config.staging.json, keys.staging.json, and service-account-key.staging.json respectively.
3. The generated configs and schemas were not being created because they apparently needed the folders to be there already. So from the root folder i.e. tw5-firebase/ I created the folder "generated" (e.g. mkdir generated) and in that folder I created the folders "config" and "jsonschema"
4. The "Default GCP Resource Location" said "nam5 (us-central)" so I tried using both "nam5" and "us-central" in place of "europe-west3". The actual resource location was "us-central1" which I eventually figured out. I entered that into my config json file. I believe those were all the issues I ran into. After that I ran 'yarn run deploy' per the instructions, it didn't throw any more errors, and everything else worked as described.