GLWS · Files and collaboration
Bring file synchronisation, sharing and collaborative tools into a workspace you administer.
Common uses of Nextcloud.
Review the supported PHP and database combinations. File volume, enabled apps, previews and background jobs all affect resource requirements.
Planning examples, not official minimum requirements.
Files and collaboration
Check the current supported operating systems, deployment methods, dependencies and licence terms. What you need depends on your workload, not just the application's name.
Large datasets and busy workloads can need far more memory, storage or different hardware. Any external API or service subscriptions are separate.
Read the Nextcloud documentation ↗ (opens in a new tab)Advice specific to this application.
Count the users, devices and files that will synchronise with the server. Leave storage space for versions, deleted-file retention and previews. Background processing and additional collaboration apps can need more resources than an idle file browser.
The database, data directory and configuration belong to the same recovery set. Document how background jobs run and how maintenance mode fits into backups and upgrades. Test restoration with a separate instance before depending on synchronised files as your only copy.
Linux guides that help with this setup.
Run Nextcloud with a database and Redis in Docker Compose, plan storage, set up cron, publish it with HTTPS, then update, back up and restore it.
Read guide →Pin image versions, back up persistent data, pull and check an update, and roll back to the previous version if it fails.
Read guide →Back up to a second server over SFTP with restic, encrypt everything, schedule it with a systemd timer and prove you can restore.
Read guide →Four steps that make the environment easier to maintain.
Read the publisher's instructions and choose a supported installation method.
Protect the dashboard, credentials and network endpoints before you expose any service.
Work out where the application keeps its state and store it separately from replaceable runtime files.
Back up the data and configuration, then check that you can restore them.
Run through it before and after you install.
$ application-checklist --name nextcloud
[ ] Supported deployment method
[ ] Authentication and access restrictions
[ ] Independent data backup
[ ] Updates and restoration tested
root@glws:~#
Quick answers before you choose resources.
No. The configurator only saves your application preference. It does not connect to any infrastructure or run an installer.
Use the planning example as a starting point only. Check the publisher's requirements and measure the whole stack under a realistic workload.
You do. Self-hosted applications need updates, configuration and recovery planning from the operator. The publisher's documentation describes supported maintenance.
The knowledge base covers Linux access, packages, services, firewalls and backups.
Other tools you might run alongside or instead.
Website, email, DNS and database management in a hosting dashboard.
Explore application →A self-hosted assistant for connecting model-powered tasks with tools and messaging.
Explore application →An agent workspace for conversations, tools and automation on infrastructure you control.
Explore application →Connect services and build repeatable workflows with a self-hosted automation platform.
Explore application →