Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

agnos.is Forums

  1. Home
  2. Selfhosted
  3. Testing vs Prod

Testing vs Prod

Scheduled Pinned Locked Moved Selfhosted
selfhosted
16 Posts 16 Posters 57 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • N [email protected]

    I've been slowly moving along in this self-hosting journey and now have a number of services that I regularly use and depend on. Of course I'm backing things up, but I also still worry about screwing up my server and having to rollback/rebuild/fix whatever got messed up.

    I'm just curious, for those of you with home labs, do you use a testing environment of some kind that you use, or do you just push whatever your working on straight to "production"?

    J This user is from outside of this forum
    J This user is from outside of this forum
    [email protected]
    wrote on last edited by
    #5

    Nope. I fiddle until it does what I want. If the thing I'm working on is complex or I'm struggling with it I'll keep versions of configs. And I back up working configs via an rsync. Which, isn't a particularly robust solution but I'm content with it for my needs.

    1 Reply Last reply
    0
    • N [email protected]

      I've been slowly moving along in this self-hosting journey and now have a number of services that I regularly use and depend on. Of course I'm backing things up, but I also still worry about screwing up my server and having to rollback/rebuild/fix whatever got messed up.

      I'm just curious, for those of you with home labs, do you use a testing environment of some kind that you use, or do you just push whatever your working on straight to "production"?

      avidamoeba@lemmy.caA This user is from outside of this forum
      avidamoeba@lemmy.caA This user is from outside of this forum
      [email protected]
      wrote on last edited by
      #6

      Sir, every professional developer knows there's never time and people to maintain the testing environment so testing is done in production! That testing environment you're dreaming of is missed shareholder value.

      1 Reply Last reply
      0
      • N [email protected]

        I've been slowly moving along in this self-hosting journey and now have a number of services that I regularly use and depend on. Of course I'm backing things up, but I also still worry about screwing up my server and having to rollback/rebuild/fix whatever got messed up.

        I'm just curious, for those of you with home labs, do you use a testing environment of some kind that you use, or do you just push whatever your working on straight to "production"?

        M This user is from outside of this forum
        M This user is from outside of this forum
        [email protected]
        wrote on last edited by
        #7

        I use testing, prod and stale. Stale is simply one version behind prod in case I see something in prod I need to roll back

        1 Reply Last reply
        0
        • N [email protected]

          I've been slowly moving along in this self-hosting journey and now have a number of services that I regularly use and depend on. Of course I'm backing things up, but I also still worry about screwing up my server and having to rollback/rebuild/fix whatever got messed up.

          I'm just curious, for those of you with home labs, do you use a testing environment of some kind that you use, or do you just push whatever your working on straight to "production"?

          L This user is from outside of this forum
          L This user is from outside of this forum
          [email protected]
          wrote on last edited by
          #8

          I don't have a testing environment, but essentially all my services are on docker saving their data in a directory mounted on the local filesystem. The dockerfile reads the sha version of the image from an env file. I have a shell script which:

          1. Triggers a new btrfs snapshot of the volume containing everyithing
          2. Pulls the new docker images and stores their hashes in the env file
          3. Restarts all the containers.

          if a new Docker version is broken rolling back is as simple as copying the old version in the env file and recreating the container. If data gets corrupted I can just copy the last working status from an old snaphot.

          The whole os is on a btrfs volume which is snapshotted regularly, so ideally if an update fucks it up beyond recovery I can always boot from a rescue image and restore an old snapshot. But I honestly feel this is extra precaution: in years that I run debian on all my computers, it never reached the point of being not bootable.

          1 Reply Last reply
          0
          • N [email protected]

            I've been slowly moving along in this self-hosting journey and now have a number of services that I regularly use and depend on. Of course I'm backing things up, but I also still worry about screwing up my server and having to rollback/rebuild/fix whatever got messed up.

            I'm just curious, for those of you with home labs, do you use a testing environment of some kind that you use, or do you just push whatever your working on straight to "production"?

            themoonisacheese@sh.itjust.worksT This user is from outside of this forum
            themoonisacheese@sh.itjust.worksT This user is from outside of this forum
            [email protected]
            wrote on last edited by
            #9

            My latest project runs on a VM I use vscode's ssh editing feature on. I edit the only copy of the file in existence (I have made no backup and there is no version control) and then I restart the systems service.

            So what if I mess it up? Big deal. The discord bot goes down for a few minutes and I fix it.

            Same goes for the machine configs. Ideally the machines are stable, the critical ones get backups, and if they aren't stable then I suppose the best way to fix it would be in prod ( my VMs run debian, they're stable).

            1 Reply Last reply
            0
            • N [email protected]

              I've been slowly moving along in this self-hosting journey and now have a number of services that I regularly use and depend on. Of course I'm backing things up, but I also still worry about screwing up my server and having to rollback/rebuild/fix whatever got messed up.

              I'm just curious, for those of you with home labs, do you use a testing environment of some kind that you use, or do you just push whatever your working on straight to "production"?

              N This user is from outside of this forum
              N This user is from outside of this forum
              [email protected]
              wrote on last edited by
              #10

              I manage all my homelab infra stuff via ansible and run services via kubenetes. All the ansible playbooks are in git, so I can roll back if I screw something up, and I test it on a sacrificial VM first when I can. Running services in kubenetes means I can spin up new instances and test them before putting them live.

              Working like that makes it all a lot more relaxing as I can be confident in my changes, and back them out if I still get it wrong.

              1 Reply Last reply
              0
              • N [email protected]

                I've been slowly moving along in this self-hosting journey and now have a number of services that I regularly use and depend on. Of course I'm backing things up, but I also still worry about screwing up my server and having to rollback/rebuild/fix whatever got messed up.

                I'm just curious, for those of you with home labs, do you use a testing environment of some kind that you use, or do you just push whatever your working on straight to "production"?

                ambitiousslab@lemmy.mlA This user is from outside of this forum
                ambitiousslab@lemmy.mlA This user is from outside of this forum
                [email protected]
                wrote on last edited by
                #11

                For services only I depend on, I have production-only. Since I can only inflict damage on myself, and can often work around problems.

                For the XMPP server my friends and family also depend on, I have a dedicated nonprod VPS. My services are driven by ansible playbooks, so I'll tweak the playbook with whatever change I want to make works in nonprod, before running the same playbook against prod.

                Whenever there's a new Debian Stable release, I'll rebuild the servers completely, to try and prevent "drift" between the nonprod and prod versions (not that I change things often enough for this to become a big problem). This is also the big test of my backups, which so far haven't been needed in a "real" emergency 🤞

                1 Reply Last reply
                0
                • N [email protected]

                  I've been slowly moving along in this self-hosting journey and now have a number of services that I regularly use and depend on. Of course I'm backing things up, but I also still worry about screwing up my server and having to rollback/rebuild/fix whatever got messed up.

                  I'm just curious, for those of you with home labs, do you use a testing environment of some kind that you use, or do you just push whatever your working on straight to "production"?

                  H This user is from outside of this forum
                  H This user is from outside of this forum
                  [email protected]
                  wrote on last edited by
                  #12

                  Eh, I sometimes spin up a temporary docker container for some nonsense on a separate computer. I usually just go for it after checking no one is on and backing up necessary data.

                  1 Reply Last reply
                  0
                  • N [email protected]

                    I've been slowly moving along in this self-hosting journey and now have a number of services that I regularly use and depend on. Of course I'm backing things up, but I also still worry about screwing up my server and having to rollback/rebuild/fix whatever got messed up.

                    I'm just curious, for those of you with home labs, do you use a testing environment of some kind that you use, or do you just push whatever your working on straight to "production"?

                    M This user is from outside of this forum
                    M This user is from outside of this forum
                    [email protected]
                    wrote on last edited by
                    #13

                    In my case, yes. My setup is managed using Ansible playbooks, so I have a dev inventory and a playbook that spins up a virtualized environment that mimics (as much as possible, as there are a few details that cannot be fully replicated) my home lab.

                    That way, I usually prepare my new setups on dev, and then deploy on my pro setup and test with the few aspects I cannot reproduce in dev.

                    Finally, I have everything backed by a (private) git repo.

                    1 Reply Last reply
                    0
                    • N [email protected]

                      I've been slowly moving along in this self-hosting journey and now have a number of services that I regularly use and depend on. Of course I'm backing things up, but I also still worry about screwing up my server and having to rollback/rebuild/fix whatever got messed up.

                      I'm just curious, for those of you with home labs, do you use a testing environment of some kind that you use, or do you just push whatever your working on straight to "production"?

                      R This user is from outside of this forum
                      R This user is from outside of this forum
                      [email protected]
                      wrote on last edited by
                      #14

                      After breaking "prod" many times, I have a Dev (local machine), Test (small VM) and Prod (big VM). My test is just less RAM and space and I need to spin down certain K8s things to spin up others, but it's a close mirror of Prod, just less.

                      1 Reply Last reply
                      0
                      • N [email protected]

                        I've been slowly moving along in this self-hosting journey and now have a number of services that I regularly use and depend on. Of course I'm backing things up, but I also still worry about screwing up my server and having to rollback/rebuild/fix whatever got messed up.

                        I'm just curious, for those of you with home labs, do you use a testing environment of some kind that you use, or do you just push whatever your working on straight to "production"?

                        S This user is from outside of this forum
                        S This user is from outside of this forum
                        [email protected]
                        wrote on last edited by
                        #15

                        I test stuff on my laptop or desktop and then push it to my NAS. Everything is also containerized and snapshotted, so risk of breaking anything is pretty small.

                        1 Reply Last reply
                        0
                        • N [email protected]

                          I've been slowly moving along in this self-hosting journey and now have a number of services that I regularly use and depend on. Of course I'm backing things up, but I also still worry about screwing up my server and having to rollback/rebuild/fix whatever got messed up.

                          I'm just curious, for those of you with home labs, do you use a testing environment of some kind that you use, or do you just push whatever your working on straight to "production"?

                          I This user is from outside of this forum
                          I This user is from outside of this forum
                          [email protected]
                          wrote on last edited by
                          #16

                          In my job? Yes.

                          At home? God no.

                          I make sure I can recover data when things go wrong, but otherwise my recovery path is redeploying quickly.

                          1 Reply Last reply
                          1
                          0
                          • System shared this topic on
                          Reply
                          • Reply as topic
                          Log in to reply
                          • Oldest to Newest
                          • Newest to Oldest
                          • Most Votes


                          • Login

                          • Login or register to search.
                          • First post
                            Last post
                          0
                          • Categories
                          • Recent
                          • Tags
                          • Popular
                          • World
                          • Users
                          • Groups