all-in-one icon indicating copy to clipboard operation
all-in-one copied to clipboard

📦 The official Nextcloud installation method. Provides easy deployment and maintenance with most features included in this one Nextcloud instance.

Results 188 all-in-one issues
Sort by recently updated
recently updated
newest added

This change adds a guide for provisioning multiple VMs to run their own AIO instances. My idea is to provide a thorough guide that is easy to follow and gets...

2. developing
documentation

This is a new pull request that follows the previous one from @burnclouds, which has not been merged due to no responses. I just reused his work, with small fixes...

3. to review
enhancement

Default installation does not work because default namespace already exists. TODO: Wrap the namespace in an if statement (if not `default`). `nextcloud-aio-helm-chart/templates/nextcloud-aio-namespace-namespace.yaml`

1. to develop
bug

Broken deployments that I noticed: - nextcloud - apache TODO: Check all deployments with `ReadWriteOnce` PVCs. ```yaml strategy: type: Recreate ```

1. to develop
bug

Every ~10 days, my Nextcloud instance becomes unresponsive - Webinterface wont load - calendar sync stops working - even on ssh, login hangs and times out - AIO:8443 login prompt...

0. Needs triage
bug
needs info

1. to develop
dependencies
upstream
blocked

See https://github.com/nextcloud/all-in-one/issues/4239 and https://github.com/nextcloud/all-in-one/pull/4253 Possibly it was caused by malfunctioning docker hub during upgrade... Hopefully https://github.com/nextcloud/all-in-one/pull/4256 prevents such things in the future

1. to develop
help wanted
dependencies

I have added a small explenation on how you need to use the `network_mode: host` option if you use the nginx-proxy-manager as a container on the same machine as the...

3. to review
documentation

- [ ] needs https://github.com/nextcloud/server/pull/45039 or https://github.com/nextcloud/server/pull/45040

1. to develop
enhancement
upstream
blocked

### Steps to reproduce 1. Pull docker-compose.yaml from the repo 2. add "SKIP_DOMAIN_VALIDATION=true" to the environment list 3. start container 4. open public_ip:8080 ### Expected behavior Domain Check should be...

0. Needs triage
bug