Docker Compose Testcloud

Frequently I need a clean throwaway deployment of Nextcloud to quickly reproduce bugs or have an isolated back end for client development and automated testing. This is the next level.

Not long ago I wrote about Nextcloud Docker test containers. Through frequent use I moved on to something more practical.

As I learned earlier, in 99 % of cases the official Nextcloud Docker image is sufficient for my use cases. I do not need the test images out of the community. They often are augmented with features for Nextcloud server (app) development. They lack documentation or just have way too much of it due to their complexity. In the end, I just want something that works to get something done quickly. But sometimes I realized that the automatically configured SQLite database of the Nextcloud image is cumbersome to inspect.

Finally I had a reason to get into Docker Compose and what it is about. My suspicion was confirmed and I was delighted how easy it is to piece together. I now can use a Nextcloud and MariaDB container in combination to retain all the benefits of the former while extending the possibilities with the latter. Most importantly: I can use tools like Sequel Ace to conveniently and quickly browse the database by exposing the MariaDB port.

You can see my GitHub repository for this linked below for further information.