simonwillisonblog-backup
neon
simonwillisonblog-backup | neon | |
---|---|---|
7 | 124 | |
15 | 12,327 | |
- | 3.5% | |
9.9 | 9.9 | |
5 days ago | 2 days ago | |
Rust | ||
- | Apache License 2.0 |
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
neon
-
How to ditch Neon
If you're reading this you probably got a really steep bill from Neon after finding yourself on their "Scale" plan. If you do want to stay with Neon but avoid surprise bills then go to the Plans page and choose what you actually want.
-
Serverless Postgres with Neon - My first impression
Such is the case with Neon, a serverless Postgres service, that went generally available on April 15. Congrats Nikita Shamgunov and team on the launch. When I saw the announcement, I knew I had to try it out for myself and report back with my findings.
-
Neon Is Generally Available: Serverless Postgres
I want to use this as a chance to bring attention to a GitHub issue that I think would help reduce friction for Neon:
https://github.com/neondatabase/neon/issues/4989
If the Neon driver were to allow us to easily pass in a localhost connection, the development and test experience would be easier. Perhaps Neon could swap to something like this internally: https://github.com/porsager/postgres.
Having run a local dev environment connected to Neon and tests connected to Neon got in our way of adoption. We'd prefer to develop and run tests against a regular Postgres localhost database.
To the PMs of Neon, put yourself in the shoes of a new developer thinking of giving Neon a try. What changes will I have to make to my code and my development workflow?
-
11 Planetscale alternatives with free tiers
Neon is an open source and cloud-native serverless database platform that focuses on simplicity and ease of use. It supports Postgres databases and offers built-in features like bottomless storage, autoscaling, and branching.
-
Breaking the Myth: Scalable, Multi-Region, Low-Latency App Exists And Will Not Cost You A Kidney.
For MySQL, we've got PlanetScale, and for PostgreSQL, there's Neon.
-
Ask HN: Freelance website builders/maintainers, what's in your 2024 toolkit?
8. https://neon.tech/As you might know not one tool fits all, I still have strong preferences for the following. It helps me get going faster and get things done right first time and helps in ease of maintenance.
Language: Typescript.
-
Why PlanetScale broke our trust in database startups
Migrated away when they removed the free tier, ended up using https://neon.tech/
-
Parsing the Postgres protocol – logging executed statements
Cool! At Neon[0], I work full time on our custom postgres proxy[1]. It's a very nice protocol to work with, although our usecase is quite a bit more complex compared to the ideas presented in the post.
Neon databases scale to zero, so the proxy needs to spin up databases on the fly. The proxy doesn't do that but it knows if the databases is running and asks our control plane to schedule it if it isn't. It's a fun service to maintain.
The biggest pain is error handling. Postgres is really bad for error messages and codes. The only available code we can use is usually protocol violation...
[0]: https://neon.tech/
- Neon: Serverless Postgres
-
No More Free Tier on PlanetScale, Here Are Free Alternatives
Neon - PostgreSQL
What are some alternatives?
WriteFreely - A clean, Markdown-based publishing platform made for writers. Write together and build a community.
supabase - The open source Firebase alternative.
blissue - A blog based on github issues
cockroach - CockroachDB - the open source, cloud-native distributed SQL database.
docs - This is a repo of the RetroArch official document page.
yugabyte-db - YugabyteDB - the cloud native distributed SQL database for mission-critical applications.
wayback-machine-downloader - Download an entire website from the Wayback Machine.
orioledb - OrioleDB – building a modern cloud-native storage engine (... and solving some PostgreSQL wicked problems) 🇺🇦
beleyBlog - The non-content portion for my blog at www.chrisbeley.com
MongoDB - The MongoDB Database
go-readability - A Go implementation of the readability algorithm by arc90 labs
edgedb - A graph-relational database with declarative schema, built-in migration system, and a next-generation query language