These projects are poorly maintained and abandoned because the industry of email has been reduced to a very few players, and they don’t care about IMAP standards, dmarc, dkim or any of it.

You’re running head on into the primary reason no one self-hosts email anymore; it has gone from being a nuisance to being adversarial.

Oh, nice. Thanks!

This is me showing my docker ignorance, I suppose.

I just snapshot the parent lxc. The data itself isn’t part of the container at any level, so if I bung up compose yml or env, I can just flip it back. The only real benefit is that all my backups are in the same place in the same format.

Like I’m not actually opposed to managing docker in one unit, I just haven’t got there yet and this has worked so far.

If I were to move to a single platform for several docker, what would you suggest? For admin and backups?

Lxc and docker are not equivalent. They are system and software containers respectively.

I use individual lxc for each docker compose so I don’t have to revert 8 services at once if I need to restore.

I would also argue that an alpine lxc runs in 22mb ram by itself … Significantly smaller footprint on disk and in memory. But most importantly, lxc can actually share memory space effectively, one doesn’t need to reserve blocks of ram.

Thank you for replies, I’m grateful.

Sorry to pester you, but I’m confused: my google calendar app does not allow removing the original google calendar. How were you able to do so?

And both of your installs can sync from device to NC? I have not been able to get around this… Only one-way sync from NC to davx to 3rd party android calendar.

Which calendar client did you use?

I thought the switch to nextcloud calendar was going to be simple, but davx is … Not a clean-cut app.

• Did you find a way to sync from device to NC?
• Were you able to merge Google’s dumb export of 3 calendars?

So I went to the demo and I have a few questions:

• Couldn’t figure out how to use 3d in demo (not critical)
• developer discord link on github is expired
• distinction between “public” and “shared” trails isn’t clear
• “Completion Status” for trails… what does this mean?
• Couldn’t import a trail in demo:

haystack-mountain-101522-105940.gpx
{"message":"TypeError: Cannot read properties of null (reading 'id')"}

I am actually really impressed with what you have so far, and I’d love to start using this!

Ok, I think I can deal with recording on an OSM client. I’ll give Wanderer a try.

I want to try this. I’m one of the unfortunate victims of Gaia GPS turning to trash.

However, I can’t seem to find in the docs how tracks can be recorded…

Is there an app?

Do I need to be in contact with the server to record a track?

Do I need to ask my friends to send me gpx exports if they aren’t on strava?

Do you envision an integration with opentrailmap so in can share trails without having to expose Wanderer to public?

It’s not actually going that great, there is already infighting on the direction of the scripts.

Are you having trouble reading context?

No, I’m not applying 2005 security, I’m saying NFS hasn’t evolved much since 2005, so throw it in a dedicated link by itself with no other traffic and call it a day.

Yes, iscsi allows the use of mounted luns as datastores like any other, you just need to use the user space iscsi driver and tools so that iscsi-ls is available. Do not use the kernel driver and args. This is documented in many places.

If you’re gonna make claims to strangers on the internet, make sure you know what you’re talking about first.

Yes, i have. Same security principles in 2005 as today.

Proxmox iscsi support is fine.

Oh, OK. I should have elaborated.

Yes, agreed. It’s so difficult to secure NFS that it’s best to treat it like a local connection and just lock it right down, physically and logically.

When i can, I use iscsi, but tuned NFS is almost as fast. I have a much higher workload than op, and i still am unable to bottleneck.

I don’t know what you’re on about, I’m talking about segregating with vlans and firewall.

If you’re encrypting your San connection, your architecture is wrong.

Your workload just won’t see much difference with any of them, so take your pick.

NFS is old, but if you add security constraints, it works really well. If you want to tune for bandwidth, try iSCSI , bonus points if you get zfs-over-iSCSI working with tuned block size. This last one is blazing fast if you have zfs at each and you do Zfs snapshots.

Beyond that, you’re getting into very tuned SAN things, which people build their careers on, its a real rabbit hole.

According to this, 6.2.4.x is not affected.

OVS is fine, you can make live changes and something like spanning port traffic is a bit less hassle than using tc, but beyond that, it’s not really an important component to a failover scenario over any other vswitch, since it has no idea what a TCP stream is.

For sure, if your thing is leaning into network configs, nothing wrong with it, especially if you have proper failover set up.

I think virtualized routing looks fun to the learning homelabber, and it is, but it does come with some caveats.