search

CSSS / csss-site-frontend

CSSS Website Frontend (2024 - Present)
https://new.sfucsss.org/
GNU Affero General Public License v3.0
6 stars 6 forks source link

Configure nginx to proxy /api #53

Open micahdbak opened 1 month ago

micahdbak commented 1 month ago
micahdbak commented 1 month ago

We may need a task in csss-site-backend too :))

micahdbak commented 1 month ago

@EarthenSky im assigning this to only u, figure it out >:)

micahdbak commented 2 weeks ago

@EarthenSky what's left for this? I know https://github.com/CSSS/csss-site-frontend/pull/54 does the proxying, but is there anything more that PR needs?

micahdbak commented 2 weeks ago

Oh right, I remember, we wanted to make a new repo for this. Could you create a csss-site-config repository? I can start adding commits transferring the scripts, nginx conf, ..., between backend and frontend

Then on the server ill clone it and make sure the scripts work as intended

Maybe we should keep the service files in backend though - just move nginx config?

@EarthenSky

micahdbak commented 2 weeks ago

Once that repo is made, then the configure /api usage PR should:

  1. delete the nginx scripts and config files from this repo
    1. note: keep the deploy_to_branch.sh script cuz it's necessary
  2. update interaction with API via JS
EarthenSky commented 2 weeks ago

what's left for this?

I hadn't done any work on this until now. Thinking about it, we just need to update the nginx proxy then I need to remove the api.sfucsss.org domain from namecheap.

csss-site-config repository

As we mentioned in dms, this is a good idea & probably the first thing we should do after the old site is taken down (or maybe even before?)

Maybe we should keep the service files in backend though

I'm fine with the config being wherever; if we want to remove the nginx from backend & move it to frontend, that would be nice.

  1. update interaction with API via JS

This should already be done as of https://github.com/CSSS/csss-site-frontend/pull/54