• 0 Posts
  • 15 Comments
Joined 5 months ago
cake
Cake day: June 30th, 2025

help-circle




  • I separate the name from the ID, so the IDs are relative to the specific device only, and the names represent the device and location.

    I’ve set the IDs for all my sensors to use a code. The letters identify the type of sensor, and the numbers are sequential when I got them. I also have a label maker and labeled all the devices with their codes.

    Example:

    AA##
    

    So my first temperature sensor is

    TS01
    

    Then the name of the sensor is a little more elaborate, where it includes the type of the sensor, the code, and the location.

    {Type} {ID} - {Location}
    

    So my bedroom motion sensor is:

    Motion MS02 - Bedroom
    

    Then if I have to rearrange anything, I don’t update the device ID, just the name and how it’s used.

    I recently moved and had to rearrange some of the devices. It wasn’t as bad as it could have been as I tried sticking the sensors in the proper rooms (ie all the old bedroom devices stayed in the bedroom). But there were some cases where I did have to rename them & update the integrations.





  • I was thinking OP could give everyone their own VM to use as a workstation so they could access the files on the server easily, and/or run programs based on their work. When their coworkers leave, OP can easily destroy the VM and the resources would be automatically reallocated (depending on the servers configuration). With a physical device, the storage on that device is only allocated to that device and can’t be shared when it’s not in use

    Me, personally? I have multiple VMs for different contexts: my teaching job (super clean, video sharing tools, presentation tools), gaming, media server (has scripts to download stuff off of YouTube), server management (just a regular Debian install), and a fuck around box (I just use it to try new OSs like Fedora, or try breaking OSs like deleting the system32 folder on windows)




  • CocaineShrimp@sh.itjust.workstoFediverse@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    25
    arrow-down
    1
    ·
    4 months ago

    As much as I want to see Lemmy and the rest of the fediverse flourish; at the same time, I hope it doesn’t.

    Once the fediverse becomes popular and gains main-stream attention, the billionaires and political twats will flock towards it and try to monetize it; Morons will flood the fediverse with memes and AI slop worse than !lemmyshitpost@lemmy.world (you know what you’ve done); corporations will start spamming ads for their shitty products; and scammers will start setting up bot nets to coerce users into sending them money to their new AI waifus.

    The unbearable weight of all the garbage entering and attacking the fediverse will drive moderators out the door, leaving servers as wastelands of junk. No longer interesting, no longer human. Just trash, like how Reddit, Facebook, Instagram, etc… are today.

    So yes, I’ll welcome friends and family into the fediverse with open arms. But I really hope we don’t start getting too many shout outs





  • I haven’t gone through your specific case, but generally what I do when doing a major update with potentially breaking changes:

    • Read the upgrade guides, if they have them. Some devs will put them out if they know their users will encounter issues when upgrading. If they don’t have an upgrade guide, there might be some in the change logs. Going from 1.17.1 to (assuming) 2.x.y, check the change logs at 2.0.0.
    • Backup everything. I’d recommend doing this on a regular basis anyway.
    • (If you’re running it in a docker container) Setup a second instance, restore the backup, then run the upgrade. You’ll be able to check to see if it breaks at all. If it works, you can just destroy the old one and use the new one
    • (if you’re not running it in a container) with the backup, try upgrading. If it breaks, you should be able to uninstall & reinstall the old version, then restore the backup