I’m still using the self hosted docker image, the all in one is too bloated for me and my computing resources are quite limited. Why would I like an antivirus? Or a backup solution different than the one I use to backup the rest of my containers?
Cool initiative anyway for other kind of users though.
Jesus Ritchie Christ, can we de-normalize ‘run anonymous superscript as root’ bullshit? It’s dumb when Oracle does it, it’s dumb when SuSE does it. It’s dumb all the time.
I appreciate the simplicity, but giving such broad permissions makes me unease and the main reason why I’m putting off moving to Nextcloud AIO. Am I the only one who thinks like this?
Love me some docker compose! I switched from a manually built VM over to the AIO setup about a year ago and never looked back. It’s been rock solid for me and my ~10 users so far.
It containerizes all the subcomponents under a mastercontainer, and even has support for community containers of things like pihole, caddy and dlna. So you have image control over each component, as well as codespace separation.
After 7 or 8 years of various forms of Nextcloud, I have to say this is the easiest one to maintain, upgrade and backup outside of my VM snapshots.
Not really, it just makes containers in your docker, accessible like any others. The mastercontainer can be used to control and update them, but you can just exec -dit them like any other containers you find in your docker ps
One of the first services on my server was nextcloud in docker container from lsio. Never had problems so there was no need to try AIO, but so many people recommend that, it will be my next setup if this one fails me
I decided to go with this one because it’s now the official distribution channel and supported by the devs. But the lsio one looks pretty solid as well.
As in, I have Nginx running on my server and use it as a reverse proxy to access a variety of apps and services. But can’t get it playing nicely with AIO Nextcloud.
I was about to ask why this is better than the docker installation, but I see step one is to install docker haha.
I’ve been running the docker container for a long time, it works very well. It is a bit more complicated if you try and use extensions that require seperatw containers (like setting up collabora), but that can be done as well. It’s just more complicated.
I do remember needing to know how to access the internal terminal a few times, but I don’t remember why. If I think of it I’ll come back and add instructions.
As a former self-configured docker compose NC user, I have to say I’m way happier with the AIO. But still, the older docker method was head and shoulders over any other method of running NC that I’d used.
I wish I could’ve like next cloud more, but it seemed bloated as all hell and was slow regardless of what machine I tried running it on :(. I might give it another go one day.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
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
I’m still using the self hosted docker image, the all in one is too bloated for me and my computing resources are quite limited. Why would I like an antivirus? Or a backup solution different than the one I use to backup the rest of my containers?
Cool initiative anyway for other kind of users though.
Running the AV container is optional, as is using the integrated backup solution. But I can see how that might feel bloated if you don’t need it.
curl -fsSL https://get.docker.com | sudo shJesus Ritchie Christ, can we de-normalize ‘run anonymous superscript as root’ bullshit? It’s dumb when Oracle does it, it’s dumb when SuSE does it. It’s dumb all the time.
This is all in one container? That is the exact wrong way to use docker.
No, you give the AIO container access to your docker daemon and it will create / handle / supervise all the other containers nextcloud needs.
Damn, why not use k8s at that point
I appreciate the simplicity, but giving such broad permissions makes me unease and the main reason why I’m putting off moving to Nextcloud AIO. Am I the only one who thinks like this?
Its OK if you have a dedicated VM just for nexcloud
Love me some docker compose! I switched from a manually built VM over to the AIO setup about a year ago and never looked back. It’s been rock solid for me and my ~10 users so far.
It containerizes all the subcomponents under a mastercontainer, and even has support for community containers of things like pihole, caddy and dlna. So you have image control over each component, as well as codespace separation.
After 7 or 8 years of various forms of Nextcloud, I have to say this is the easiest one to maintain, upgrade and backup outside of my VM snapshots.
So it’s sub containers?
deleted by creator
Not really, it just makes containers in your docker, accessible like any others. The mastercontainer can be used to control and update them, but you can just
exec -ditthem like any other containers you find in yourdocker psOne of the first services on my server was nextcloud in docker container from lsio. Never had problems so there was no need to try AIO, but so many people recommend that, it will be my next setup if this one fails me
I decided to go with this one because it’s now the official distribution channel and supported by the devs. But the lsio one looks pretty solid as well.
I’m setting it up. Only having some issues with proxy manager and cloudfare combo.
This has helped me a lot in my scenario.
Yes thanks. I’m using it already but for now can’t get it working.
Yes I’ve not managed to solve this yet. For me, it’s hosting AIO behind my existing Nginx.
Behind existing Nginx? Do you mean that you are not using Nginx and only cloudfare tunnel?
As in, I have Nginx running on my server and use it as a reverse proxy to access a variety of apps and services. But can’t get it playing nicely with AIO Nextcloud.
That’s my issue too.
Whats this used for?
Nextcloud is a web-based, open-source cloud / collaboration software suite, which can be self-hosted
Didn’t knew it exists. That might make me give nextcloud another chance. Thanks man.
Welcome. I use it in conjunction with Fedora CoreOS so I hopefully never have to manually update anything ever again.
I was about to ask why this is better than the docker installation, but I see step one is to install docker haha.
I’ve been running the docker container for a long time, it works very well. It is a bit more complicated if you try and use extensions that require seperatw containers (like setting up collabora), but that can be done as well. It’s just more complicated.
I do remember needing to know how to access the internal terminal a few times, but I don’t remember why. If I think of it I’ll come back and add instructions.
Edit: It’s to be able to run occ commands:
Sudo docker exec -u www-data nextcloud-app php occ “Command goes here”
Sudo docker exec -u www-data nextcloud-app php occ files:scan --all
As a former self-configured docker compose NC user, I have to say I’m way happier with the AIO. But still, the older docker method was head and shoulders over any other method of running NC that I’d used.
With AIO it’s almost the same:
sudo docker exec -u www-data nextcloud-aio-nextcloud php occ <command>I wish I could’ve like next cloud more, but it seemed bloated as all hell and was slow regardless of what machine I tried running it on :(. I might give it another go one day.