simonwillisonblog-backup
website
simonwillisonblog-backup | website | |
---|---|---|
7 | 9 | |
15 | 141 | |
- | 2.1% | |
9.9 | 8.6 | |
5 days ago | 12 days ago | |
HTML | ||
- | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
simonwillisonblog-backup
-
Tracking SQLite Database Changes in Git
> I’ve been running that for a couple of years in this repo: https://github.com/simonw/simonwillisonblog-backup - which provides a backup of my blog’s PostgreSQL Django database (first converted to SQLite and then dumped out using sqlite-
I'm curious, what is the reason you chose not to use pgdump, but instead opted to convert to to sqlite and then dump the DB using sqlite-diffable?
On a project I'm working on, I'd like to dump our Postgres schema into individual files for each object (i.e., one file for each table, function, stored proc, etc.), but haven't spent enough time to see if pgdump could actually do that. We're just outputting files by object type for now (one tables, function, and stored procs files).
- Versioning data in Postgres? Testing a Git like approach
-
WordPress Core to start using SQLite Database
My personal blog runs on Django + PostgreSQL, and I got fed up of not having a version history of changes I made to my content there.
I solved that by setting up a GitHub repo that mirrors the content from my database to flat files a few times a day and commits any changes.
It's worked out really well so far. It wasn't much trouble to setup and it's now been running for nearly three years, capturing 1400+ changes.
I'd absolutely consider using the same technique for a commercial project in the future:
Latest commits are here: https://github.com/simonw/simonwillisonblog-backup/commits/m...
Workflow is https://github.com/simonw/simonwillisonblog-backup/blob/main...
-
How Postgres Triggers Can Simplify Your Back End Development
If you really, really need to be able to see a SQL schema representing the current state, a cheap trick is to run an automation on every deploy that snapshots the schema and writes it to a GitHub repository.
I do a version of that for my own (Django-powered) blog here: https://github.com/simonw/simonwillisonblog-backup/blob/main...
-
Blog with Markdown and Git, and degrade gracefully through time
My blog is Django and PostgreSQL on Heroku, but last year I decided I wanted a reliable long-term public backup... so I set up a scheduled GitHub Actions workflow to back it up to a git repository.
Bonus feature: since it runs nightly it gives me diffs if changes I make to my content, including edits to old posts.
The backups are in this repo: https://github.com/simonw/simonwillisonblog-backup
website
-
35M Hot Dogs: Benchmarking Caddy vs. Nginx
Oh, just saw this. You wrote your comment while I wrote mine. If you can enumerate specifically what you want to see, please submit it to our issue tracker: https://github.com/caddyserver/website
Generally we encourage examples in our community wiki though: https://caddy.community/c/wiki/13 -- much easier to maintain that way.
-
Caddyhttp: Enable HTTP/3 by Default
Yes, the docs have been updated at https://github.com/caddyserver/website but haven't been deployed yet. There is a new protocols option:
protocols h1 h2
- The appeal of using plain HTML pages
-
Show HN: Caddy v2.5.0
Could you be more specific about these complaints? What examples don't work? We can't work on improving the docs if we don't get specific and actionable feedback. The docs are found at https://github.com/caddyserver/website if you want to propose any changes.
-
I'm Using SNI Proxying and IPv6 to Share Port 443 Between Webapps
Protip: you can click almost everything in code blocks in the docs. For example, if you click `[]`, it brings you right to the request matcher syntax section, which explains what you can fill in there.
It would be redundant to write on every page what you can use as a matcher. The Caddyfile reference docs assume you've read https://caddyserver.com/docs/caddyfile/concepts which walks you through how the Caddyfile is structured, and it'll give you the fundamentals you need to understand the rest of the docs (I think, anyway).
If you think we need more examples for a specific usecase, we can definitely include those. Feel free to propose some changes on https://github.com/caddyserver/website, we could always use the help!
- Generate Static Sites from Markdown Files with Caddy
- Blog with Markdown and Git, and degrade gracefully through time
What are some alternatives?
WriteFreely - A clean, Markdown-based publishing platform made for writers. Write together and build a community.
neocities - Neocities.org - the web site. Yep, the backend is open source!
blissue - A blog based on github issues
wayback-machine-downloader - Download an entire website from the Wayback Machine.
docs - This is a repo of the RetroArch official document page.
souin - An HTTP cache system, RFC compliant, compatible with @tyktechnologies, @traefik, @caddyserver, @go-chi, @bnkamalesh, @beego, @devfeel, @labstack, @gofiber, @go-goyave, @go-kratos, @gin-gonic, @roadrunner-server, @zalando, @zeromicro, @nginx and @apache
beleyBlog - The non-content portion for my blog at www.chrisbeley.com
go-readability - A Go implementation of the readability algorithm by arc90 labs