Move the podverse-api scripts into podverse-workers, and integrate with new repos and node_modules

.dockerignore

@@ -1,8 +1,6 @@
 .git
 
-/src/config/bitpay/api.key
 /src/config/google/jwt.keys.json
-/src/config/parser/addFeedUrlsFile.json
 
 /src/public/samples
 

.gitignore

@@ -1,6 +1,5 @@
 .git
 
-/src/config/bitpay/api.key
 /src/config/google/jwt.keys.json
 /src/config/parser/addFeedUrlsFile.json
 

.nvmrc

@@ -1 +1 @@
-v16.13.1
+v20.10.0

.vscode/settings.json

@@ -7,7 +7,6 @@
     "partytime",
     "podverse",
     "ratelimit",
-    "Reparsing",
-    "typeorm"
+    "Reparsing"
   ]
 }

Dockerfile

@@ -1,8 +1,8 @@
-FROM node:16-bullseye
+FROM node:20-bullseye
 WORKDIR /tmp
 COPY . .
 
-RUN npm install -g ts-node@8.5.4
+RUN npm install -g ts-node@10.9.2
 RUN npm install
 
 # Update the package listing, so we know what package exist:

README.md

@@ -19,24 +19,20 @@ Data API, database migration scripts, and backend services for the Podverse ecos
 
 If you are looking to run this app or contribute to Podverse for the first time, please read the sections that are relevant for you in our [CONTRIBUTE.md](https://github.com/podverse/podverse-ops/blob/master/CONTRIBUTING.md) file in the podverse-ops repo. Among other things, that file contains instructions for running a local instance of the Podverse database.
 
-### NPM or Yarn
-
-We use yarn and maintain a `yarn.lock` file, but it's not really a requirement for you to use yarn. This documentation uses npm in examples, but we generally use the yarn equivalent commands.
-
 ### Setup environment variables
 
 For local development, environment variables are provided by a local `.env` file. You can find a link to example `.env` files in the [CONTRIBUTING.md](https://github.com/podverse/podverse-ops/blob/master/CONTRIBUTING.md) file.
 
 ### Install node_modules
 
-```bash
-npm install
+```sh
+yarn
 ```
 
 ### Start dev server
 
-```bash
-npm run dev
+```sh
+yarn dev:watch
 ```
 
 ### Populate database
@@ -47,8 +43,8 @@ Instructions for this can be found in the [podverse-ops CONTRIBUTING.md file](ht
 
 If you are creating a database from scratch, and not using the `populateDatabase` command explained in the CONTRIBUTE.md file, then you will need to populate the database with categories.
 
-```bash
-npm run dev:seeds:categories
+```sh
+yarn dev:seeds:categories
 ```
 
 ### Sync podcast data with Podcast Index API

docs/populateDatabase.md

@@ -33,7 +33,7 @@ Also, you will need to set `SUPER_USER_ID=jISAEEgXa` (due to [this Github issue]
 #### Install node modules
 
 ```bash
-npm install
+yarn
 ```
 
 ### Populate database
@@ -43,7 +43,7 @@ npm install
 To populate the database:
 
 ```bash
-npm run dev:seeds:qa:populateDatabase
+yarn dev:seeds:qa:populateDatabase
 ```
 
 The full run will take 3+ minutes, mostly due to network requests to Podcast Index API to use real podcast data to populate the database.
@@ -53,5 +53,5 @@ The full run will take 3+ minutes, mostly due to network requests to Podcast Ind
 To populate the database faster (with fewer podcasts), you can pass a `quick` flag to the populateDatabase script:
 
 ```bash
-npm run dev:seeds:qa:populateDatabase quick
+yarn dev:seeds:qa:populateDatabase quick
 ```

docs/postman/podverse-api_v4-13-4.postman_collection.json

@@ -1186,7 +1186,7 @@
 				"header": [
 					{
 						"key": "Authorization",
-						"value": "key={{FCM_GOOGLE_API_AUTH_TOKEN}}",
+						"value": "key={{GOOGLE_AUTH_TOKEN}}",
 						"type": "text"
 					},
 					{