OpenPunk/openpunk-ansible
1
0
Fork 0
mirror of https://github.com/CPunch/openpunk-ansible.git synced 2024-11-21 23:10:05 +00:00
Code Issues Packages Projects Releases Wiki Activity
Ansible project used for my production server for https://openpunk.com
9 Commits 2 Branches 3 Tags 126 KiB
Shell 100%
63715f1f8a
Go to file
CPunch 63715f1f8a Deadswitch: Use git patches instead of a raw markdown file
2022-08-01 23:57:43 -05:00
group_vars Inital commit 2022-05-30 10:46:36 -05:00
secrets@d13438c377 Added secrets submodule 2022-05-31 13:20:17 -05:00
tasks Deadswitch: Use git patches instead of a raw markdown file 2022-08-01 23:57:43 -05:00
templates Deadswitch: Use git patches instead of a raw markdown file 2022-08-01 23:57:43 -05:00
.gitignore Added secrets submodule 2022-05-31 13:20:17 -05:00
.gitmodules Added secrets submodule 2022-05-31 13:20:17 -05:00
README.md Misc. refactoring, less changes per rerun. Reruns should have no effect on a fully-setup vps now 2022-05-31 13:48:01 -05:00
run.yml Setup git 2022-05-30 23:39:32 -05:00

README.md

OpenPunk's Ansible playbook

This is my failsafe (and also my helpful migration tool) for restoring the OpenPunk server. This handles setting everything back up, including:

  • gitea
  • blog
  • tor mirror
  • nginx (for the above mentioned)
  • my shell theme (zsh + powerlevel10k)
  • deadswitch (& the ssh + git config to allow pushes)

This playbook assumes the target VPS is running the latest debian stable release.

Notes to my future self

The deadswitch has the deadtrigger setup every run, so you have a 14-day timer to add a one-liner to your crontab to keep that deadtrigger set.

Usage

ansible-playbook -i hosts --ask-vault-pass run.yml

NOTE: The 'secrets' directory has been omitted from this repo (so it's not going to run without the provided files)

Example hosts file

[hosts]
openpunk-vps ansible_host=104.238.138.76 ansible_user=root ansible_connection=ssh