Nextcloud Cloud Storage for Greensburg Ghost Society
A self-hosted Nextcloud environment I provide and administer for Greensburg Ghost Society, giving members private storage and file access using infrastructure hosted in my Proxmox environment.
Project Goal
Greensburg Ghost Society needed a practical location for members to store, organize, and access investigation files without relying entirely on third-party consumer cloud storage.
I provide and administer a self-hosted Nextcloud environment for the organization, including the application platform, storage capacity, supporting services, maintenance, and infrastructure integration.
Public documentation intentionally excludes internal addresses, account information, credentials, private storage paths, and administrative configuration.
Environment Summary
Nextcloud Platform
Nextcloud 33.0.3 running in a dedicated Debian 12 LXC container hosted on Proxmox VE.
Web and Application Stack
Apache serves the Nextcloud application with PHP 8.3, while MariaDB provides the database backend.
Redis Integration
Redis is actively configured for Nextcloud memory caching and file locking to improve application behavior and reduce database locking overhead.
Storage
The Nextcloud environment has a 15 TB filesystem hosted on NAS-backed NFS storage integrated with Proxmox.
Service Status
Nextcloud is installed and operational with maintenance mode disabled and no database upgrade currently required.
Architecture
Technologies Used
What I Built
- Deployed and administer a dedicated Debian LXC container for the Nextcloud service.
- Installed and maintain Nextcloud with Apache, PHP, and MariaDB.
- Configured Redis as both the Nextcloud memory cache and file-locking backend.
- Provisioned a 15 TB Nextcloud filesystem on NAS-backed NFS storage integrated with Proxmox.
- Provide the hosted service and storage capacity for Greensburg Ghost Society members.
- Maintain the supporting Linux services and application stack required for the environment.
- Validate application state using Nextcloud command-line administration tools and standard Linux service checks.
Security and Privacy Considerations
- Internal addressing, credentials, user information, private storage paths, and administrative configuration are not published.
- The Nextcloud application runs in its own dedicated workload rather than being mixed directly with unrelated services.
- Redis uses a local socket for Nextcloud caching and file-locking operations.
- Database, application, and storage responsibilities are separated logically within the service design.
- Public documentation focuses on architecture and operational responsibilities without exposing member data or private infrastructure details.
Operational Value
Unlike a temporary lab exercise, this environment provides an ongoing service used by an actual organization. That requires attention to application availability, storage capacity, upgrades, supporting services, and member access.
The project combines Linux administration, application hosting, database services, caching, storage integration, and operational ownership in one environment.
It also demonstrates how self-hosted infrastructure can be used to provide useful services to a community organization without exposing the underlying management infrastructure publicly.
What This Demonstrates
This project demonstrates Linux service administration, Nextcloud deployment and maintenance, Apache and PHP application hosting, MariaDB administration, Redis caching and file locking, Proxmox workload management, NAS-backed NFS storage integration, capacity planning, and ongoing ownership of a service used by real users.
Project Status
Active and operational. Nextcloud 33.0.3 is currently running with Apache, MariaDB, and Redis active. Maintenance mode is disabled, no database upgrade is pending, and the service continues to provide hosted storage for Greensburg Ghost Society.