ethibox / awesome-stacks

Deploy 110+ open-source web apps with one Docker command

Awesome Stacks

Deploy 110+ open-source web apps with one Docker command.

✨ Features

• Traefik compatibility
• Portainer compatibility
• No need to manage configuration files
• Distributed storage compatibility (GlusterFS, Ceph, NFS) with the env VOLUME_PATH=/mnt/storage_mountpoint/

🚀 Get started

# 1. Deploy traefik
docker swarm init
docker network create --driver=overlay traefik-net
docker stack deploy -c stacks/traefik.yml traefik

# 2. Check your HTTP and HTTPS ports
curl https://ipv4.am.i.mullvad.net/port/80
curl https://ipv4.am.i.mullvad.net/port/443

# 3. Deploy a stack
DOMAIN=<mydomain.com> docker stack deploy -c <stack.yml> <name>

# Example
DOMAIN=ghost.example.com docker stack deploy -c stacks/ghost.yml ghost

🎁 Support me

I'd love to work on this project, but my time on this earth is limited, support my work to give me more time!

Please support me with a one-time or a monthly donation and help me continue my activities.

📜 License

This project is licensed under the GNU GPL v3.0 - see the LICENSE.txt file for details

Free Software, Hell Yeah!

awesome-stacks's Issues

Template file not loading in Portainer

I've checked the JSON and I just dont get why https://raw.githubusercontent.com/ethibox/awesome-stacks/master/templates.json won't load as Template directory in Portainer 2.11.0 ? Other similar repos on github work fine.

Revolt Chat Stack ?

Hello, I've managed to build a stack based on the self hosted revolt chat docker (https://github.com/revoltchat/self-hosted)
It's working... but as I'm already using portainer and traefik the ports are not working.

Any idea on how to fix that ? And maybe it can help others too :)
I mean I already have a: portainer + swarmpit + traefik + gitea + drone + taiga (thanks a loooooooot)
When I try to subscribe it's says Network error.

Thanks

version: '3.8'

x-default: &defaults
environment:

• MONGODB=mongodb://database
• REDIS_URI=redis://redis/
• REVOLT_APP_URL=http://revolt.PRIVATE
• REVOLT_PUBLIC_URL=http://revolt.PRIVATE
• VITE_API_URL=http://revolt.PRIVATE
• REVOLT_EXTERNAL_WS_URL=ws://revolt.PRIVATE
• AUTUMN_PUBLIC_URL=http://revolt.PRIVATE
• JANUARY_PUBLIC_URL=http://revolt.PRIVATE
• REVOLT_UNSAFE_NO_CAPTCHA=1
• REVOLT_UNSAFE_NO_EMAIL=1
• REVOLT_INVITE_ONLY=0
• REVOLT_MAX_GROUP_SIZE=150
• REVOLT_VAPID_PRIVATE_KEY=LS0tLS1CRUdJTiBFQyBQUklWQVRFIEtFWS0tLS0tCk1IY0NBUUVFSUJSUWpyTWxLRnBiVWhsUHpUbERvcEliYk1yeVNrNXpKYzVYVzIxSjJDS3hvQW9HQ0NxR1NNNDkKQXdFSG9VUURRZ0FFWnkrQkg2TGJQZ2hEa3pEempXOG0rUXVPM3pCajRXT1phdkR6ZU00c0pqbmFwd1psTFE0WAp1ZDh2TzVodU94QWhMQlU3WWRldVovWHlBdFpWZmNyQi9BPT0KLS0tLS1FTkQgRUMgUFJJVkFURSBLRVktLS0tLQo=
• REVOLT_VAPID_PUBLIC_KEY=BGcvgR-i2z4IQ5Mw841vJvkLjt8wY-FjmWrw83jOLCY52qcGZS0OF7nfLzuYbjsQISwVO2HXrmf18gLWVX3Kwfw=
• AUTUMN_S3_REGION=minio
• AUTUMN_S3_ENDPOINT=http://minio:9000
• MINIO_ROOT_USER=minioautumn
• MINIO_ROOT_PASSWORD=minioautumn
• AWS_ACCESS_KEY_ID=minioautumn
• AWS_SECRET_ACCESS_KEY=minioautumn

networks:
traefik-public:
external: true

services:

MongoDB database

database:
<<: *defaults
image: mongo
volumes:
- revoltdb:/data/db
networks:
- traefik-public

Redis server

redis:
<<: *defaults
image: eqalpha/keydb
networks:
- traefik-public

API server (delta)

api:
<<: *defaults
image: ghcr.io/revoltchat/server:20220715-1
depends_on:
- database
- redis
ports:
- "8000:8000"
networks:
- traefik-public

Events service (quark)

events:
<<: *defaults
image: ghcr.io/revoltchat/bonfire:20220715-1
depends_on:
- database
- redis
ports:
- "9000:9000"
networks:
- traefik-public

Web App (revite)

