Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Posthog play #58

Merged
merged 2 commits into from
Dec 22, 2023
Merged

Posthog play #58

merged 2 commits into from
Dec 22, 2023

Conversation

cooldracula
Copy link
Contributor

adds a posthog play to show how we deployed our posthog service. This is a v. simple playbook/role/inventory as the majority of the work is handled by posthog's own deployment script.

I tested this by deploying posthog.ansible.fun using the playbook (as part of the new-do-droplet play) and then running it again on the same server. If you run the play multiple times, it will simply run the deploy script, which creates and restarts the docker containers. This should be safe for running against existing services. However, the suggested way to maintain the posthog deployment is to use their upgrade script, which is fiercely interactive and does not play well with ansible. Which is to say: I think this play is best suited for starting up new instances of posthog, but we should use their scripts outside of ansible for maintaining existing services.

@cooldracula cooldracula merged commit b6f2259 into main Dec 22, 2023
1 check passed
@cooldracula cooldracula deleted the posthog-play branch December 22, 2023 08:18
@cooldracula cooldracula mentioned this pull request Dec 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant