The January 2024 Community post is essentially a pointer to an external BigBearCasaOS tutorial rather than a full installation procedure preserved inside the forum. It introduced BigBear as a convenient way to install Nextcloud on CasaOS and described Nextcloud as a self-hosted alternative to services such as Dropbox, Microsoft 365, or Google Drive when combined with collaboration tools.
For a long-lived page, the useful approach is to keep that historical context while checking the current Big Bear store rather than reproducing a two-year-old package definition. Big Bear remains independently maintained and its CasaOS repository still includes multiple Nextcloud options.
The Source Is a 2024 CasaOS Tutorial, Not a Current ZimaOS Recipe
The thread belongs to the CasaOS category and dates from January 2024. Its linked tutorial was designed around the CasaOS custom app-store workflow available at that time.
Do not treat the old screenshots, ports, or image tags as proof of current ZimaOS behavior.
Big Bear Still Maintains Nextcloud Packages
The current Big Bear CasaOS repository continues to list Nextcloud packages, including the main Big Bear Nextcloud build and a LinuxServer-based option. The repository also says custom app stores require CasaOS 0.4.4 or later.
Review the current Big Bear CasaOS app definitions before installing from an older tutorial.
Do Not Pin a 2024 Nextcloud Version from the Original Tutorial
Big Bear's maintained store updates application definitions over time. A Nextcloud image from early 2024 can be several major releases behind a current package and may have different PHP, database, or app compatibility requirements.
Use the version in the current store and read its release notes before upgrading an existing production instance.
Persistent Nextcloud Data Needs a Storage Plan Before Installation
A Nextcloud container is replaceable; the files and database are not. Decide where user files, configuration, and database state will live before letting the server accumulate important data.
On a small system disk, thumbnails, previews, app data, and database growth can become a capacity problem even when the user's main files are on a larger disk.
Database Choice Matters More as the Server Grows
For a permanent multi-user Nextcloud deployment, use the database topology supported by the package you selected and avoid casually swapping database engines after the instance is established.
If the Big Bear package uses a multi-container stack, preserve the database volume and service networking when moving or backing up the app.
Big Bear's Current Store Includes Nextcloud Variants with SMB Support
The maintained repository currently includes a Nextcloud package based on a Big Bear image with SMB client support. That can matter when Nextcloud needs to attach other network storage as external storage.
This should not be confused with putting the primary Nextcloud database on an SMB share.
Back Up Both Files and Database State
A folder copy of the Nextcloud data directory alone is not a complete application backup. Database state, configuration, and installed-app information are also required for a reliable recovery.
Before an upgrade or migration, record the current image version, volume mappings, database service, and reverse-proxy configuration.
Remote Access Needs HTTPS and Authentication
Nextcloud is designed for remote use, but publishing it directly to the Internet without a secure reverse proxy, TLS, updates, and strong authentication is not a good default.
For a personal deployment, private access through a VPN/overlay network can reduce exposure when public sharing is not required.
Nextcloud on CasaOS FAQ
Does the original forum post contain the full installation steps?
No. It primarily links to an external BigBearCasaOS tutorial.
Is Big Bear Nextcloud still maintained?
The current Big Bear CasaOS repository continues to list actively updated Nextcloud packages.
Should I reuse the exact 2024 image version?
No. Use the current package definition and preserve your persistent data before upgrades.
