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.
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.