Fraîche Flow

Linux · Infrastructure · Networking · Virtualisation

docs/Nextcloud stack with MariaDB and Redis
58 lines2.07 KB

Nextcloud stack with MariaDB and Redis

MILOUD NECILI

Fraîche Flow · IT Systems Integration

Project objective

Separate a web application into application, database and cache containers and operate them as a stack.

My implementation

  • Deployed Nextcloud as nextcloudcontainer on host port 8888.
  • Ran MariaDB as datenbankcontainer and Redis as rediscontainer.
  • Treated the Compose structure, port mapping and persistent storage as one coherent deployment.
  • Checked HTTP reachability and container status and added the services to Kuma.

Technical context

Application nextcloudcontainer · 8888:80
Database datenbankcontainer · mariadb:lts
Cache rediscontainer · redis:alpine
Separation In addition to the native Nextcloud stack; no migration claimed

Result

All three containers were shown as Up. The HTTP test against 127.0.0.1:8888 returned 200. In the final monitoring view, Nextcloud Docker, Docker MariaDB and Redis Container were online.

Verification and operational evidence

docker ps --filter name=nextcloudcontainer
docker ps --filter name=datenbankcontainer --filter name=rediscontainer
curl -I http://192.168.10.13:8888

Nextcloud Docker stack with MariaDB, Redis, HTTP status 200 and a shared network

Practical troubleshooting

The database and Redis had no published host ports. Additional Docker network connectivity was used for Kuma so that the containers were reachable internally.

Security and technical context

Do not include database passwords in public Compose examples. Manual network-connect changes are not automatically stored in Compose and must be added declaratively before recreating containers.

Transferable skills

Multi-container architecture, internal service communication, persistence and Compose operations.

Project status

Completed according to confirmation from the project lead.