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

Improve self-hosted getting started docs #1805

Closed
5 tasks done
leggetter opened this issue Aug 18, 2021 · 6 comments · Fixed by #1826
Closed
5 tasks done

Improve self-hosted getting started docs #1805

leggetter opened this issue Aug 18, 2021 · 6 comments · Fixed by #1826
Assignees
Labels
docs Improvements or additions to product documentation, "Docs"

Comments

@leggetter
Copy link
Contributor

leggetter commented Aug 18, 2021

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:

  • Signup for a DO account and get $100 credit 🥳
  • Click the 1-click install app. Initially, this doesn't seem to work and instead, you are taken to your main account screen. If you then create a k8 cluster and follow the process (click to install) you are prompted to either use an existing cluster or create a new cluster. I'll need to create a new account to verify this. If there is a problem we should add a callout/note.
  • Find external IP address and navigate to it
  • Setup an A name so that you're no longer using an IP address
  • Setup an SSL certificate - I'm stuck here so would appreciate some help
@leggetter leggetter added the docs Improvements or additions to product documentation, "Docs" label Aug 18, 2021
@jamesefhawkins
Copy link
Contributor

jamesefhawkins commented Aug 18, 2021

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.

@leggetter
Copy link
Contributor Author

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

@Twixes
Copy link
Contributor

Twixes commented Aug 18, 2021

Technically it's possible, but it's more effort than with a domain name and ends up being subpar, so almost nobody does that.

@leggetter
Copy link
Contributor Author

At the moment I'm stuck on step 3: create/update values.yml. The next step also looks daunting as there's mention of helm that hasn't been required up until this point and we provide no pointers on where to get started.

@tiina303
Copy link
Contributor

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 brew install helm on a mac.

So to narrow it down there are these parts in step 3:

  • create a values.yaml file
  • get kubectl & point it to your DO cluster
  • install helm
  • run the 3 commands for upgrading

Where are you at?

@leggetter
Copy link
Contributor Author

Thanks, @tiina303. Got this working. For the web, you can use PostHog via http://{ip_address} on your development server running localhost which I believe provides a suitable validation point.

As discussed, if folks want a self-hosted version running over HTTPS they'll need to understand helm charts 👍

@leggetter leggetter self-assigned this Aug 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Improvements or additions to product documentation, "Docs"
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants