The objective of this repository is having a CaaS Containers as a Service to provide a "ready to use" container with the basic enviroment features to deploy a RabbitMQ broker service under a lightweight Linux Alpine image for development stage requirements.
The container configuration is as Host Network on eth0 as Bridge network, thus it can be accessed through localhost:${PORT} by browsers but to connect with it or this with other services ${HOSTNAME}:${PORT} will be required.
https://hub.docker.com/layers/library/rabbitmq/3.13-management-alpine/
Docker Official Image packaging for RabbitMQ
- Built on the lightweight and secure Alpine 3.19 2024 release Linux distribution
- Multi-platform, supporting AMD4, ARMv6, ARMv7, ARM64
- Very small Docker image size (+/-40MB)
- The logs of all the services are redirected to the output of the Docker container (visible with
docker logs -f <container name>) - Follows the KISS principle (Keep It Simple, Stupid) to make it easy to understand and adjust the image to your needs
- Services independency to connect the application to other database allocation
This repository is structured so it can be included into other projects inside a parent main /docker directory
.
│
├── docker
│ ├── rabbitmq (this repository)
│ │ ├── docker
│ │ │ ├── config
│ │ │ ├── .env
│ │ │ └── docker-compose.yml
│ │ │
│ │ └── Makefile
│ │
│ └── nginx-php (example)
│
├── symfony
│ └── (application...)
│
├── .env
├── .env.example
└── Makefile
Makefiles are often used to automate the process of building and compiling software on Unix-based systems as Linux and macOS.
On Windows - I recommend to use Makefile:
https://stackoverflow.com/questions/2532234/how-to-run-a-makefile-in-windows
Makefile recipies
$ make help
usage: make [target]
targets:
Makefile help shows this Makefile help message
Makefile hostname shows local machine hostname ip
Makefile fix-permission sets project directory permission
Makefile port-check shows this project port availability on local machine
Makefile env checks if docker .env file exists
Makefile env-set sets docker .env file
Makefile ssh enters the container shell
Makefile build builds the container from Dockerfile
Makefile up attaches to containers for a service and also starts any linked services
Makefile start starts the container running
Makefile stop stops the container running - data will not be destroyed
Makefile restart execute this Makefile "stop" and "start" recipes
Makefile clear removes container from Docker running containers
Makefile destroy delete container image from Docker - Docker prune commands still needed to be applied manually
Makefile dev set a development enviroment