Deploying to Microsoft Azure

Why Azure

Microsoft Azure is one of the most well-established Cloud Providers. It offers a comprehensive dashboard with simple configuration, as well as an extensive Free Trial.

Deploying to Azure

To deploy on Azure, our suggested method is deploying with Docker, which we'll explain in detail on this page. If you would rather not use Docker, you can consider deploying from source, as well as other providers with one-click installs, like Heroku or AWS.

Docker Install: Virtual Machine Setup

The first thing you'll need is a Microsoft Azure account. Once you have that up and running, you're good to go!

Step-By-Step

Access your Dashboard
Click 'Virtual Machine' if it is available on the main screen. Otherwise, click 'Create a Resource' > 'Compute' > 'Virtual Machine'
On the 'Virtual Machine' page, click 'Add' on the top right if you were not automatically taken to the creation page
Set up your desired configuration. We'll be using the 'Ubuntu Server 18.04 LTS' image for this tutorial.

You may also want to enable ports 22, 80, and 443, for SSH, HTTP Traffic, and HTTPS Traffic respectively. It is recommended to set security preferences and allowed IPs for these ports. For this tutorial, you will also need the 'username' you create at this stage, so take note of that.

Finally, for the server specifications, we recommend a config with about the following specs for a medium volume instance:
- 4GB of RAM
- 2 CPUs
- 50GB of storage
However, this will vary based on the volume you're expecting. If you're expecting a low volume, a lighter instance may do just fine. Conversely, if you are expecting high volume, you should probably scale up from the specs above.
Click 'Review + create' once you're done with the configuration steps
Once your instance is live, that means you're ready to move on to the next tutorial.

Docker Installation

SSH into your Virtual Machine by using the IP provided as a resource on your Virtual Machine Console. Use that IP instead of <YOUR_IP>, and run the following command on a terminal:
```
ssh <username>@<YOUR_IP>
```
If you downloaded a new key during the creation of the Virtual Machine, you may need to run:
```
ssh -i path/to/your/key.pem <username>@<YOUR_IP>
```
After accessing the instance, install Docker Engine
Then install Docker Compose
Setup Docker to run without root priviledges (optional but strongly recommended)
You should already have git installed. In that case, skip this step. Otherwise, install git:
```
sudo apt-get update && sudo apt-get install git
```

To clone the PostHog repository and enter the new directory, run:

git clone https://github.com/posthog/posthog.git && cd posthog

You'll then need to generate a SECRET_KEY that is unique to your instance.

⚠️ Note: Do not use our placeholder key! Read more about the importance of this key here.

First, run: openssl rand -hex 32. This will generate a new key for you. You'll need this in the next step.

Then, open the docker-compose.yml file with the command: nano docker-compose.yml

Lastly, substitute "<randomly generated secret key>" for the key you got from the key generation command.

This means the SECRET_KEY: "<randomly generated secret key>" line will end up looking something like this (with your key, of course):
```
SECRET_KEY: "cd8a182315defa70d995452d9258908ef502da512f52c20eeaa7951d0bb96e75"
```
Then, to run PostHog, do:
```
docker-compose up -d
```
You're good to go! PostHog should be accessible on the domain you set up or the IP of your instance.

Important Points

⚠️ Never, Ever, Run PostHog Without TLS/SSL

PostHog needs to run on HTTPS because:

a) It will fail
b) It is a grave security concern and potentially illegal

Check Your Firewall/Security Group if You Cannot Connect to a Port

If you are unable to connect to a certain port, this might be due to the firewall or security group settings for your VM.

Firewall Issues

Generally, this is a matter of running:

sudo ufw allow <PORT> && sudo ufw reload

To check that the changes were applied, run:

sudo ufw status

You can read this tutorial for more information.

Security Group Issues

Here's a good Azure Tutorial about this.

Upgrading Docker on Azure

See this PostHog tutorial about upgrading your PostHog version with Docker.