go-readability
simonwillisonblog-backup
go-readability | simonwillisonblog-backup | |
---|---|---|
2 | 7 | |
131 | 15 | |
- | - | |
0.0 | 9.9 | |
almost 2 years ago | about 17 hours 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.
go-readability
-
Which library/project do you wish was ported to golang?
https://github.com/go-shiori/go-readability https://github.com/mauidude/go-readability
-
Blog with Markdown and Git, and degrade gracefully through time
In terms of extracting the actual blog content from pages, there is a go library that implements the readability algorithm:
https://github.com/mauidude/go-readability
This is the kind of thing pocket/instapaper do to extract the main content from a page in a format that's easier to read (and also probably to programmatically modify)
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
What are some alternatives?
docs - This is a repo of the RetroArch official document page.
WriteFreely - A clean, Markdown-based publishing platform made for writers. Write together and build a community.
website - The Caddy website
blissue - A blog based on github issues
temporalite-archived - An experimental distribution of Temporal that runs as a single process
wayback-machine-downloader - Download an entire website from the Wayback Machine.
bdv32 - This is my website
beleyBlog - The non-content portion for my blog at www.chrisbeley.com