-
Notifications
You must be signed in to change notification settings - Fork 434
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
Improve self-hosted getting started docs #1805
Comments
This is a great example of taking docs written by our engineering team and making them more accessible. That means far more growth :) Definitely worth doing this sort of thing, especially for all the critical hurdles to getting PostHog up and running. |
@tiina303 @fuziontech - would it be possible to have a setup where we could access the IP address over HTTPS? This means you can avoid the domain setup. |
Technically it's possible, but it's more effort than with a domain name and ends up being subpar, so almost nobody does that. |
At the moment I'm stuck on step 3: create/update |
I forgot to link to helm there, I linked to it just a bit below in the manual section. Basically it's https://helm.sh/docs/intro/install/#through-package-managers so So to narrow it down there are these parts in step 3:
Where are you at? |
Thanks, @tiina303. Got this working. For the web, you can use PostHog via As discussed, if folks want a self-hosted version running over HTTPS they'll need to understand helm charts 👍 |
I've walked through the self-hosted docs where we encourage installation on Digital Ocean. Getting PostHog up and running on DO is definitely easy. However, I'd like to either clarify what additional steps are required to use this deployment on a hobby app or make changes to improve the steps to make that easier.
My process so far:
The text was updated successfully, but these errors were encountered: