this post was submitted on 03 Aug 2026
467 points (97.4% liked)

Linux

14565 readers
1075 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 3 years ago
MODERATORS
 

what internship are you doing?

you are viewing a single comment's thread
view the rest of the comments
[–] AnimalsDream@slrpnk.net 15 points 1 day ago (3 children)

The thing that I hate about self-hosting is that a lot of apps that could just be a plain offline thing are instead being designed to be super bloated server-docker things. Databases are not reasonably portable data formats.

[–] RamenJunkie@midwest.social 2 points 1 day ago

This is why my self created apps all use Markdown files instead if DBs.

[–] zaphod@sopuli.xyz 3 points 1 day ago (1 children)

An sqlite database is a perfectly fine portable data format.

[–] AnimalsDream@slrpnk.net 3 points 1 day ago (1 children)

Or, and apparently this is crazy these days - I can just use a file that's in a format appropriate to what I'm trying to do, compatible with the simpler offline app it was made for, and then just use a more general purpose syncing method whether online or sneakernet if I need to do some kind of data transfer - as opposed to accumulating an ever expanding collection of server stacks that are just redundantly doing the same kind of thing anyway while needlessly adding an insane amount of attack surface.

[–] TehPers@beehaw.org 1 points 21 hours ago

SQLite allows for more efficient querying of data than doing it by hand, can enforce constraints on the data, and I can query it from my shell.

Of course it's not going to replace a commonly-used format for a domain. If no such format exists, it's a perfectly acceptable data format for data that's tabular in nature. And it can by sync'd/backed up the same as any other file.

[–] 0x0@lemmy.zip 5 points 1 day ago

Databases are not reasonably portable data formats.

I mean.. if you stick to standard SQL...