Start work on Fastify server

.env

@@ -1,2 +1 @@
-REACT_APP_GOOGLE_CLIENT_ID=706375540729-sqnnig7o0d0uqmvav0h8nh8aft6l55u3.apps.googleusercontent.com
-API_BASE=https://hydrant.xvm.mit.edu
+REACT_APP_GOOGLE_CLIENT_ID=706375540729-sqnnig7o0d0uqmvav0h8nh8aft6l55u3.apps.googleusercontent.com

.env.development

@@ -1,2 +1,3 @@
-API_PORT=6873
-API_BASE=http://localhost:$API_PORT
+PORT=3428
+SITE=http://localhost:3428
+FIREROAD_API_BASE=https://fireroad-dev.mit.edu

.env.production

@@ -0,0 +1,3 @@
+SITE=https://hydrant.mit.edu
+FIREROAD_API_BASE=https://fireroad.mit.edu
+# Store secrets (if any) in .env.production.local

.github/workflows/autodeploy.yml

@@ -15,7 +15,7 @@ jobs:
     - name: Install node
       uses: actions/setup-node@v3
       with:
-        node-version: 16
+        node-version: 18
     - name: Install node dependencies
       run: npm install
     - name: Run build
@@ -26,4 +26,5 @@ jobs:
         name: built-site
         path: |
           build
-          !build/latest.json
+          server
+          !server/dev.js

.gitignore

@@ -18,3 +18,7 @@ __pycache__
 deploy.sh
 
 .idea
+
+# Secrets
+.env.local
+.env.*.local

.node-version

@@ -1 +1 @@
-16.16.0
+18.17.0

README.md

@@ -20,7 +20,7 @@ There's the frontend, which is the website and the interface. Then there's the b
 
 To update the frontend (source code in the `src/` directory), you can run `npm start` and open the link that shows up in your terminal window. As you change the source code, the site should update in real-time, but you can reload if you want to make sure you're using the latest version.
 
-To work on the backend (located in `src-server/`), it's a similar process. If you run `npm start`, you can edit any of the files in `src-server/` to reload the Node.js server automatically with your changes. If you just want to tinker with the API without touching the frontend code, you can alternatively run `npm run start:frontend`.
+To work on the backend (located in `src-server/`), it's a similar process. If you run `npm start`, you can edit any of the files in `src-server/` to reload the Node.js server automatically with your changes.
 
 *NB: Hydrant is currently in the process of moving to a Node.js-only backend! For now, you'll need to do the following steps as well.*
 
@@ -40,9 +40,7 @@ Finally, run the normal update process and commit the results to the repo.
 
 ### Updating the server
 
-The server's frontend updates based on the `deploy` branch on GitHub, so any changes pushed there will become live.
-
-The server's backend is updated by an automatic deploy to an XVM instance via the same `deploy` branch.
+The server's frontend and backend updates are based on the `deploy` branch on GitHub, so any changes pushed there will become live.
 
 See `deploy/README.md` for more info.
 

deploy/README.md

@@ -39,4 +39,5 @@ The backend runs on an XVM instance at `hydrant.xvm.mit.edu`. It is deployed sep
 
 After the backend is build with `npm run build`, we start the server on the XVM instance with [PM2](https://pm2.keymetrics.io/) using the `pm2.config.js` file located in this folder.
 
-*NB: This documentation is incomplete! It will be updated after the migration to a Node.js backend is finished and we finalize the deployment process.*
+*NB: This documentation is incomplete! It will be updated after the migration to a Node.js backend is finished and we finalize the deployment process.*
+- TODO: how to use secrets on backend? `dotenv`?