Selfhosted

39937 readers

375 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Nextcloud appreciation post (lemmy.ml)

submitted 6 months ago by Yerbouti@lemmy.ml to c/selfhosted@lemmy.world

26 comments fedilink hide all child comments

After months of waiting, I finally got myself an instance with Libre Cloud. I was expecting basic file storage with a few goodies but boy, this is soooo much more. I am amaze by how complete this is!!! Apps let me configure my instance to fit everything I need, my workflow is now crazy fast and I can finally say goodbye to gdrive, gsuite, trello, calendar, etc. All of this, with 1tb while not giving any of ma data to some evil business for... 10$ cad a month!? Can't believe this is not what every organisation are using.

you are viewing a single comment's thread
view the rest of the comments

[–] x3i@kbin.social 3 points 6 months ago (1 children)

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.

[–] moonpiedumplings@programming.dev 1 points 6 months ago (2 children)

What was it? I'm planning to do a nextcloud deployment via helm soon.

[–] x3i@kbin.social 1 points 6 months ago

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!

[–] x3i@kbin.social 1 points 6 months ago

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.