ominous ocelot

Logseq has how many? And it’s stalled really… from an external viewpoint.

https://github.com/logseq/logseq/graphs/contributors

About 4. Plus the people who maintain plugins.

https://github.com/logseq/logseq/graphs/commit-activity

They didn’t stop working on the code. But you’re right, it doesn’t feel like it UI wise. Which can be a good thing if the status quo is fine.

Markor

Promising. I will take a look.

Yeah, personally, I think they’d gradually make it db first and then markdown will gradually become an import / export function.

Can be. One of the reasons I like md - i’m not bound to one solution.

Still. At one point I will look at silverbullet.

Thanks!
For the interested: They’re working on a logseq edition with db backend as a basis for real time collaboration, better performance, data loss prevention during sync.

FAQ states:

Are you going to deprecate Markdown files support? No, we’ll continue to support both file-based and database-based graphs, with a long-term goal of achieving seamless two-way sync between the database and markdown files. This will allow you to leverage the benefits of the database version while still being able to use other tools.

It looks like, for the moment the md version is there to stay. I’d very much like that, because syncing with git or syncthing.

I’m not sure how useful the collaboration part will be for me. Other tools would have to make room for it in our workflow (ticket system, wiki).

Same here. Silverbullet looks tempting, markdown files and roughly the same feature set as logseq. I tried it out for a few minutes but did not go further.

What holds me back

• there is just one maintainer. What if…
• migration would take some work
• I’m lazy and haven’t tested it out yet

I use logseq and mainly the tagging/ backlink feature (frontmatter and inline) + the usual md language to structure my personal knowledge. Very few queries which I would have to rewrite.

I do not have a real reason to switch away from logseq. It works well enough. There is the occasional full text search search bug which can be circumvented with ripgrep or the like. It takes quite some time to start up - once or twice a day. Otherwise it works.

You say they plan to drop the md support in favour of a DB? Would you please provide a link? Thanks.

Ah. The approach that squirrel@piefed.zip suggested. ;)

Thanks for the tutorial though.

Unattended-Upgrades. Most of the time it is better to risk a faulty upgrade instead of an unpatched remote ACE.

I don’t get the resentment for yuno. In the end it is a hobby. You can have fun building everything from scratch. And you can have fun, using pre configured services.

What counts is that you get away from big corp.

Can’t say much about your tutorial though. Didn’t read it. I’m sorry. ;)

I use their wifi APs because they make them really easy to configure and manage. But the management interface stays locked in a vlan without access to the internets. Because I don’t trust their cloud affinity.

This also disqualifies their routers and firewalls for me. How can I trust a device which tries to phone home? So that area is covered by opnsense on a device with a sufficient amount of Ethernet ports.

Any device with a mass storage can act as a NAS - a single board computer + Linux + samba/ nfs/ scp/ sftp. I heard TrueNAS or OpenMediaVault are recommended as all in one solutions - I don’t know them.

Verbose please? What happened?

E: thank you all. Especially lambdaRX’ hint to a summary (comment 234 by GrabbenD) helped me.

I’ve been hinking about infrastructure as code tools. Skimmed the very surface of opentofu, looked at the list of alternatives.

I’m in need of something that is both, deployment automation and (implicit) documentation of the thing that I call “the zoo”. Namely:

• network definition
• machine definitions (VMs, containers) and their configuration
• inventory: keeping track of third party resources

Now I think about which tool would be the right one for the job while I’m still not 100% sure what the job is. I don’t like added complexity, it is quite possible this could become a dead end for me, if I spend more time wrangling the tool than I gain in the end.

PS: If you haven’t already, please take a look at your openssl packages. Since this week there are two new CVEs rated as high: https://openssl-library.org/news/vulnerabilities/index.html

I wouldn’t say silent, it’s very audible when they switch from 6 to 25 °C. But I don’t observe that occasional self regulating behaviour. So I don’t mind.

Moot point!

You could still get certificates for other people’s domains from Honest Ahmed 's used cars and totally trustworthy CA or so. But that’s another story. (there are A LOT of trusted CAs in everybody OS and browser. Do you know and trust them all?)

It’s the “change your password often odyssey” 2.0. If it is safe, it is safe, it doesn’t become unsafe after an arbitrary period of time (if the admin takes care and revokes compromised certs). If it is unsafe by design, the design flaw should be fixed, no?

Or am I missing the point?

Thanks. I looked into the demo. When would you recommend pdfding over paperless ngx? It looks like easy sharing and annotations are focused. Tagging is a feature which both tools share.

At first I thought it would be a tool like pdf24 (cutting, merging, editing PDFs).

I would get some cheap maybe even used X86 hardware to start with. Depending on your backup needs, you might need more than one M2 or SATA port. If you plan to use it as an always on device, I would keep the power consumption in mind. A celeron N could be the way. The cpu processing power is, in my experience, not the limiting factor for a self-hosted environment. Give it lots of RAM, every virtual machine and every running service needs space.

Using arm, like a Raspberry Pi, is not bad if you can find all your Docker images and binaries, compiled for this platform. I went away from it.

There are many possible distributions and software you could use, it really depends on personal preference.

You can never be sure. Regressions do happen.

First evaluate it on your test setup.
— useless hint of the day

Some fs can do snapshotting (btrfs, zfs,…). Second best would be a current backup to restore from.

rsnapshot is a script for the purpose of repeatedly creating deduplicated copies (hardlinks) for one or more directories. You can chose how many hourly, daily, weekly,… copies you’d like to keep and it removes outdated copies automatically. It wraps rsync and ssh (public key auth) which need to be configured before.

• journalctl shows the oom event
• Container limits you can limit container resource usage
• also you can look at container stats to maybe identify the culprit. Or cyclically write the stdout of ps to a file to identify the memory hungry process.

Debian + LVM + Incus :)

The h4 already can be a managed switch itself (2" 2,5gbit + 4*1gbit with the nic addon.) if you want it to be one. Linux as the host OS (VLANs, bridges) - netplan works well for me. Some VMs and containers on top (lxd, incus, some use proxmox) for router/ firewall/ vpn-gateway (opnsense, ipfire,…) and other functionality which you don’t want to run on the host OS directly. The cpu is fast enough to run all your services at once. It all comes down to RAM.

IMO there is not one right way. It all depends on what you want to achieve. Also a lot depends on, whether you want results fast or if you enjoy the tinkering while learning.