https://github.com/keivanipchihagh/server-loader

pre-configured stacks and scripts to deploy my favorite production-ready services in a nutshell 🐳
https://github.com/keivanipchihagh/server-loader

alertmanager docker grafana nginx-proxy-manager pgadmin portainer postgresql prometheus registry vault

Last synced: 4 months ago
JSON representation

pre-configured stacks and scripts to deploy my favorite production-ready services in a nutshell 🐳

• Host: GitHub
• URL: https://github.com/keivanipchihagh/server-loader
• Owner: keivanipchihagh
• License: apache-2.0
• Created: 2022-12-08T18:20:45.000Z (over 2 years ago)
• Default Branch: main
• Last Pushed: 2024-03-26T15:00:04.000Z (about 1 year ago)
• Last Synced: 2025-01-11T21:22:33.664Z (5 months ago)
• Topics: alertmanager, docker, grafana, nginx-proxy-manager, pgadmin, portainer, postgresql, prometheus, registry, vault
• Language: Shell
• Homepage: https://www.keivanipchihagh.com
• Size: 178 KB
• Stars: 1
• Watchers: 1
• Forks: 0
• Open Issues: 2
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# server-loader

pre-configured stacks and scripts to deploy my favorite production-ready services in a nutshell 🐳

> **Note**

> Use `.env.template` files as templates to create `.env` files that will be used in the stacks. All sensitive data have been emptied, so fill them yourself you must (:

## Stacks

Stacks are used to deploy multiple containers that usually operate together and are dependent. Most of these stacks are pre-configured for painless deployment:

- **nginx-proxy-manager:**

  - Containers:

    - nginx-proxy-manager

- **monitoring**:

  - Containers:

    - grafana

    - prometheus

    - alertmanager

    - node-exporter

    - cadvisor

- **portainer**:

  - Containers:

    - portainer

    - portainer-agent

- **postgres**:

  - Containers:

    - postgres

    - pgadmin

    - postgres-exporter

- **registry**:

  - Containers:

    - registry

    - registry-ui

## Network Architecture

To ensure flexibility and security for all services operating on the server, three Docker networks are defined:

- **nginx**

  - Type: `Internal`

  - Info: Containers that are **only** be accessible from the reverse-proxy (unreachable by their IP:PORT!) which are comminucated with over TLS.

- **public**

  - Type: `External`

  - Info: Containers that are publicly accessible by IP:PORT over HTTP (unencrypted channel).

- **private**

  - Type: `Internal`

  - Info: Containers that are not accessible from the outside world. This network is **hidden** and used for internal traffic of sensitive data.