DutchEllie/pepebot
1
0
Fork 0
Code Issues2 Pull Requests Packages Projects Releases Wiki Activity
75 Commits 2 Branches 0 Tags 632 KiB
Go 98%
Dockerfile 2%
main
Go to file
DutchEllie 683b644227
Added deploy step
2022-05-19 13:36:14 +02:00
discord Add ben birthday 2022-05-19 08:03:09 +02:00
limiter fixed check 2021-05-31 14:32:04 +02:00
models First commit 2021-05-18 12:11:30 +02:00
pepeservice Moved to cdn.nicecock.eu again. Welcome back 2022-05-16 10:43:01 +02:00
.dockerignore Oops 2022-05-11 14:28:02 +02:00
.drone.yml Added deploy step 2022-05-19 13:36:14 +02:00
.gitignore Update .gitignore 2022-05-19 13:30:35 +02:00
docker-compose.yml Changed repo 2022-05-11 10:48:20 +02:00
Dockerfile Maybe this? 2022-05-11 15:01:54 +02:00
go.mod First commit 2021-05-18 12:11:30 +02:00
go.sum First commit 2021-05-18 12:11:30 +02:00
LICENSE Added LICENCE 2021-05-18 13:17:42 +02:00
README.md readme update 2021-05-18 13:14:18 +02:00

README.md

Substitute the environment variables in the docker-compose.yml file for your own

When changes have happened first use docker-compose build to update the pepe_server container's image. Then execute docker-compose up -d to start the containers.

When running for the first time, the database has to first start up properly, that can take some time. Also the database badwords (which is automatically created) won't have any tables or content in it yet. Similarly this happens when you have no volume yet to store your data. Create these yourself.