• 0 Posts
  • 19 Comments
Joined 11 months ago
cake
Cake day: December 24th, 2023

help-circle


  • Update: seems like the persistence section is sufficient; I have

    persistence:
      enabled: true
      existingClaim: nextcloud-config-claim
    
    

    at the end of my values file which references a volume claim (and volume) that I created manually upfront. The importand file is config.php. Back that thing up immediately and three times, print it if you have to. The secret in there is unrecoverable otherwise and needed for any repair actions.
    I also use the postgresql sub-chart (by simply enabling postgresql as database) and provide a claim there:

    postgresql:
      enabled: true
    global:
        postgresql:
          auth:
            username: XX
            password: YY
            database: nextcloud
      image:
        repository: postgres
        tag: "14"
        postgresqlDataDir: /bitnami/pgdata
      primary:
        persistence:
          enabled: true
          existingClaim: nextcloud-db-claim
    
    

    Hope it helps!


  • I think it was literally called “config”. I will check my setup and provide the mount points I used here later today, if you back these up, it should work. Put some disposable data on it once you finished setup and then upgrade to a newer version to see if everything works. You can specify the image tag to use manually (or you install an older chart version).
    I also pinned the postgres version to 14, not sure if I can recommend that but I had issues with DB upgrades in a docker installation, so I tend to be careful there.


  • True. Have a setup running on Kubernetes with their helm chart but the documentation is (or at least was) insufficient on what is important to back up, so I had to start over once, learning the hard way that the config file contains the one string you always need for recovering data. Since then, it is pretty stable and I had almost no problems.







  • Whenever you accept the TOS, your device is somehow registered/authenticated against their servers. Such a session establishment of course should be secured through TLS, just like all web traffic in general. Frankly, I see the issue here clearly on your side; you have to make sure your device supports up-to-date cryptography standards.

    I saw in a different comment that you do not want to replace your phone but you definitely have to replace your software. Find an older build of lineageOS (well, probably even CyanogenMod in this case) and migrate to that. Even if it is based on Android 8, it would still be much more in line with modern security than what you are running now.
    Btw, the complaint of you not being able to do banking through your browser anymore while it does not support TLS 1.3 really made me laugh, thank you!

    I don’t think you realize just how big the risk is that you are putting yourself in with such old software.








  • Well, if you can pick it up for 10 bucks or less, give it a shot but the story will not blow you away. I played WD2 and legion last year and there was a significant downgrade in story and characters between them. Gameplay was fine but I liked the spider drones in WD2 better than the new drones there.

    It also felt much more political and “modern”, similarly to what they seem to have done for FC6. So depending on your age and maybe political opinions, this might be a pro or a con. I agree with the notion that it becomes very repetitive too.

    Other people here suggested Uncharted and Witcher, definitely go there instead if you can!!