web:
<<: *defaults
image: ghcr.io/revoltchat/client:master
ports:
- "5000:5000"
networks:
- traefik-public
deploy:
placement:
constraints:
- node.role == manager
labels:
- traefik.enable=true
- traefik.docker.network=traefik-public
- traefik.constraint-label=traefik-public
- traefik.http.routers.revolt-http.rule=Host(revolt.PRIVATE)
- traefik.http.routers.revolt-http.entrypoints=http
- traefik.http.routers.revolt-http.middlewares=https-redirect
- traefik.http.routers.revolt-https.rule=Host(revolt.PRIVATE)
- traefik.http.routers.revolt-https.entrypoints=https
- traefik.http.routers.revolt-https.tls=true
- traefik.http.routers.revolt-https.tls.certresolver=le
- traefik.http.services.revolt.loadbalancer.server.port=5000

S3-compatible storage server

minio:
<<: *defaults
image: minio/minio
command: server /data
volumes:
- revoltminio:/data
ports:
- "10000:9000"
networks:
- traefik-public

Create buckets for minio.

createbuckets:
<<: *defaults
image: minio/mc
depends_on:
- minio
entrypoint: >
/bin/sh -c "
while ! curl -s --output /dev/null --connect-timeout 1 http://minio:9000; do echo 'Waiting minio...' && sleep 0.1; done;
/usr/bin/mc alias set minio http://minio:9000 $MINIO_ROOT_USER $MINIO_ROOT_PASSWORD;
/usr/bin/mc mb minio/attachments;
/usr/bin/mc mb minio/avatars;
/usr/bin/mc mb minio/backgrounds;
/usr/bin/mc mb minio/icons;
/usr/bin/mc mb minio/banners;
/usr/bin/mc mb minio/emojis;
exit 0;
"

File server (autumn)

autumn:
<<: *defaults
image: ghcr.io/revoltchat/autumn:1.1.5
depends_on:
- database
- createbuckets
environment:
- AUTUMN_MONGO_URI=mongodb://database
ports:
- "3000:3000"
networks:
- traefik-public

Metadata and image proxy (january)

january:
<<: *defaults
image: ghcr.io/revoltchat/january:master
ports:
- "7000:7000"
networks:
- traefik-public

volumes:
revoltdb:
revoltminio:

Trying to get in touch regarding a security issue

Hi there,

I couldn't find a SECURITY.md in your repository and am not sure how to best contact you privately to disclose a security issue.

Can you add a SECURITY.md file with an e-mail to your repository, so that our system can send you the vulnerability details? GitHub suggests that a security policy is the best way to make sure security issues are responsibly disclosed.

Once you've done that, you should receive an e-mail within the next hour with more info.

Thanks! (cc @huntr-helper)

Add support for traefik v2 and web access

Hi, I would be great to see support for Traefik 2 and have the ability to easily enable web access to Traefik's monitoring tools.

Beers on me ;)

Taiga default creds ?

Hello and thanks a lot for your work!
I've installed taiga but I can't manage to login.
I think I'm missing smthg, what are the fault creds ?

Inserting custom configuration into application specific nginx.conf

Since the stacks are ephemeral by design all application configurations need to be declared in the app_stack.yml file, so I need some instructions on how to modify the app_stack.yml files to insert custom configuration in nginx,conf.

Documentation?

Any chance we can get a full documentation\guide? A.I. can probably make it a lot easier. Thanks bro! :)

Certificate Issue. Warning: Potential Security Risk Ahead

Hi,

Trying to update my Mattermost instance.

I had no SSL issue using prior version of Mattermost/Traefik, i.e. stack version 3.7

In version 3.8, does the new configuration include accessing the service using HTTPS by default, because in the end, we often want to access the service from the Internet and not necessary locally.

Since update, after following the “Get started”, I've got the following message from Firefox and everything is broken and can no longer access Mattermost on my VPS:

Warning: Potential Security Risk Ahead
[domain] uses an invalid security certificate.
The certificate is not trusted because it is self-signed.
Error code: MOZILLA_PKIX_ERROR_SELF_SIGNED_CERT

I did not have any certificate issue before when using an older version of the stacks. I used “traefik-ssl.yml”, version 3.7.

Obviously, the content between “traefik-ssl.yml”, version 3.7 and “traefik.yml” version 3.8 dramatically changed. In version 3.8 of “traefik.yml” I see the use of letsencrypt. So, don't understand why Firefox still showing “self-signed” certificate.

Also, when forcing the visit, I now have the message:

404 page not found

This is what happened when going from stack version 3.7 to stack version 3.8. I reverted back to stack version 3.7, and I can now access Mattermost.

Even though after issuing the command:

DOMAIN=[MY_DOMAIN] docker stack deploy -c mattermost.yml mattermost

I also put the SCHEME=https argument like I used in the previous version, but not working either.

---

Thanks for your help.

BASH access to application specific NGINX containers fails

The first issue is that the application specific NGINX containers fails to connect to the bash session of the contianers, both from the host servers console and Portainer. I have tried it with 2 other WP app instances that I have installed and its the same, nginx throws "Connection error" for Console access.