StatsPro

StatsPro is a open-source, easily deployable, and privacy friendly alternative to Google Analytics.

About The Project • Why Choose StatsPro • Architecture • Running Locally • Running In The Cloud • License

About The Project

StatsPro is a open-source, easily deployable, and privacy friendly web analytics software. StatsPro has many of the features that you would expect from other analytics software without invading your users privacy and without selling data to 3rd parties for advertisements.

StatsPro does not use cookies and is fully compliant with GDPR, PECR, CCPA.

You can run StatsPro on your own servers (by following the instructions below) or have us host it for you. We only host on European servers owned by European companies to ensure your analytics is compliant with the law.

Why Choose StatsPro

Learn more about why you should choose StatsPro over other analytics providers on our website here.

Architecture

Broadcaster

The Broadcaster is the javascript file which is installed on your website to collect pageview data when users visit your site. It is designed to be as lightweight and un-intrusive as possible.

Backend

The Backend of the application is written in Laravel, a modern framework that makes it easy to write complex services.

One of the most important parts of the backend is The Collector. The Collector records the data from Broadcasters into a Postgres database.

Frontend

The frontend of the application is written in React, allowing a clean separation between the backend and frontend application.

Running Locally

The steps below outline how you can run StatsPro on your own machine. If you don't want to deal with running StatsPro on your own, we can handle it for you.

These steps have been tested on Mac OS X 12.5.

Prerequisites

• Docker
• Understanding of command line utilities
• Understanding of modern frontend development with React
• Basic understanding of Laravel.

Steps

1. Run this command to start containers to run nginx, the StatsPro app, and Postgres

   make rebuild-local

2. Manually connect to the database with username postgres and password postgres create a stats_pro database.

3. Now you'll need to SSH into the app container to install all Javascript and PHP dependencies and run our Vite server. This will compile and serve up our frontend resources.

   docker-compose exec app /bin/bash
   composer install
   npm install
   npm run dev

4. Now you should be able to visit localhost to see StatsPro running.

5. Next, we'll run migrations on the database to get all the tables setup. While SSHed into the container, run

   php artisan migrate

6. (Optional)

   1. Setting up stripe signing secret: The docker compose file already specifies a stripe-cli container which will start up and listen for webhooks and forward them onto the nginx container. In order for this to work correctly, you must add the signing secret which is output from starting the containers into your .env file under STRIPE_WEBHOOK_SECRET
   2. Create an .env file at the root of the project and add your STRIPE_SECRET to it so that docker can read it

      STRIPE_SECRET=<stripe secret here>
      

Running In The Cloud

StatsPro is hosted on Stackhero, a European company which has servers in Europe. This guide assumes you will be running on Stackhero. StatsPro should run the same on other docker cloud providers but there may be some work to get it all configured. If you don't want to deal with running StatsPro on your own, we can handle it for you.

StatsPro is deployed to Stackhero using Github Actions.

1. Create a new Docker service within Stackhero. Keep the host, service ID, and certificates password handy as we'll be using them in a later step.

2. Create a new Postgres service within Stackhero. Keep the host, username, and password handy as well be using them in a later step.

3. Setup Github Actions environment variables

   • STACKHERO_DOCKER_HOST - set this to the value provided by Stackhero
   • STACKHERO_DOCKER_SERVICE_ID - set this to the value provided by Stackhero
   • STACKHERO_DOCKER_CERTIFICATES_PASSWORD - set this to the value provided by Stackhero
   • DOT_ENV - this will populate the .env to be used by the application, it should contain

   APP_ENV=staging
   APP_KEY=base64:<your app key here>
   APP_DEBUG=false
   APP_URL=<your STACKHERO_DOCKER_HOST>
   VITE_APP_URL=<your STACKHERO_DOCKER_HOST>
   SANCTUM_STATEFUL_DOMAINS="${APP_HOST}"
   
   DB_HOST=<your postgres database host>
   DB_PORT=5432
   DB_DATABASE=stats_pro
   DB_USERNAME=<your postgres username>
   DB_PASSWORD=<your postgres password>
   
   GOOGLE_CLIENT_ID=<optional, google client id for Signin With Google>
   GOOGLE_CLIENT_SECRET=<optional, google client secret for Signin With Google>
   
   MAIL_HOST=<optional, the SMTP host to be used to send emails>
   MAIL_PORT=<optional>
   MAIL_USERNAME=<optional>
   MAIL_PASSWORD=<optional>
   MAIL_FROM_ADDRESS=<optional>
   

   Replace the values in triangle brackets with the appropriate values.

   <your app key here> should be a random base-64 encoded string of length 32

4. Now go to Github Actions and run the Build Staging action.

5. One the action has finished running, you should be able to see StatsPro running by visiting the docker host URL.

License

StatsPro is open source under the GNU Affero General Public License Version 3 (AGPLv3).

License