Compare commits
No commits in common. 'master' and 'new-app-ini' have entirely different histories.
master
...
new-app-in
31 changed files with 894 additions and 292 deletions
@ -1,56 +0,0 @@
@@ -1,56 +0,0 @@
|
||||
|
||||
captain hook config: |
||||
- need to have a template |
||||
- requires us to set a secret |
||||
- have been using "charles@charlesreid1.com" |
||||
- md5 |
||||
|
||||
|
||||
captain hook canary setup: |
||||
- install service script that checks for the canary file every 10 seconds |
||||
- it should run a script in the captain hook install dir |
||||
- if it finds the canary file, it should use a docker pod scripts dir script to update captain hook |
||||
|
||||
|
||||
pod-webhooks: |
||||
- need to install captain hook canary and captain hook pull host |
||||
- debian/dotfiles/bluebear_scripts/captain_hook_canary.sh |
||||
- debian/dotfiles/bluebear_scripts/captain_hook_pull_host.py |
||||
- debian/dotfiles/service/captain-hook-canary.service |
||||
|
||||
|
||||
|
||||
making domain swappable: |
||||
- submodules of pod-charlesreid1 would need to be reviewed in detail... |
||||
- need to template more files than we are currently templating |
||||
- the jinja copy from, copy to approach works well |
||||
- gitea |
||||
- mediawiki |
||||
- nginx |
||||
- letsencrypt |
||||
- the pod-charlesreid1 role defaults has a top_domain set to charlesreid1.com |
||||
- it says, "check for letsencrypt certs to this domain (top level domain of entire pod)" |
||||
- this does not match up with the nginx config files... which is how things are REALLY set |
||||
- top domain is used by gitea... |
||||
|
||||
|
||||
|
||||
subdomains/domains approach needs to be: |
||||
- specify a list of top level domains |
||||
- subdomains are fixed, but needs to be eg pages.${TOP_DOMAIN} |
||||
|
||||
|
||||
|
||||
pod-charlesreid1 /www setup |
||||
|
||||
https://git.charlesreid1.com/charlesreid1/charlesreid1.com |
||||
|
||||
/www/charlesreid1.com/ |
||||
charlesreid1.com-src/ <-- clone of charlesreid1.com repo, src branch |
||||
git/ <-- .git dir for charlesreid1.com repo gh-pages branch |
||||
git.data/ <-- .git dir for charlesreid1-data |
||||
htdocs/ <-- clone of charlesreid1.com repo gh-pages branch |
||||
data/ <-- clone of charlesreid1-data |
||||
|
||||
|
||||
|
||||
@ -1,81 +0,0 @@
@@ -1,81 +0,0 @@
|
||||
# Linode Quickstart |
||||
|
||||
This quickstart walks through the process |
||||
of setting up a Linode node |
||||
using these Ansible playbooks. |
||||
|
||||
|
||||
Table of Contents |
||||
================= |
||||
|
||||
* [Node setup](#node-setup) |
||||
* [Run provision and base playbooks](#run-provision-and-base-playbooks) |
||||
* [Run pod playbooks](#run-pod-playbooks) |
||||
|
||||
|
||||
## Node setup |
||||
|
||||
Start by logging in to your Linode account |
||||
and creating a new node. You should be able to |
||||
create or specify an SSH key. |
||||
|
||||
!!! warning |
||||
You must modify the path to the SSH private |
||||
key, specified in `linode.cfg` (the Linode |
||||
Ansible config file), to match the SSH key that |
||||
you added to the droplet at its creation. |
||||
|
||||
!!! warning |
||||
Once you create your droplet and it is connected |
||||
to the internet via a public IP, you must update |
||||
the file `linodehosts` (the Linode Ansible |
||||
inventory file) to point to the correct IP address |
||||
for the node. |
||||
|
||||
|
||||
## Run provision and base playbooks |
||||
|
||||
Once you have the correct SSH key in `linode.cfg` |
||||
and the correct droplet IP address in `linodehosts`, |
||||
you are ready to run the Ansible playbooks. |
||||
|
||||
Run the provision playbook to prepare the droplet for Ansible: |
||||
|
||||
```plain |
||||
ANSIBLE_CONFIG="linode.cfg" \ |
||||
ansible-playbook \ |
||||
provision.yml |
||||
``` |
||||
|
||||
Now you can run the base playbook. |
||||
|
||||
!!! warning |
||||
You must provide a `machine_name` parameter to |
||||
the base playbook. This variable is **_not_** |
||||
defined by default. Define it using the |
||||
`--extra-vars` flag. |
||||
|
||||
Specifying a machine name using the `--extra-vars` flag: |
||||
|
||||
```plain |
||||
ANSIBLE_CONFIG="linode.cfg" \ |
||||
ansible-playbook \ |
||||
--extra-vars "machine_name=redbeard" \ |
||||
base.yml |
||||
``` |
||||
|
||||
## Run pod playbooks |
||||
|
||||
Once you've run the base playbook, you can install the |
||||
docker pod with the corresponding playbook by specifying |
||||
`ANSIBLE_CONFIG` and pointing to the Linode config file. |
||||
|
||||
pod-charlesreid1: |
||||
|
||||
```plain |
||||
ANSIBLE_CONFIG="linode.cfg" \ |
||||
ansible-playbook \ |
||||
--extra-vars "machine_name=redbeard" \ |
||||
podcharlesreid1.yml |
||||
``` |
||||
|
||||
@ -0,0 +1,14 @@
@@ -0,0 +1,14 @@
|
||||
--- |
||||
# main playbook for webhooks docker pod |
||||
|
||||
|
||||
# SSL certs are all handled by the pod-charlesreid1 compute node |
||||
|
||||
- name: Install webhooks docker pod (pages.* and hooks.* and bots.* subdomains) |
||||
hosts: servers |
||||
become: yes |
||||
roles: |
||||
- role: pod-webhooks |
||||
tags: pod-webhooks |
||||
charlesreid1_server_name_default: "charlesreid1.red" |
||||
|
||||
@ -0,0 +1,38 @@
@@ -0,0 +1,38 @@
|
||||
Role Name |
||||
========= |
||||
|
||||
A brief description of the role goes here. |
||||
|
||||
Requirements |
||||
------------ |
||||
|
||||
Any pre-requisites that may not be covered by Ansible itself or the role should be mentioned here. For instance, if the role uses the EC2 module, it may be a good idea to mention in this section that the boto package is required. |
||||
|
||||
Role Variables |
||||
-------------- |
||||
|
||||
A description of the settable variables for this role should go here, including any variables that are in defaults/main.yml, vars/main.yml, and any variables that can/should be set via parameters to the role. Any variables that are read from other roles and/or the global scope (ie. hostvars, group vars, etc.) should be mentioned here as well. |
||||
|
||||
Dependencies |
||||
------------ |
||||
|
||||
A list of other roles hosted on Galaxy should go here, plus any details in regards to parameters that may need to be set for other roles, or variables that are used from other roles. |
||||
|
||||
Example Playbook |
||||
---------------- |
||||
|
||||
Including an example of how to use your role (for instance, with variables passed in as parameters) is always nice for users too: |
||||
|
||||
- hosts: servers |
||||
roles: |
||||
- { role: username.rolename, x: 42 } |
||||
|
||||
License |
||||
------- |
||||
|
||||
BSD |
||||
|
||||
Author Information |
||||
------------------ |
||||
|
||||
An optional section for the role authors to include contact information, or a website (HTML is not allowed). |
||||
@ -0,0 +1,2 @@
@@ -0,0 +1,2 @@
|
||||
--- |
||||
# defaults file for pod-bots |
||||
@ -0,0 +1,6 @@
@@ -0,0 +1,6 @@
|
||||
--- |
||||
# handlers file for pod-charlesreid1 |
||||
# |
||||
- name: restart pod-charlesreid1 |
||||
service: name=pod-charlesreid1 state=restarted |
||||
|
||||
@ -0,0 +1,60 @@
@@ -0,0 +1,60 @@
|
||||
galaxy_info: |
||||
author: your name |
||||
description: your description |
||||
company: your company (optional) |
||||
|
||||
# If the issue tracker for your role is not on github, uncomment the |
||||
# next line and provide a value |
||||
# issue_tracker_url: http://example.com/issue/tracker |
||||
|
||||
# Some suggested licenses: |
||||
# - BSD (default) |
||||
# - MIT |
||||
# - GPLv2 |
||||
# - GPLv3 |
||||
# - Apache |
||||
# - CC-BY |
||||
license: license (GPLv2, CC-BY, etc) |
||||
|
||||
min_ansible_version: 2.4 |
||||
|
||||
# If this a Container Enabled role, provide the minimum Ansible Container version. |
||||
# min_ansible_container_version: |
||||
|
||||
# Optionally specify the branch Galaxy will use when accessing the GitHub |
||||
# repo for this role. During role install, if no tags are available, |
||||
# Galaxy will use this branch. During import Galaxy will access files on |
||||
# this branch. If Travis integration is configured, only notifications for this |
||||
# branch will be accepted. Otherwise, in all cases, the repo's default branch |
||||
# (usually master) will be used. |
||||
#github_branch: |
||||
|
||||
# |
||||
# Provide a list of supported platforms, and for each platform a list of versions. |
||||
# If you don't wish to enumerate all versions for a particular platform, use 'all'. |
||||
# To view available platforms and versions (or releases), visit: |
||||
# https://galaxy.ansible.com/api/v1/platforms/ |
||||
# |
||||
# platforms: |
||||
# - name: Fedora |
||||
# versions: |
||||
# - all |
||||
# - 25 |
||||
# - name: SomePlatform |
||||
# versions: |
||||
# - all |
||||
# - 1.0 |
||||
# - 7 |
||||
# - 99.99 |
||||
|
||||
galaxy_tags: [] |
||||
# List tags for your role here, one per line. A tag is a keyword that describes |
||||
# and categorizes the role. Users find roles by searching for tags. Be sure to |
||||
# remove the '[]' above, if you add tags to this list. |
||||
# |
||||
# NOTE: A tag is limited to a single word comprised of alphanumeric characters. |
||||
# Maximum 20 tags per role. |
||||
|
||||
dependencies: [] |
||||
# List your role dependencies here, one per line. Be sure to remove the '[]' above, |
||||
# if you add dependencies to this list. |
||||
@ -0,0 +1,2 @@
@@ -0,0 +1,2 @@
|
||||
--- |
||||
# tasks file for pod-bots |
||||
@ -0,0 +1,5 @@
@@ -0,0 +1,5 @@
|
||||
--- |
||||
- hosts: localhost |
||||
remote_user: root |
||||
roles: |
||||
- pod-bots |
||||
@ -0,0 +1,2 @@
@@ -0,0 +1,2 @@
|
||||
--- |
||||
# vars file for pod-bots |
||||
@ -0,0 +1,38 @@
@@ -0,0 +1,38 @@
|
||||
Role Name |
||||
========= |
||||
|
||||
A brief description of the role goes here. |
||||
|
||||
Requirements |
||||
------------ |
||||
|
||||
Any pre-requisites that may not be covered by Ansible itself or the role should be mentioned here. For instance, if the role uses the EC2 module, it may be a good idea to mention in this section that the boto package is required. |
||||
|
||||
Role Variables |
||||
-------------- |
||||
|
||||
A description of the settable variables for this role should go here, including any variables that are in defaults/main.yml, vars/main.yml, and any variables that can/should be set via parameters to the role. Any variables that are read from other roles and/or the global scope (ie. hostvars, group vars, etc.) should be mentioned here as well. |
||||
|
||||
Dependencies |
||||
------------ |
||||
|
||||
A list of other roles hosted on Galaxy should go here, plus any details in regards to parameters that may need to be set for other roles, or variables that are used from other roles. |
||||
|
||||
Example Playbook |
||||
---------------- |
||||
|
||||
Including an example of how to use your role (for instance, with variables passed in as parameters) is always nice for users too: |
||||
|
||||
- hosts: servers |
||||
roles: |
||||
- { role: username.rolename, x: 42 } |
||||
|
||||
License |
||||
------- |
||||
|
||||
BSD |
||||
|
||||
Author Information |
||||
------------------ |
||||
|
||||
An optional section for the role authors to include contact information, or a website (HTML is not allowed). |
||||
@ -0,0 +1,20 @@
@@ -0,0 +1,20 @@
|
||||
--- |
||||
# defaults file for pod-webhooks |
||||
|
||||
username: "{{ nonroot_user }}" |
||||
|
||||
# where pod-webhooks is installed |
||||
webhooks_install_dir: "/home/{{ username }}/pod-webhooks" |
||||
|
||||
# shared secret |
||||
# # (must be entered every time you create a webhook) |
||||
captain_hook_secret: "{{ charlesreid1_captain_hook_secret }}" |
||||
|
||||
# ---------------- |
||||
# subpages nginx |
||||
# configuration variables |
||||
server_name_default: "{{ charlesreid1_server_name_default }}" |
||||
|
||||
# end nginx configuration variables |
||||
# ---------------- |
||||
# |
||||
@ -0,0 +1,6 @@
@@ -0,0 +1,6 @@
|
||||
--- |
||||
# handlers file for pod-charlesreid1 |
||||
# |
||||
- name: restart pod-charlesreid1 |
||||
service: name=pod-charlesreid1 state=restarted |
||||
|
||||
@ -0,0 +1,524 @@
@@ -0,0 +1,524 @@
|
||||
--- |
||||
########################### |
||||
# Set up webhooks pod |
||||
# |
||||
# git.charlesreid1.com/docker/pod-webhooks |
||||
# git.charlesreid1.com/docker/d-nginx-subdomains |
||||
# |
||||
# Tasks: |
||||
# ------ |
||||
# |
||||
# clone pod contents |
||||
# |
||||
# /www setup |
||||
# pages subdomain clone |
||||
# hooks subdomain clone |
||||
# bots subdomain clone |
||||
# docker and docker compose checks |
||||
# pages subdomain prep |
||||
# captain hook setup |
||||
# captain hook canary setup |
||||
# |
||||
# construct the pod (docker-compose build) |
||||
# install service |
||||
# (port mapping in Dockerfile) |
||||
# (letsencrypt cert check) |
||||
# enable service |
||||
# |
||||
# NOTE: This is almost identical to |
||||
# pod-charlesreid1, except for a few |
||||
# different sections. We could have |
||||
# made everything shared, but f--k it |
||||
# this has dragged on long enough. |
||||
# |
||||
########################### |
||||
|
||||
|
||||
|
||||
# ##################################### |
||||
# CLONE POD-WEBHOOKS |
||||
|
||||
|
||||
# Check if we already cloned it |
||||
- name: Check if pod-webhooks repo is cloned |
||||
stat: |
||||
path: "{{ webhooks_install_dir }}" |
||||
register: pod_webhooks_clone_check |
||||
tags: |
||||
- pod-webhooks |
||||
|
||||
|
||||
# Clone it |
||||
- name: Clone pod-webhooks |
||||
become: yes |
||||
become_user: "{{ username }}" |
||||
git: |
||||
repo: 'https://github.com/charlesreid1-docker/pod-webhooks.git' |
||||
dest: "{{ webhooks_install_dir }}" |
||||
recursive: yes |
||||
when: |
||||
- "not pod_webhooks_clone_check.stat.exists" |
||||
tags: |
||||
- pod-webhooks |
||||
|
||||
|
||||
# Pull it |
||||
- name: Pull pod-webhooks |
||||
become: yes |
||||
become_user: "{{ username }}" |
||||
command: "git pull" |
||||
args: |
||||
chdir: "{{ webhooks_install_dir }}" |
||||
when: |
||||
- "pod_webhooks_clone_check.stat.exists" |
||||
tags: |
||||
- pod-webhooks |
||||
|
||||
|
||||
# Pull submodules |
||||
- name: Pull pod-webhooks submodules |
||||
become: yes |
||||
become_user: "{{ username }}" |
||||
command: "git submodule update --remote" |
||||
args: |
||||
chdir: "{{ webhooks_install_dir }}" |
||||
when: |
||||
- "pod_webhooks_clone_check.stat.exists" |
||||
tags: |
||||
- pod-webhooks |
||||
|
||||
|
||||
|
||||
# ##################################### |
||||
# BUILD DOCKER-COMPOSE FILE FROM TEMPLATE |
||||
# |
||||
- name: Fetch the docker-compose template from the remote machine |
||||
run_once: true |
||||
fetch: |
||||
src: "{{ webhooks_install_dir }}/docker-compose.yml.j2" |
||||
dest: "/tmp/pod-webhooks-docker-compose.yml.j2" |
||||
flat: yes |
||||
fail_on_missing: yes |
||||
tags: |
||||
- pod-webhooks |
||||
- pod-webhooks-docker |
||||
|
||||
|
||||
- name: Install the docker-compose file |
||||
become: yes |
||||
become_user: "{{ username }}" |
||||
template: |
||||
src: "/tmp/pod-webhooks-docker-compose.yml.j2" |
||||
dest: "{{ webhooks_install_dir }}/docker-compose.yml" |
||||
mode: 0640 |
||||
force: yes |
||||
tags: |
||||
- pod-webhooks |
||||
- pod-webhooks-docker |
||||
|
||||
|
||||
|
||||
# ##################################### |
||||
# SET UP /WWW DIRECTORY |
||||
# |
||||
# Create /www directory |
||||
# for subdomains content |
||||
- name: Create the /www directory |
||||
become: yes |
||||
file: |
||||
path: "/www" |
||||
state: directory |
||||
recurse: yes |
||||
owner: "{{ username }}" |
||||
group: "{{ username }}" |
||||
tags: |
||||
- pod-webhooks |
||||
- pod-webhooks-content |
||||
|
||||
# Template scripts to populate /www |
||||
# with subdomain pages is done in the |
||||
# rules below... |
||||
|
||||
|
||||
|
||||
# ##################################### |
||||
# SUBDOMAIN PAGES SETUP (ALL) |
||||
# |
||||
# Initializes the /www folder structure for |
||||
# /www/pages.* |
||||
# /www/hooks.* |
||||
# /www/bots.* |
||||
# |
||||
# This is done with template python scripts |
||||
# |
||||
# /www/<subdomain>.charlesreid1.com/ |
||||
# <subdomain>.charlesreid1.com-src/ |
||||
# git/ |
||||
# htdocs/ |
||||
|
||||
|
||||
- name: "Fetch the initial subdomain clone commands script template" |
||||
fetch: |
||||
src: "{{ webhooks_install_dir }}/scripts/subdomains_init_setup.py.j2" |
||||
dest: "/tmp/subdomains_init_setup.py.j2" |
||||
flat: yes |
||||
fail_on_missing: yes |
||||
tags: |
||||
- pod-webhooks |
||||
- pod-webhooks-content |
||||
|
||||
|
||||
- name: "Install the initial subdomain clone commands script" |
||||
become: yes |
||||
become_user: "{{ username }}" |
||||
template: |
||||
src: "/tmp/subdomains_init_setup.py.j2" |
||||
dest: "{{ webhooks_install_dir }}/scripts/subdomains_init_setup.py" |
||||
mode: 0755 |
||||
force: yes |
||||
tags: |
||||
- pod-webhooks |
||||
- pod-webhooks-content |
||||
|
||||
|
||||
- name: Run initial clone commands to set up bots/pages/hooks subdomains at /www/ |
||||
command: "python {{ webhooks_install_dir }}/scripts/subdomains_init_setup.py" |
||||
tags: |
||||
- pod-webhooks |
||||
- pod-webhooks-content |
||||
|
||||
|
||||
|
||||
# ##################################### |
||||
# PAGES SETUP |
||||
# |
||||
# Initializes the contents of /www/pages.*/* |
||||
|
||||
- name: Fetch the initial pages script |
||||
fetch: |
||||
src: "{{ webhooks_install_dir }}/scripts/pages_init_setup.py.j2" |
||||
dest: "/tmp/pages_init_setup.py.j2" |
||||
flat: yes |
||||
fail_on_missing: yes |
||||
tags: |
||||
- pod-webhooks |
||||
- pod-webhooks-content |
||||
|
||||
|
||||
- name: Install the pages init setup script |
||||
become: yes |
||||
become_user: "{{ username }}" |
||||
template: |
||||
src: "/tmp/pages_init_setup.py.j2" |
||||
dest: "{{ webhooks_install_dir }}/scripts/pages_init_setup.py" |
||||
mode: 0755 |
||||
force: yes |
||||
tags: |
||||
- pod-webhooks |
||||
- pod-webhooks-content |
||||
|
||||
|
||||
- name: Run initial clone commands to set up pages at /www/pages.charlesreid1.com |
||||
command: "python {{ webhooks_install_dir }}/scripts/pages_init_setup.py" |
||||
tags: |
||||
- pod-webhooks |
||||
- pod-webhooks-content |
||||
|
||||
|
||||
|
||||
# ##################################### |
||||
# DOCKER/DOCKER COMPOSE |
||||
|
||||
# The docker role, in the base playbook, |
||||
# will install docker-compose, but we want |
||||
# to double check that the executable exists |
||||
|
||||
- name: Check that docker compose executable is available |
||||
stat: |
||||
path: "/usr/local/bin/docker-compose" |
||||
register: webhooks_register_docker_compose |
||||
tags: |
||||
- pod-webhooks |
||||
- pod-webhooks-docker |
||||
|
||||
|
||||
# Also make sure the docker daemon is running |
||||
|
||||
- name: Enable docker service |
||||
become: yes |
||||
service: |
||||
name: docker |
||||
enabled: yes |
||||
state: restarted |
||||
tags: |
||||
- pod-webhooks |
||||
- pod-webhooks-docker |
||||
- pod-webhooks-services |
||||
|
||||
|
||||
|
||||
# ##################################### |
||||
# NGIX CONFIG PREP |
||||
# |
||||
# prepare the config files for the |
||||
# subdomains nginx server: |
||||
# - copy templates from remote machine |
||||
# - clean conf.d directory |
||||
# - copy rendered templates to remote machine |
||||
|
||||
- name: Clean d-nginx-subdomains conf.d directory |
||||
become: yes |
||||
become_user: "{{ username }}" |
||||
command: "python {{ webhooks_install_dir }}/d-nginx-subdomains/scripts/clean_config.py" |
||||
tags: |
||||
- pod-webhooks |
||||
|
||||
|
||||
# Install the d-nginx-subdomains configuration templates |
||||
# |
||||
- name: Fetch d-nginx-subdomains configuration templates from remote machine |
||||
run_once: true |
||||
fetch: |
||||
src: "{{ webhooks_install_dir }}/d-nginx-subdomains/conf.d_templates/http.subdomains.conf.j2" |
||||
dest: "/tmp/http.subdomains.conf.j2" |
||||
flat: yes |
||||
fail_on_missing: yes |
||||
tags: |
||||
- pod-webhooks |
||||
|
||||
|
||||
- name: Install the d-nginx-subdomains configuration templates |
||||
become: yes |
||||
become_user: "{{ username }}" |
||||
template: |
||||
src: "/tmp/http.subdomains.conf.j2" |
||||
dest: "{{ webhooks_install_dir }}/d-nginx-subdomains/conf.d/http.subdomains.conf" |
||||
force: yes |
||||
tags: |
||||
- pod-webhooks |
||||
|
||||
|
||||
|
||||
# ##################################### |
||||
# CAPTAIN HOOK SETUP |
||||
|
||||
- name: Fetch the captain hook config file template |
||||
fetch: |
||||
src: "{{ webhooks_install_dir }}/b-captain-hook/config.json.j2" |
||||
dest: "/tmp/captain_hook_config.json.j2" |
||||
flat: yes |
||||
fail_on_missing: yes |
||||
tags: |
||||
- captain-hook |
||||
|
||||
|
||||
- name: Install the captain hook config file |
||||
become: yes |
||||
become_user: "{{ username }}" |
||||
template: |
||||
src: "/tmp/captain_hook_config.json.j2" |
||||
dest: "{{ webhooks_install_dir }}/b-captain-hook/config.json" |
||||
mode: 0755 |
||||
force: yes |
||||
tags: |
||||
- captain-hook |
||||
|
||||
|
||||
# ##################################### |
||||
# CAPTAIN HOOK CANARY SCRIPT SETUP |
||||
# |
||||
# Start with the canary script first. |
||||
# |
||||
# The whole pod has to be built and the |
||||
# pod startup service installed |
||||
# before the canary service can be |
||||
# installed. |
||||
|
||||
# Script 1 - canary script itself |
||||
# Use the template provided to make it |
||||
# |
||||
- name: Fetch the captain hook canary script template from the remote machine |
||||
run_once: true |
||||
fetch: |
||||
src: "{{ webhooks_install_dir }}/scripts/captain_hook_canary.sh.j2" |
||||
dest: "/tmp/captain_hook_canary.sh.j2" |
||||
flat: yes |
||||
fail_on_missing: yes |
||||
tags: |
||||
- captain-hook |
||||
|
||||
# Install the captain hook canary script |
||||
# |
||||
- name: Install the captain hook canary script |
||||
become: yes |
||||
become_user: "{{ username }}" |
||||
template: |
||||
src: "/tmp/captain_hook_canary.sh.j2" |
||||
dest: "{{ webhooks_install_dir }}/scripts/captain_hook_canary.sh" |
||||
mode: 0755 |
||||
force: yes |
||||
tags: |
||||
- captain-hook |
||||
|
||||
|
||||
# Script 2 - pull host script |
||||
# Do it all again for the pull host script |
||||
# Use the template provided to make it |
||||
# |
||||
- name: Fetch the captain hook pull host script template from the remote machine |
||||
run_once: true |
||||
fetch: |
||||
src: "{{ webhooks_install_dir }}/scripts/captain_hook_pull_host.py.j2" |
||||
dest: "/tmp/captain_hook_pull_host.py.j2" |
||||
flat: yes |
||||
fail_on_missing: yes |
||||
tags: |
||||
- captain-hook |
||||
|
||||
# Install the captain hook pull host script |
||||
- name: Install the captain hook pull host script |
||||
become: yes |
||||
become_user: "{{ username }}" |
||||
template: |
||||
src: "/tmp/captain_hook_pull_host.py.j2" |
||||
dest: "{{ webhooks_install_dir }}/scripts/captain_hook_pull_host.py" |
||||
mode: 0755 |
||||
force: yes |
||||
tags: |
||||
- captain-hook |
||||
|
||||
|
||||
|
||||
# ##################################### |
||||
# CONSTRUCT THE POD |
||||
# |
||||
# This task is very time-consuming. |
||||
|
||||
- name: Build pod-webhooks from scratch |
||||
become: yes |
||||
become_user: "{{ username }}" |
||||
command: "/usr/local/bin/docker-compose build --no-cache" |
||||
args: |
||||
chdir: "{{ webhooks_install_dir }}" |
||||
when: |
||||
- "webhooks_register_docker_compose.stat.exists" |
||||
|
||||
|
||||
|
||||
# ##################################### |
||||
# INSTALL STARTUP SERVICE |
||||
# |
||||
# Check if the webhooks docker pod service |
||||
# is installed. If not, install it. |
||||
|
||||
### # Just kidding - don't bother. |
||||
### # Always reinstall the startup service. |
||||
### # |
||||
### - name: Check if pod-webhooks service is installed |
||||
### stat: |
||||
### path: "/etc/systemd/system/pod-webhooks.service" |
||||
### register: pod_webhooks_service_check |
||||
### tags: |
||||
### - pod-webhooks-services |
||||
|
||||
|
||||
# Fetch the pod-webhooks service template |
||||
# |
||||
- name: Fetch the pod-webhooks template from remote host machine |
||||
run_once: true |
||||
fetch: |
||||
src: "{{ webhooks_install_dir }}/scripts/pod-webhooks.service.j2" |
||||
dest: "/tmp/pod-webhooks.service.j2" |
||||
flat: yes |
||||
fail_on_missing: yes |
||||
tags: |
||||
- pod-webhooks-services |
||||
|
||||
|
||||
# Apply the template and install it for goodness sake |
||||
# |
||||
- name: Install pod-webhooks service |
||||
become: yes |
||||
template: |
||||
src: "/tmp/pod-webhooks.service.j2" |
||||
dest: "/etc/systemd/system/pod-webhooks.service" |
||||
mode: 0774 |
||||
tags: |
||||
- pod-webhooks-services |
||||
|
||||
|
||||
# Now enable the pod-webhooks service. |
||||
# Don't worry about SSL cert checks, not our problem. |
||||
|
||||
- name: Enable pod-webhooks service |
||||
become: yes |
||||
service: |
||||
name: pod-webhooks |
||||
enabled: yes |
||||
state: restarted |
||||
when: |
||||
- "webhooks_register_docker_compose.stat.executable" |
||||
tags: |
||||
- pod-webhooks-services |
||||
|
||||
|
||||
|
||||
# ##################################### |
||||
# CAPTAIN HOOK CANARY SERVICE SETUP |
||||
|
||||
### # Begin by checking to see if installed |
||||
### # Just kidding - always reinstall the canary service from the repo template |
||||
### # |
||||
### - name: Check if the captain hook canary service is installed |
||||
### stat: |
||||
### path: "/etc/systemd/system/captain-hook-canary.service" |
||||
### register: canary_service_check |
||||
### tags: |
||||
### - pod-webhooks-services |
||||
### - captain-hook |
||||
|
||||
# Fetch the captain hook canary startup service template onto local computer |
||||
# # |
||||
- name: Fetch the captain hook canary service template file from the remote machine |
||||
run_once: true |
||||
fetch: |
||||
src: "{{ webhooks_install_dir }}/scripts/captain-hook-canary.service.j2" |
||||
dest: "/tmp/captain-hook-canary.service.j2" |
||||
flat: yes |
||||
fail_on_missing: yes |
||||
tags: |
||||
- pod-webhooks-services |
||||
- captain-hook |
||||
|
||||
|
||||
# Apply the captain hook canary startup service template |
||||
# |
||||
- name: Install the captain hook canary startup service |
||||
become: yes |
||||
template: |
||||
src: "/tmp/captain-hook-canary.service.j2" |
||||
dest: "/etc/systemd/system/captain-hook-canary.service" |
||||
mode: 0774 |
||||
force: yes |
||||
tags: |
||||
- pod-webhooks-services |
||||
- captain-hook |
||||
|
||||
|
||||
# Now enable the captain hook canary startup service. |
||||
# |
||||
- name: Enable the captain hook canary startup service |
||||
become: yes |
||||
service: |
||||
name: captain-hook-canary |
||||
enabled: yes |
||||
state: restarted |
||||
tags: |
||||
- pod-webhooks-services |
||||
- captain-hook |
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -0,0 +1,27 @@
@@ -0,0 +1,27 @@
|
||||
# Service script for starting up the |
||||
# captain hook canary service. |
||||
# |
||||
# The main purpose of this service is to |
||||
# allow the captain hook webhook container |
||||
# to send a signal to the host machine |
||||
# (by touching a file in a shared directory). |
||||
# |
||||
# Each repository has its own webhooks, |
||||
# and each repository can create their own |
||||
# canary files and have custom actions to |
||||
# deal with them. |
||||
|
||||
[Unit] |
||||
Description=captain hook canary script |
||||
Requires=pod-webhooks.service |
||||
After=pod-webhooks.service |
||||
|
||||
[Service] |
||||
Restart=always |
||||
ExecStart=/home/charles/blackbeard_scripts/captain_hook_canary.sh |
||||
ExecStop=/usr/bin/pgrep -f captain_hook_canary | /usr/bin/xargs /bin/kill |
||||
|
||||
[Install] |
||||
WantedBy=default.target |
||||
|
||||
|
||||
@ -0,0 +1,16 @@
@@ -0,0 +1,16 @@
|
||||
# Service script for starting up the webhooks docker pod |
||||
# # (hooks subdomain, pages subdomain) |
||||
|
||||
[Unit] |
||||
Description=webhooks and subdomains docker pod |
||||
Requires=docker.service |
||||
After=docker.service |
||||
|
||||
[Service] |
||||
Restart=always |
||||
ExecStart=/usr/local/bin/docker-compose -f /home/charles/codes/docker/pod-webhooks/docker-compose.yml up |
||||
ExecStop=/usr/local/bin/docker-compose -f /home/charles/codes/docker/pod-webhooks/docker-compose.yml down |
||||
|
||||
[Install] |
||||
WantedBy=default.target |
||||
|
||||
Loading…
Reference in new issue