README.md

D-Zone

https://github.com/d-zone-org/d-zone/tree/heroku in a container!

Creates a Container which runs the heroku branch of D-Zone-Org's D-Zone, with lsiobase/alpine as the base image, as seen on https://pixelatomy.com/dzone/?s=default.

The lasiobase/alpine image is a custom base image built with Alpine linux and S6 overlay. Using this image allows us to use the same user/group ids in the container as on the host, making file transfers much easier

---

D-Zone is a graphical simulation meant to abstractly represent the activity in your Discord server.

This is not meant for any actual monitoring or diagnostics, only an experiment in the abstraction of chatroom data represented via autonomous characters in a scene.

Usage

  d-zone:
    container_name: d-zone
    image: griefed/d-zone
    restart: unless-stopped
    volumes:
      - ./path/to/config/files:/config
    environment:
      - TOKEN=<YOUR_BOT_TOKEN_HERE>
      - TZ=Europe/Berlin
      - PUID=1000  #User ID
      - PGID=1000  #Group ID
    ports:
      - 3000:3000

Configuration	Explanation
restart:	Restart policy Either: "no", always, on-failure, unless-stopped
/config volume	Local path to config files
TZ	Timezone
PUID	for UserID
PGID	for GroupID
ports	The port where D-Zone will be available at. Change left number.

User / Group Identifiers

When using volumes, permissions issues can arise between the host OS and the container. Linuxserver.io avoids this issue by allowing you to specify the user PUID and group PGID.

Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.

In this instance PUID=1000 and PGID=1000, to find yours use id user as below:

  $ id username
    uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup)

Deploy on Rasbperry Pi

Using the noproxy Dockerfile, this container can be built and run on a Raspberry Pi, too! I've tested it on a Raspberry Pi 3B+.

1. Clone the repository: git clone https://github.com/Griefed/docker-D-Zone.git ./d-zone
2. Replace Dockerfile with Dockerfile.noproxy: rm Dockerfile && mv Dockerfile.noproxy Dockerfile
3. Prepare docker-compose.yml file as seen below
4. docker-compose up -d --build d-zone
5. Visit IP.ADDRESS.OF.HOST:3000
6. ???
7. Profit!

docker-compose.yml