ansible/playbooks/tasks/app/gulagbot.yml

# vim:ft=ansible:
- name: docker deploy gulagbot
  docker_container:
    name: gulagbot
    image: rehashedsalt/gulagbot:latest
    env:
      DISCORD_TOKEN: "{{ secret_gulagbot_discord_token }}"
      GULAG_DEBUG: "false"
      GULAG_HUMILIATION: "3"
      GULAG_SCORE_MIN: "-3"
      GULAG_SCORE_MAX: "15"
      PGHOST: eth0.vm-psql-1.home.mgmt.desu.ltd
      PGDATABASE: gulagbot-desultd
      PGUSER: gulagbot-desultd
      PGPASSWORD: "{{ secret_gulagbot_db_pass }}"
  tags: [ docker, gulagbot, stalin ]
Divide webservices into task files 2021-08-07 16:49:24 -05:00			`# vim:ft=ansible:`
			`- name: docker deploy gulagbot`
			`docker_container:`
			`name: gulagbot`
Revert "Lock gulagbot to 4.1.8" This reverts commit 4be2e313fd189e70ed427791dc8c7cf2a33fdac3. 2022-02-11 13:57:31 -06:00			`image: rehashedsalt/gulagbot:latest`
Divide webservices into task files 2021-08-07 16:49:24 -05:00			`env:`
			`DISCORD_TOKEN: "{{ secret_gulagbot_discord_token }}"`
Add some params for a new version of gulagbot 2021-11-22 14:12:13 -06:00			`GULAG_DEBUG: "false"`
Fix some unquoted number variables causing the gulagbot task to fail 2021-11-25 13:20:23 -06:00			`GULAG_HUMILIATION: "3"`
			`GULAG_SCORE_MIN: "-3"`
Change some Stalin settings 2022-02-04 23:04:36 -06:00			`GULAG_SCORE_MAX: "15"`
Have gulagbot connect to its DB via DNS Additionally, I configured a static IP for this machine This should eliminate the circumstance where gulagbot fails to connect to its DB after a reboot 2022-04-11 12:28:43 -05:00			`PGHOST: eth0.vm-psql-1.home.mgmt.desu.ltd`
Divide webservices into task files 2021-08-07 16:49:24 -05:00			`PGDATABASE: gulagbot-desultd`
			`PGUSER: gulagbot-desultd`
			`PGPASSWORD: "{{ secret_gulagbot_db_pass }}"`
			`tags: [ docker, gulagbot, stalin ]`