Simple, open source, lightweight (< 1 KB) and privacy-friendly web analytics alternative to Google Analytics.
The highlights of this release are:
ENABLE_EMAIL_VERIFICATION=true
option.To update your installation, make sure your _docker-compose.yml_l file is referencing plausible/analytics
with the following tag: v1.4.0
. Then run the following commands:
$ docker-compose down
$ docker-compose pull plausible
$ docker-compose up -d
This will run your database migrations and boot up the new version of the app. Following changes have been made since v1.3:
metrics
for the /api/v1/stats/timeseries
endpoint plausible/analytics#952DATABASE_SOCKET_DIR
& DATABASE_NAME
were added.CLICKHOUSE_FLUSH_INTERVAL_MS
and CLICKHOUSE_MAX_BUFFER_SIZE
configuration parameters plausible/analytics#1073path
component of BASE_URL to allow subfolder installatonsENABLE_EMAIL_VERIFICATION=true
if you want to keep the old behaviourThe highlights of this release are:
ENABLE_EMAIL_VERIFICATION=true
option.This is a release candidate for testing. To update your installation, make sure your docker-compose.yml file is referencing plausible/analytics
with the following tag: v1.4.0-rc.0
. Then run the following commands:
$ docker-compose down
$ docker-compose pull plausible
$ docker-compose up -d
This will run your database migrations and boot up the new version of the app. Following changes have been made since v1.3:
metrics
for the /api/v1/stats/timeseries
endpoint plausible/analytics#952DATABASE_SOCKET_DIR
& DATABASE_NAME
were added.CLICKHOUSE_FLUSH_INTERVAL_MS
and CLICKHOUSE_MAX_BUFFER_SIZE
configuration parameters plausible/analytics#1073path
component of BASE_URL to allow subfolder installatonsENABLE_EMAIL_VERIFICATION=true
if you want to keep the old behaviourThe highlights of this release are:
maxmindinc/geoipupdate
container is no longer necessary for geolocationThis release bumps the minimum Clickhouse version is 20.8.7.15
so make sure you upgrade your Clickhouse installation if needed.
To update your Plausible installation, make sure your docker-compose.yml file is referencing plausible/analytics
with one of the following tags: latest
, v1
, v1.3
, v1.3.0
. Then run the following commands:
$ docker-compose down
$ docker-compose pull plausible
$ docker-compose up -d
This will run your database migrations and boot up the new version of the app. Following changes have been made since v1.2:
T
and S
, respectively) plausible/analytics#709The highlights of this release are:
This is a release candidate for testing. To update your installation, make sure your docker-compose.yml file is referencing plausible/analytics
with the following tag: v1.3.0-rc.0
. Then run the following commands:
$ docker-compose down
$ docker-compose pull plausible
$ docker-compose up -d
This will run your database migrations and boot up the new version of the app. Following changes have been made since v1.2:
T
and S
, respectively) plausible/analytics#709To update your installation, make sure your docker-compose.yml file is referencing plausible/analytics
with one of the following tags: latest
, v1
, v1.2
, v1.2.0
. Then run the following commands:
$ docker-compose down
$ docker-compose pull plausible
$ docker-compose up -d
This will run your database migrations and boot up the new version of the app. Following changes have been made since v1.1:
A quick patch release to fix deleting sites that have a spike notification configured. To update your installation, change your docker-compose.yml
file to reference plausible/analytics:v1.2-rc.1
. Then run the following commands:
$ docker-compose down
$ docker-compose pull plausible
$ docker-compose up -d
Previous release candidate: https://github.com/plausible/analytics/releases/tag/v1.2-rc.0
🚧 This is a release candidate for testing purposes. If you decide to give it a try, please leave a message of how it went on the forum
To update your installation, change your docker-compose.yml
file to reference plausible/analytics:v1.2
. Then run the following commands:
$ docker-compose down
$ docker-compose pull plausible
$ docker-compose up -d
This should run your database migrations and boot up the new version of the app. Following changes have been made since v1.1.1
: