simonwillisonblog-backup
Hexo
simonwillisonblog-backup | Hexo | |
---|---|---|
7 | 28 | |
15 | 38,492 | |
- | 0.5% | |
9.9 | 8.2 | |
5 days ago | 7 days ago | |
TypeScript | ||
- | MIT License |
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
Hexo
-
Ask HN: Looking for lightweight personal blogging platform
A lot of great suggestions here and some stuff I’ve never heard of before!
Throwing my own suggestion into the ring, as I was just looking into this last week.
I started setting up a blog using Hexo. It’s another Node based SSG that uses markdown and supports tags. It has a lot of neat plugins that people have developed, too.
I like it so far!
https://github.com/hexojs/hexo
-
Hexo, WebFinger and better discoverability
In my case, the latter is not possible because this blog is a static site, generated via Hexo and hosted on GitHub. It simply lacks a modifiable active server component.
-
Top ten popular static site generators (SSG) in 2023
Hexo — best lightweight SSG
-
Nuxt 3 - showcase your sites
Previously I've used Nuxt2 and even sooner - hexo.io
-
Building a static blog using Jekyll & Strapi
To make their creation easier, numerous open-source static websites generators are available: Jekyll, Hugo, Gatsby, Hexo, etc. Most of the time, the content is managed through static (ideally Markdown) files or a Content API. Then, the generator requests the content, injects it in templates defined by the developer and generates a bunch of HTML files.
-
Running a blog on GithubPages with Markdown storage
https://gohugo.io/ written in go, support md https://hexo.io/ written in node
-
Comparing Static and Dynamic Websites
Hexo's
-
who is self-hosting a static website and what are you using to build it?
I'm currently using Hexo, I write articles in markdown, commit them to a git repository and push them to Github. I then have a Github Action to bundle the static website and publish it on Github Pages, so I get free hosting 👌
-
Deploy your blog via let.sh
There are also many alternatives for selecting Static-Side Generating blog framework such as Hexo, Gatsby, Next.js (more details here). We will pick Hexo as our framework because it is a fast, simple & powerful blog framework.
-
What I'm Learning in 2022
Some alternatives I'm considering learning instead of Gatsby are Jeckyll or Hexo.
What are some alternatives?
WriteFreely - A clean, Markdown-based publishing platform made for writers. Write together and build a community.
Hugo - The world’s fastest framework for building websites.
blissue - A blog based on github issues
Ghost - Independent technology for modern publishing, memberships, subscriptions and newsletters.
docs - This is a repo of the RetroArch official document page.
Jekyll - :globe_with_meridians: Jekyll is a blog-aware static site generator in Ruby
wayback-machine-downloader - Download an entire website from the Wayback Machine.
Pelican - Static site generator that supports Markdown and reST syntax. Powered by Python.
beleyBlog - The non-content portion for my blog at www.chrisbeley.com
GrapesJS - Free and Open source Web Builder Framework. Next generation tool for building templates without coding
go-readability - A Go implementation of the readability algorithm by arc90 labs
astro - The web framework for content-driven websites. ⭐️ Star to support our work!