faenz
litestream
faenz | litestream | |
---|---|---|
5 | 165 | |
15 | 9,997 | |
- | - | |
7.6 | 7.5 | |
12 days ago | 14 days ago | |
Ruby | Go | |
- | 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.
faenz
-
Running a funny experiment with my free web-analytics
Two years back, I created a little web analytics tool for my side projects and I called Faenz. It's open source and self-hostable, available on GitHub at https://github.com/a-chris/faenz.
I've recently given it an update and came up with the idea of creating a demo version that's accessible to everyone.
How does it work?
You can add your own website, blog or e-commerce site and keep track of the visits it receives. Your website stats will be visible to others, and you'll get to check out everyone else's stats too. You won't be allowed to edit/delete a website, you should reach out to me for that.
I find it to be a fun experiment to see how people handle SEO or just to discover some cool new websites :)
The demo is available here https://faenz.acmecorp.dev/
- Il Garante della privacy Italiana dichiara lo stop all’uso di Google Analytics per il trasferimento dei dato negli USA senza garanzie adeguate
-
Small tip to shrink your Docker images size
Here is the project I'm working on: Faenz Analytics
- Ask HN: Have you used SQLite as a primary database?
-
Ask HN: Have you created programs for only your personal use?
I've built several personal projects to be honest; background jobs, tasks automation, telegram bots to find a house to rent or buy, most of them are kept provate.
The two I'm most proud of are a web analytics that, coincidentally, I've made public today after a few weeks of work:
https://github.com/a-chris/faenz
I developed it for collect data for my personal website and it is working well so far, really happy of it.
The other one is a Google Chrome extension to manage bookmark because I think the default one is a mess and very unpratical to use. I haven't worked on it for a while:
https://github.com/a-chris/peffect-bookmarks-manager
litestream
-
Ask HN: SQLite in Production?
I have not, but I keep meaning to collate everything I've learned into a set of useful defaults just to remind myself what settings I should be enabling and why.
Regarding Litestream, I learned pretty much all I know from their documentation: https://litestream.io/
-
How (and why) to run SQLite in production
This presentation is focused on the use-case of vertically scaling a single server and driving everything through that app server, which is running SQLite embedded within your application process.
This is the sweet-spot for SQLite applications, but there have been explorations and advances to running SQLite across a network of app servers. LiteFS (https://fly.io/docs/litefs/), the sibling to Litestream for backups (https://litestream.io), is aimed at precisely this use-case. Similarly, Turso (https://turso.tech) is a new-ish managed database company for running SQLite in a more traditional client-server distribution.
-
SQLite3 Replication: A Wizard's Guide🧙🏽
This post intends to help you setup replication for SQLite using Litestream.
-
Ask HN: Time travel" into a SQLite database using the WAL files?
I've been messing around with litestream. It is so cool. And, I either found a bug in the -timestamp switch or don't understand it correctly.
What I want to do is time travel into my sqlite database. I'm trying to do some forensics on why my web service returned the wrong data during a production event. Unfortunately, after the event, someone deleted records from the database and I'm unsure what the data looked like and am having trouble recreating the production issue.
Litestream has this great switch: -timestamp. If you use it (AFAICT) you can time travel into your database and go back to the database state at that moment. However, it does not seem to work as I expect it to:
https://github.com/benbjohnson/litestream/issues/564
I have the entirety of the sqlite database from the production event as well. Is there a way I could cycle through the WAL files and restore the database to the point in time before the records I need were deleted?
Will someone take sqlite and compile it into the browser using WASM so I can drag a sqlite database and WAL files into it and then using a timeline slider see all the states of the database over time? :)
-
Ask HN: Are you using SQLite and Litestream in production?
We're using SQLite in production very heavily with millions of databases and fairly high operations throughput.
But we did run into some scariness around trying to use Litestream that put me off it for the time being. Litestream is really cool but it is also very much a cool hack and the risk of database corruption issues feels very real.
The scariness I ran into was related to this issue https://github.com/benbjohnson/litestream/issues/510
-
Pocketbase: Open-source back end in 1 file
Litestream is a library that allows you to easily create backups. You can probably just do analytic queries on the backup data and reduce load on your server.
https://litestream.io/
- Litestream – Disaster recovery and continuous replication for SQLite
- Litestream: Replicated SQLite with no main and little cost
-
Why you should probably be using SQLite
One possible strategy is to have one directory/file per customer which is one SQLite file. But then as the user logs in, you have to look up first what database they should be connected to.
OR somehow derive it from the user ID/username. Keeping all the customer databases in a single directory/disk and then constantly "lite streaming" to S3.
Because each user is isolated, they'll be writing to their own database. But migrations would be a pain. They will have to be rolled out to each database separately.
One upside is, you can give users the ability to take their data with them, any time. It is just a single file.
[0]. https://litestream.io/
-
Monitor your Websites and Apps using Uptime Kuma
Upstream Kuma uses a local SQLite database to store account data, configuration for services to monitor, notification settings, and more. To make sure that our data is available across redeploys, we will bundle Uptime Kuma with Litestream, a project that implements streaming replication for SQLite databases to a remote object storage provider. Effectively, this allows us to treat the local SQLite database as if it were securely stored in a remote database.
What are some alternatives?
termdbms - A TUI for viewing and editing database files.
rqlite - The lightweight, distributed relational database built on SQLite.
dqlite - Embeddable, replicated and fault-tolerant SQL engine.
pocketbase - Open Source realtime backend in 1 file
ws4sqlite - Query sqlite via json+http
realtime - Broadcast, Presence, and Postgres Changes via WebSockets
k8s-mediaserver-operator - Repository for k8s Mediaserver Operator project
sqlcipher - SQLCipher is a standalone fork of SQLite that adds 256 bit AES encryption of database files and other security features.
litefs - FUSE-based file system for replicating SQLite databases across a cluster of machines
flyctl - Command line tools for fly.io services
datasette - An open source multi-tool for exploring and publishing data
PostgreSQL - Mirror of the official PostgreSQL GIT repository. Note that this is just a *mirror* - we don't work with pull requests on github. To contribute, please see https://wiki.postgresql.org/wiki/Submitting_a_Patch