3) Choose the $5/mo plan
If you want you can choose a more powerful server, but the $5/mo should be enough for at least 20-30k monthly visitors.
You can also change the plan any time after creating the server.
4) Choose your preferred server location
Normally this should be close to you, or close to where the majority of the tracked users are. A central location such as Amsterdam could also be good.
5) Check the "Monitoring" checkbox
This will enable performance graphs in your DigitalOcean dashboard, so you can see the CPU/Memory/Disk/Network usage of the server.
6) Check the "User data" checkbox and add the userTrack installation config.
This is where the magic happens and what automatically installs userTrack on the server.
Add that code to the User data input, so it should look something like this:
7) Select the preferred authentication method to access the server and the server name. SSH is recommended, but if you are not familiar with SSH you can select one-time password.
You can optionally enable backups. You can also do this later, after the server is created.
To recap, those options should be selected:
Marketplace -> LAMP on 18.04 (or newer) image.
User data textarea must be filled with the #cloud-config code as explained above.
Everything is done, click Create Droplet.
The server will now be created, it usually takes 4-5 minutes before it can be accessed.
While it's being setup we can add our own domain to point to that IP.
2. Point your own domain name to the userTrack dashboard server
To do this, you have to go add some DNS records to your domain from your domain name registrar.
Add two A recordsfrom your domain (or subdomain name) to the IP of your server.
A analytics.example.com 123.123.456.9
A www.analytics.example.com 123.456.78.9
3. Add free HTTPS certificate for that domain.
The easiest way to access the server is through the web console. Here you can use the password that was set when creating the droplet.
Note that when you type passwords in a console, nothing is displayed but the password is actually typed. When you paste the password from your email you won't see anything, so just paste with it CTRL+V and submit with ENTER.
You should now be able to access userTrack from the domain name. It can also be accessed from the server IP.
Now, back to the HTTPS certificate.
While you are in the console, run this command to generate a free HTTPS certificate using certbot:
(replace example.com and www.example.com with the own domains, the same as in step 2)
There are 3-4 questions you have to respond to in the console after running that command in order for the certificate to be issued.
You now have a userTrack instance, running on your own server, on your own domain with a HTTPS certificate.
You might be able to also use this as a guide to add userTrack on a server from different hosting provider, but the user data (cloud-init) script might not work, as it has some DigitalOcean specific paths.
If you had any issues following this guide, or want to suggest to make a similar guide for a different provider (assuming they support premade LAMP images and cloud-init), you can send me an e-mail at support [at] usertrack.net.