Add Docker-based Nextcloud setup with advanced features for home labs

[willsnake]

Changes Made

Added the following files to set up a Docker-based Nextcloud instance with enhanced functionality:

1. .env.example: Added an example environment file with configuration variables for Nextcloud, MySQL, and timezone settings.

2. docker-compose.yml: Created a Docker Compose file that defines services for:

   • MariaDB database
   • Redis cache
   • Nextcloud application
     The file includes network configurations, volume mappings, and environment variable references.

3. Dockerfile: Added a custom Dockerfile based on the latest Nextcloud image. This Dockerfile:

   • Modifies user and group IDs to solve volume mounting issues
   • Installs additional packages including ffmpeg, ghostscript, and smbclient
   • Configures PHP extensions like bz2 and imap
   • Sets up supervisord for process management

4. supervisord.conf: Added a configuration file for supervisord to manage Apache2 and cron processes within the container.

These changes provide a comprehensive setup for running Nextcloud with face recognition and memories features apps enabled, and resolve issues related to volume mounting in LXC containers.

Purpose

The purpose of these changes is to provide a robust and feature-rich Docker setup for Nextcloud, specifically tailored for home lab environments. These modifications aim to:

1. Enable advanced features: By including ffmpeg and other necessary packages, this setup allows users to utilize Nextcloud's face recognition and memories features out of the box.

2. Improve performance: The inclusion of Redis as a caching layer enhances the overall performance of the Nextcloud instance.

3. Enhance security: The use of environment variables for sensitive information (as demonstrated in the .env.example file) promotes better security practices.

4. Solve compatibility issues: The modifications in the Dockerfile, particularly the user and group ID changes, address common problems when mounting volumes in LXC containers.

5. Provide process management: The addition of supervisord ensures proper management of Apache and cron processes within the container.

6. Offer a complete solution: By providing all necessary configuration files, this setup allows users to quickly deploy a fully functional Nextcloud instance with advanced features in their home lab.

Context

This pull request is part of the ongoing effort to enhance the JimsGarage repository with more comprehensive and advanced home lab setups. Specifically:

1. Nextcloud popularity: Nextcloud is a widely used self-hosted cloud solution in the home lab community. This setup addresses common pain points and feature requests from users.

2. Docker-based deployment: The use of Docker simplifies deployment and management, making it accessible to a wider range of users with varying levels of expertise.

3. Advanced features focus: There's growing interest in Nextcloud's AI-powered features like face recognition and memories. This setup makes these features more accessible.

4. LXC container compatibility: Many home lab setups use LXC containers. The modifications in this PR address common issues faced when running Nextcloud in such environments.

5. Security considerations: The .env approach for configuration aligns with best practices for managing sensitive information in Docker environments.

6. Performance optimization: The inclusion of Redis as a caching layer is a common performance optimization for Nextcloud instances.

Additional Notes

1. Environment Variables:

   • Users should create their own .env file based on the provided .env.example, ensuring to change all passwords and sensitive information.

2. Volume Mounting:

   • The Dockerfile includes modifications to user and group IDs (set to 10000) to address volume mounting issues in LXC containers. Users with different ID requirements may need to adjust these values.

3. Resource Requirements:

   • This setup, especially with face recognition and memories features enabled, may require more resources than a basic Nextcloud installation. Users should ensure their system meets the increased CPU, RAM, and storage requirements.

4. Customization:

   • The Dockerfile can be further customized to include or exclude specific packages based on individual needs.

5. Updates:

   • While this setup uses the latest Nextcloud image as a base, users should regularly update their installations to ensure they have the latest security patches and features.

6. Backup:

   • As with any data-critical application, regular backups are strongly recommended. This setup does not include a backup solution out of the box.

7. SSL/TLS:

   • This configuration does not include SSL/TLS setup. For production use, it's highly recommended to set up HTTPS, either through a reverse proxy or by configuring the Nextcloud container directly.

8. Community Feedback:

   • As this is a new addition to the JimsGarage repository, community feedback and contributions for further improvements are welcome.

[JamesTurland]

Wow, thanks for all of this, very comprehensive. I will test it out ASAP.