Docs Improvement - Accessing NextCloud after AIO setup, Reverse Proxy Improvement

[surapuramakhil]

Steps to reproduce

1. Go through AIO docs
2. Try to Setup NextCloud using NextCloud AIO
3. you might be able to access nextCloud AIO instance - but you are stuck in accessing next cloud instance.

you will realize that next cloud AIO is manager for next cloud.

Expected behavior

you shouldn't be facing this issue

Actual behavior

you are clue less - how you can access Next Cloud instance that you made setup using AIO

Other information

Host OS

Output of sudo docker info

Docker run command or docker-compose file that you used

Other valuable info

[szaimen]

you will realize that next cloud AIO is manager for next cloud.

Expected behavior

you shouldn't be facing this issue

Actual behavior

you are clue less - how you can access Next Cloud instance that you made setup using AIO

Hi, I agree on this but how can we improve the situation? Simply adding a chapter to the top of the rp docs how AIO works internally maybe? Do you have some ideas?

[surapuramakhil]

Hi, I agree on this but how can we improve the situation? Simply adding a chapter to the top of the rp docs how AIO works internally maybe? Do you have some ideas?

Can I raise PRs for this & you can review those

[szaimen]

Hi, I agree on this but how can we improve the situation? Simply adding a chapter to the top of the rp docs how AIO works internally maybe? Do you have some ideas?

Can I raise PRs for this & you can review those

Yes, please do. Sounds good :)

[szaimen]

Hi, I agree on this but how can we improve the situation? Simply adding a chapter to the top of the rp docs how AIO works internally maybe? Do you have some ideas?

Can I raise PRs for this & you can review those

Hi @surapuramakhil any update here?

[surapuramakhil]

@szaimen I am in the process of evaluating borgbase - which has made this "nextCloud" as anti-cloud rather than being cloud native.

@szaimen I am evaluating efforts - moving to nextCloud knowing about backup pitfalls.

borgbackup is an amazing tool but it has made this entire setup restricted to brogbase (their backup storage service)

[szaimen]

but it has made this entire setup restricted to brogbase (their backup storage service)

No. You can also simply use any server that runs borg as target or use a local directory on the server, including network mounts. See https://github.com/nextcloud/all-in-one?tab=readme-ov-file#are-remote-borg-backups-supported

[surapuramakhil]

use a local directory on the server

This has loss of storage (as storage requred for backups) . This storage is typically taken from capacity allocated to nextCloud.

You can also simply use any server that runs borg as target, including network mounts.

Even if I have storage, I prefer it in increasing capacity of my nextCloud rather than using it for backups. do you do this in in rented server it will be expensive.

All these thoughts led me to restricted to brogbase (or) other alternative I have is rsync.net

@szaimen can you comment on this. what you think etc.

@szaimen you can expect a week of time for this.

[szaimen]

@szaimen you can expect a week of time for this.

okay

[szaimen]

@surapuramakhil any update here?