Automated Backups, Content

Had a good night's sleep and I have a lot of time, so hopefully today I'll finish a bunch of stuff.

Plan for today:

• set up automated backups
• display content on dashboard

Automated Backups

For the backups, I'll simply be dumping the volumes into a tar and uploading them to Wasabi. I choose Wasabi because it seems to be the cheapest option, and it's S3 compatible.

sudo apt install awscli
aws configure --profile wasabi

Then I can use the s3 cli as usual, but I need to postfix every command with the wasabi config, which is kinda annoying but I guess it's fine as I won't be running them manually that much.

aws s3 ls --profile wasabi --endpoint-url=https://s3.wasabisys.com

Now that I've done it, I see that it was a stupid idea. You can't just dump the filesystem of a running Postgres database and call it a backup. I will change the backup method for Postgres. The content backup stays the same.

I'm also thinking of skipping the whole local content thing and serving directly from buckets. Can I configure the custom domain? Can I set the headers? I'll probably do that later.

I will run this backup script with a cron job once a day for now.

I've also switched to Cloudflare R2, as the Wasabi pricing is actually $7 after the trial, no matter the usage. Pretty lame. Also the docs and the whole experience using the service is horrendeous.

Content Management

Next up, displaying the content in the dashboard.

I updated the dashboard so it supports windows, and added a few that I'm sure I'll need. I've also added a small overview, just for fun.

I've added the content endpoint and a simple screen listing all the user's content. Not sure I like it, but it's good enough for now.

I need to decide what I'm going to be doing next. I'll probably continue with the content pipeline, but I'm too tired to think about it now.

I've moved the web-app into a separate repo to fix the versioning. Pretty happy with how everything is looking.

Pretty happy with the session today.