Skip to content

UPV Server

Roger B. Dannenberg edited this page Oct 14, 2022 · 3 revisions

Notes on server at UPV

URL: https://soundcool.webs.upv.es/

Automated Installation/Updates

The button labeled "Pull Updates" should appear below "Node.js App" on the Websites & Domains page but it seems to have been removed (Oct 14, 2022) and hasn't been working.

From Amit:

So the "Pull Updates" checks, if there are any changes on the Github repository, pulls them to the UPV server. Once the changes are fetched, it triggers the pleask_deployment.sh script currently placed at the root of the Github repository. It completed the setup in the following manner

  1. Fetch npm modules for frontend
  2. Run Webpack build to generate static files
  3. Fetch npm modules for backend
  4. Once these steps are done, we copy our backend from the cloned directory, ' httpdocs/gitSoundcooltohttpdocs, which is a node server in plesk`.
  5. After that, we finish the setup by modifying the modification timestamp of httpdocs/tmp/restart.txt which restarts the node.js server.

Also, as the copy operation starts only if previous operations were successful hence there are very low chances that the website will go down.

In any case, if it goes down and it gets hard to figure out the issue. One can simply upload a working backend of the soundcool to httpsdocs directory by drag and drop operation using file management on the UPV server.

This is a quick doc but should give somewhat the idea of what is going on and what should we do if anything goes wrong.

Notes on Changes and Maintenance

RBD backed up all of httpdocs in home to httpdocs-14oct2022.zip in home. After attempting to install changes, which made the site stop functioning (no logins or new accounts), I restored everything from here, and the site started working again, so let's keep this backup in case we get in trouble again.

RBD backed up httpdocs/public to backend-public-backup-14oct2022.zip

RBD copied a local (macOS) version of src/backend/public via backend-public.zip to httpdocs/public, and the new personal data and privacy changes appear to be installed and working.

RBD My guess is that overwriting the soundcool.db from my local installation was a bad idea. I don't know how/if we can change the real backend code, because these recent changes are only to the front-end, which seem to be compiled into backend/public/src/build/bundle.{css,js} (and maybe other files in backend/public/).