HybridSarcasm

joined 1 year ago
MODERATOR OF
[–] [email protected] 4 points 2 weeks ago

This is a question probably better-suited for one of the Proxmox communities. But, I’ll give it a try.

Regarding your concerns about new SSDs and old VM configs: why not upgrade to PVE8 on the existing hardware? This would seem to mitigate your concerns about PVE8 restoring VMs from a PVE7 system. Still, I wouldn’t expect it to be a problem either way.

Not sure about your TrueNAS question. I wouldn’t expect any issues unless a PVE8 installs brings with it a kernel driver change that is relevant to hardware.

Finally, there are several config files that would be good to capture for backup. Proxmox itself doesn’t have a quick list, but this link has one that looks about right: https://www.hungred.com/how-to/list-of-proxmox-important-configuration-files-directory/

[–] [email protected] 4 points 2 weeks ago (1 children)

Is there any actual research? All I see are TikTok videos and Reddit comments.

[–] [email protected] 37 points 3 weeks ago (1 children)

Love another iOS option.

[–] [email protected] 4 points 4 weeks ago (1 children)

Nextcloud Photos performs okay, but the interface is very ‘meh’. Plus, the mobile client’s sync is a little unstable. On iOS, there’s no background sync at all.

[–] [email protected] 2 points 1 month ago

This seems the correct advice. If the container is on the same host as the data, there’s no need to access the data via Samba. In fact, it’s likely the container doesn’t contain the samba client needed for such connectivity.

Assuming TrueNAS allows the containers to see local data, a bind mount is the way to go.

[–] [email protected] -3 points 1 month ago (1 children)

Maybe some castration along the way, too.

[–] [email protected] 2 points 1 month ago (1 children)

Right. You kind of want your bare metal OS as vanilla as possible. If you need to nuke and pave, you don’t need to worry about re-applying various configs. Additionally, on a theoretical level, if there’s a bug in something on the bare metal OS, the separation provided by VMs and containers should mean it doesn’t affect the the apps in those VMs / containers.

That seems easier - at least to me - than keeping track of configs in text files or even Ansible playbooks.

[–] [email protected] 22 points 1 month ago (1 children)

This is good stuff. Has it been posted to the project’s GitHub (issue, discussion, etc.)?

[–] [email protected] 7 points 1 month ago (2 children)

Just watched this episode. It was as fun as a Q episode can be. Slightly annoying that the omnipotent beings can come around and NOT whoosh Voyager forward on the journey home.

[–] [email protected] 3 points 1 month ago (3 children)

Have you considered searching the GitHub issues?

[–] [email protected] 77 points 1 month ago (15 children)

I love how the ONE time they did, all the fears were validated.

 

As is stated in the title, I created and moderated [email protected]. According to the modlog, this community was removed 10 days ago. The modlog doesn't show me who removed the community. I understand the community wouldn't necessarily be everyone's cup of tea, but the actions taken seem improper.

EDIT

After making my case via email to [email protected], I received the following response:

"We would rather not have a prolife community on our instance. We were getting a lot of reports about it and we have enough on our plate. I'm sure you can find an instance that better suits your needs."

This community was incredibly small (19 subscribers), had less than 10 postings, and had several waves of trollings. Yet, the admins of lemmy.world would rather do away with this community than bother to review if it has broken any rules or is the target of trolling/bullying. I take nothing away from the right to run their instance as they see fit. Perhaps the Code of Conduct should also explicitly state "we reserve the right to do anything we want, regardless of any published rules".

view more: next ›