simonwillisonblog-backup

Backups of the database for simonwillison.net (by simonw)

Simonwillisonblog-backup Alternatives

Similar projects and alternatives to simonwillisonblog-backup

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better simonwillisonblog-backup alternative or higher similarity.

simonwillisonblog-backup reviews and mentions

Posts with mentions or reviews of simonwillisonblog-backup. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-11-02.
  • Tracking SQLite Database Changes in Git
    7 projects | news.ycombinator.com | 2 Nov 2023
    > 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
    9 projects | news.ycombinator.com | 20 Oct 2023
  • WordPress Core to start using SQLite Database
    5 projects | news.ycombinator.com | 26 Jul 2023
    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
    2 projects | news.ycombinator.com | 23 Apr 2023
    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
    14 projects | news.ycombinator.com | 8 Feb 2021
    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

  • A note from our sponsor - SaaSHub
    www.saashub.com | 25 Apr 2024
    SaaSHub helps you find the best software and product alternatives Learn more →