open-gov-crawlers VS burplist

I get feedback occasionally that this is the cleanest web scraping code someone’s seen: https://github.com/public-law/open-gov-crawlers

Writing more scrapers for legal glossaries of many country governments: adding Australia and the UK: https://github.com/public-law/open-gov-crawlers

Here's the repo's README.md with the table. I made this to help onboarding new open-source developers. Also to help people understand what's there.

I find it very agnostic. I use it for app development, not packages. E.g.: https://github.com/public-law/open-gov-crawlers

The original PDF: https://github.com/public-law/open-gov-crawlers/blob/rome-statute-english/docs/Rome-Statute.pdf

For techies, here's the GitHub repo: https://github.com/public-law/open-gov-crawlers/discussions/70

Heroku Dynos apps — Burplist was migrated to Koyeb. Having tried out other notable Heroku alternatives like Fly.io, Northflank, and Railway, I can safely say that the migration from Heroku to Koyeb required the least amount of effort and kinks. It just works in my case.

A little less than a year ago, I built Burplist, a free search engine for craft beer in Singapore. With the goal to keep my infrastructure cost as low as possible, I started off with Heroku Postgres free tier.

The link is to an article about how the search engine was built. The search engine itself can be found here:

https://burplist.me/

You should mention that this is only for Singapore. Nothing wrong with that, just that HN is predomonantly US and if someone goes to https://burplist.me/ searching US craft beers they are going to be a bit unhappy.

Rather than slamming in code examples in this post, I write about a high-level overview of how and why things are done in such a manner. So, you may find links to articles in different sections of this post on the know-how of how some steps were achieved, including the source code.