Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deploy to the organisers.doesliverpool.com VPS #34

Open
amcewen opened this issue Jun 20, 2024 · 4 comments
Open

Deploy to the organisers.doesliverpool.com VPS #34

amcewen opened this issue Jun 20, 2024 · 4 comments

Comments

@amcewen
Copy link
Member

amcewen commented Jun 20, 2024

At present the weeknotes have been running from one of my servers. Now we're going to be serving images too it really should (rather than just should) be on DoES infrastructure.

The server being used by optimism might as well do double-duty; particularly once #33 is done.

@amcewen
Copy link
Member Author

amcewen commented Jun 20, 2024

I've set up the DNS for media.doesliverpool.com, which points at the organisers.doesliverpool.com VPS and set up NGINX to serve files for it (probably still need to sort out the certificates for it).

@amcewen
Copy link
Member Author

amcewen commented Jun 20, 2024

Ran certbot --nginx to update the certificates and get them working for both sites on that VPS.

@amcewen
Copy link
Member Author

amcewen commented Jul 2, 2024

The Dockerfile needs two volumes to be mounted:

  • /var/local/media_root to hold the published media files. This should be mounted to $site_root/m for the media web server (because I think it'll be useful to put all the content in a top-level folder and something super-short, like /m/ for Mastodon, seems sensible.
  • /var/local/workfiles to hold the consent requests and toots waiting to be processed. This should be mounted to some local folder on the server

@amcewen
Copy link
Member Author

amcewen commented Aug 13, 2024

Initially I couldn't clone this repo on the production server because it didn't have any keys set up. Not quite sure why, as DoESLiverpool/optimism#17 (comment) mentions us setting up a deploy key 🤷 There wasn't a deploy key in optimism, so I added it again there.

I was expecting to have to follow this guide to set up aliases in ssh and add a deploy key from this repo too, but I could actually just clone it once I'd added the optimism deploy key.

I've added cron jobs to look for new posts (and ask for consent) effectively on the hour; and at quarter-past-the-hour it checks for responses to the consent requests. They both seem to be running okay so far. I've also set up cron to generate the weeknotes on Monday morning too. Will leave this open until I've confirmed that that's working.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant