https://github.com/fefas/stack-ready

Docker images ready for being used in a stack
https://github.com/fefas/stack-ready

Last synced: about 1 month ago
JSON representation

Docker images ready for being used in a stack

• Host: GitHub
• URL: https://github.com/fefas/stack-ready
• Owner: fefas
• License: mit
• Created: 2020-05-04T19:21:02.000Z (over 4 years ago)
• Default Branch: main
• Last Pushed: 2021-02-08T07:11:48.000Z (almost 4 years ago)
• Last Synced: 2024-11-07T01:43:13.658Z (3 months ago)
• Language: Shell
• Size: 7.81 KB
• Stars: 2
• Watchers: 3
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# Stack Ready

## Purpose

These images were built to help those who are always redoing the same work when

setting up new applications to be running in a container cluster.

If you need something optmizated, this repo might not be what you are looking

for. It will be mostly probably better to build images by your own.

On the otherhand, if you are just setting up a new project using the most common

packages, this is your place! Just pick up the image that better fits for your

use case.

# Tags organization

The images follow the following format:

`fefas/stack-ready/:-+[-[-]...]`

Examples:

- `fefas/stack-ready/php:8.0.2-alpine3.11-composer2.0.9-mysql`

- `fefas/stack-ready/php:8.0.2-alpine3.11-composer2.0.9-postgresql`

- `fefas/stack-ready/php:8.0.2-alpine3.11-composer2.0.9-postgresql-rabbitmq-redis`

## Features

This repository contains docker images ready for being used in a stack. But what

does it means? Every time containerized applications are set up, common problems

such as the followings have to be addressed:

- Not root user

- Workdir

- Controlling of startup order

- Dependecy manager of our choosen language

- Common packages (of course, the minimum according to your need)

- ...

> Even though this is not intended to be part of [official docker

> images](https://docs.docker.com/docker-hub/official_images/), [the best

> practices](https://docs.docker.com/develop/develop-images/dockerfile_best-practices/)

> were followed.