GoatCounter is an open source web analytics platform available as a hosted service or self-hosted app

Overview

Awesome Humane Tech

GoatCounter is an open source web analytics platform available as a hosted service (free for non-commercial use) or self-hosted app. It aims to offer easy to use and meaningful privacy-friendly web analytics as an alternative to Google Analytics or Matomo.

There are two ways to run this: as hosted service on goatcounter.com, free for non-commercial use, or run it on your own server. The source code is completely Open Source/Free Software, and it can be self-hosted without restrictions.

See docs/rationale.markdown for some more details on the "why?" of this project.

There's a live demo at https://stats.arp242.net.

Please consider contributing financially if you're self-hosting GoatCounter so I can pay my rent :-) GoatCounter is sponsored by a grant from NLnet's NGI Zero PET fund.

Features

  • Privacy-aware; doesn’t track users with unique identifiers and doesn't need a GDPR notice. Fine-grained control over which data is collected. Also see the privacy policy and GDPR consent notices.

  • Lightweight and fast; adds just ~3.5K of extra data to your site. Also has JavaScript-free "tracking pixel" option, or you can use it from your application's middleware or import from logfiles.

  • Identify unique visits without cookies using a non-identifiable hash (technical details).

  • Keeps useful statistics such as browser information, location, and screen size. Keep track of referring sites and campaigns.

  • Easy; if you've been confused by the myriad of options and flexibility of Google Analytics and Matomo that you don't need then GoatCounter will be a breath of fresh air.

  • Accessibility is a high-priority feature, and the interface works well with assistive technology such as screen readers.

  • 100% committed to open source; you can see exactly what the code does and make improvements, or self-host it for any purpose.

  • Own your data; you can always export all data and cancel at any time.

  • Integrate on your site with just a single script tag:

    ">
    
    
  • The JavaScript integration is a good option for most, but you can also use a no-JavaScript image-based tracker, integrate it in your backend middleware, or parse log files.

Getting data in to GoatCounter

There are three ways:

  1. Add the JavaScript code on your site; this is the easiest and most common method. Detailed documentation for this is available at https://www.goatcounter.com/code

  2. Integrate in your middleware; send data to GoatCounter by calling the API from your backend server middleware. Detailed documentation for this is available at https://www.goatcounter.com/api#backend-integration

  3. Parse logfiles. GoatCounter can parse logfiles from nginx, Apache, CloudFront, or any other HTTP middleware or proxy. See goatcounter help import for detailed documentation on this.

Running your own

The release page has binaries for Linux amd64, arm, and arm64. These are statically compiled, contain everything you need, and should work in pretty much any Linux environment. The only other thing you need is somewhere to store a SQLite database file or a PostgreSQL connection.

GoatCounter should run on any platform supported by Go, but there are no binaries for them (yet); you'll have to build from source if you want to run it on e.g. FreeBSD or macOS.

Note this README is for the latest master; use the release-2.0 branch for the 2.0 README.

Generally speaking only the latest release is supported, although critical fixes (security, data loss, etc.) may get backported to previous releases.

Deploy scripts and such

Building from source

You need Go 1.16 or newer and a C compiler (for SQLite). If you compile it with CGO_ENABLED=0 you don't need a C compiler but can only use PostgreSQL.

Compile from source with:

$ git clone -b release-2.0 https://github.com/zgoat/goatcounter.git
$ cd goatcounter
$ go build -ldflags="-X zgo.at/goatcounter.Version=$(git log -n1 --format='%h_%cI')" ./cmd/goatcounter

You'll now have a goatcounter binary in the current directory.

The -ldflags=[..] sets the version; this isn't strictly required as such, but it's recommended as it's used to "bust" the cache for static files and may also be useful later when reporting bugs. This can be any string and doesn't follow any particular format, you can also set this to the current date or banana or anything you want really.

To build a fully statically linked binary:

$ go build -tags osusergo,netgo,sqlite_omit_load_extension \
    -ldflags="-X zgo.at/goatcounter.Version=$(git log -n1 --format='%h_%cI') -extldflags=-static" \
    ./cmd/goatcounter

It's recommended to use the latest release as in the above command. The master branch should be reasonably stable but no guarantees, and sometimes I don't write detailed release/upgrade notes until the actual release so you may run in to surprises.

You can compile goatcounter without cgo if you're planning to use PostgreSQL and don't use SQLite:

$ CGO_ENABLED=0 go build \
    -ldflags="-X zgo.at/goatcounter.Version=$(git log -n1 --format='%h_%cI')" \
    ./cmd/goatcounter

Functionally it doesn't matter too much, but builds will be a bit easier and faster as it won't require a C compiler.

Running

You can start a server with:

$ goatcounter serve

The default is to use an SQLite database at ./db/goatcounter.sqlite3, which will be created if it doesn't exist yet. See the -db flag and goatcounter help db to customize this.

Both SQLite and PostgreSQL are supported. SQLite should work well for most smaller sites, but PostgreSQL gives better performance. There are some benchmarks over here to give some indication of what performance to expect from SQLite and PostgreSQL.

GoatCounter will listen on port *:80 and *:443 by default. You don't need to run it as root and can grant the appropriate permissions on Linux with:

$ setcap 'cap_net_bind_service=+ep' goatcounter

Listening on a different port can be a bit tricky due to the ACME/Let's Encrypt certificate generation; goatcounter help listen documents this in depth.

You can create new sites with the db create site command:

$ goatcounter db create site -vhost stats.example.com -user.email [email protected]

This will ask for a password for your new account; you can also add a password on the commandline with -password. You must also pass the -db flag here if you use something other than the default.

Updating

You may need to run the database migrations when updating. Use goatcounter serve -automigrate to always run all pending migrations on startup. This is the easiest way, although arguably not the "best" way.

Use goatcounter migrate or goatcounter migrate all to manually run migrations; generally you want to upload the new version, run migrations while the old one is still running, and then restart so the new version takes effect.

Use goatcounter migrate pending to get a list of pending migrations, or goatcounter migrate list to show all migrations.

PostgreSQL

To use PostgreSQL run GoatCounter with a custom -db flag; for example:

$ goatcounter serve -db 'postgresql://dbname=goatcounter'
$ goatcounter serve -db 'postgresql://host=/run/postgresql dbname=goatcounter sslmode=disable'

This follows the format in the psql CLI; you can also use the PG* environment variables:

$ PGDATABASE=goatcounter DBHOST=/run/postgresql goatcounter serve -db 'postgresql://'

See goatcounter help db and the pq docs for more details.

Development/testing

You can start a test/development server with:

$ goatcounter serve -dev

The -dev flag makes some small things a bit more convenient for development; TLS is disabled by default, it will listen on localhost:8081, the application will automatically restart on recompiles, templates and static files will be read directly from the filesystem, and a few other minor changes.

See .github/CONTRIBUTING.markdown for more details on how to run a development server, write patches, etc.

Various aggregate data files are available at https://www.goatcounter.com/data

Comments
  • How do you run this through a proxy?

    How do you run this through a proxy?

    I'm not really familiar with Go, but I've run go build -ldflags="-X main.version=$(git log -n1 --format='%h_%cI')" ./cmd/goatcounter and it was able to download the files.

    It seems the next step is to run goatcounter serve but that just returns a goatcounter not found

    opened by Okozzie 20
  • Reports over 1 month are empty

    Reports over 1 month are empty

    Hello,

    Using the Team Kodi account, I cannot seem to generate a report greater than 1 month. When I attempt to generate a report for 3 months I end up with one of the following screens.

    Is this a known issue?

    goat1

    goat2

    opened by KarellenX 20
  • Add/expand self-hosting guide

    Add/expand self-hosting guide

    I think a step-by-step guide with examples for setting up goatcounter on a fresh VPS to a production-ready state could go a long way with making self-hosting more approachable. I've just finished setting it up myself and here are a few particular issues I encountered:

    1. time.LoadLocation(...) which is used by your tz module (used in goatcounter) expects that system has a list of all timezones available, and fails with a quite cryptic error message when it cannot find it: panic: tz.init: unknown time zone Asia/Kabul (or some other random timezone). This requires something like apk add tzdata or apt install tzdata (depending on distro) to fix.

    2. When calling goatcounter create, it's not intuitive for a first-time user that -domain is the domain where goatcounter runs, not the tracked domain. Also, I'm still not sure what the -parent parameter does, and the -h description doesn't really help. Also, I think -createdb should be the default, as otherwise it just panics saying it couldn't find the database file. serve creates the DB automatically, I don't see a reason why create shouldn't.

    3. Adding some basic instructions on how to setup goatcounter to run automatically using systemd would be nice for first timers, although I understand that it's out of scope for goatcounter. :)

    Few articles I found around the internet, which may serve as an inspiration:

    • https://rgth.co/blog/replacing-google-analytics-with-goatcounter/
    • https://daulton.ca/2021/01/openbsd-goatcounter-server/

    Lastly, I wanna say thanks for goatcounter - I love both the philosophy and UI. If it proves to work well over time, I'll gladly send some donations your way. :)

    opened by MatejKafka 19
  • i18n support

    i18n support

    Hey Martin,

    I really love what you did here. It's a really nice tool. I'm using the goatcounter the first time and for my customer I need to translate it in german, because english is not "allowed". Are you planning on internationalization/multi-language support any soon? Or is my only option currently to translate all files. I was also thinking about creating a pull request with some i18n-package.

    Thank you already, Marco

    opened by mheumann 17
  • Show State/Province Locations

    Show State/Province Locations

    I stumbled upon GoatCounter yesterday and am very impressed. (So long Matomo.) The only missing information I noticed is location by state/province. In Canada, USA, China etc, I think it's useful to be able to see what state people are visiting from.

    enhancement 
    opened by cwmke 15
  • Docker

    Docker

    I would love to make a pull request but I'm really not quiet strong with the Dockerness. I think having a Dockerfile, docker-compose.yml, and an official docker image might make it easier for certain people to use and work on goatcounter.

    opened by Th3Whit3Wolf 15
  • Is there any way to _populate_ an existing, empty, PostgreSQL database without manually pulling the schema from `goatcounter db schema-pgsql`?

    Is there any way to _populate_ an existing, empty, PostgreSQL database without manually pulling the schema from `goatcounter db schema-pgsql`?

    Is there any way to populate an existing, empty, PostgreSQL database without manually pulling the schema from goatcounter db schema-pgsql?

    Running goatcounter db create site complains about migrations that haven't been run, but running goatcounter db migrate fails with:

    goatcounter: zdb.Migrate.Run: running "2020-08-28-1-paths-tables": pq: relation "hits" does not exist
    

    Originally posted by @jbg in https://github.com/zgoat/goatcounter/issues/452#issuecomment-829985048

    opened by arp242 14
  • Site switcher in top-left corner looks squished/weird once you have a lot of sites

    Site switcher in top-left corner looks squished/weird once you have a lot of sites

    Is there a way to apply our own custom CSS to the dashboard?

    https://rgth.co/blog/replacing-google-analytics-with-goatcounter/

    I followed the tutorial above, where are the files located for the doing so?

    Thanks

    opened by Okozzie 14
  • [HELP] -stripe: must be set.

    [HELP] -stripe: must be set.

    Creating goatcounter binary from the newest source codes, and trying to starte it, then goatcounter print help messages and doesn't start.

    Does -stripe flag become essential? If so, how is necessary keys created? What parameters should I assign in Stripe? Could you tell me step-by-step procedure?

    support 
    opened by mzch 14
  • Deal with adblockers etc. better

    Deal with adblockers etc. better

    GoatCounter got added to EasyList Privacy as follows:

    ||gc.zgo.at^$third-party
    ||goatcounter.com/count^$third-party
    

    That was bound to happen sooner or later, and I guess it's not a bad sign that GoatCounter is deemed worthy of inclusion 😅 Because of the third-party option it only gets blocked if it's loaded as 3rd-party script, so goatcounter.com and such still work fine.

    However, I've had some people report that AdGuard simply blocks all of the goatcounter.com domains; the reason for this is that their DNS filter simply includes:

    ||gc.zgo.at^
    ||goatcounter.com^
    

    That's ... a rather crude approach, but it is what it is.

    It would perhaps be better if a different domain was used for the tracking; I already have goatanalytics.com so that's kind of an obvious choice. That way ad blockers can block that, and keep goatcounter.com unblocked.

    opened by arp242 13
  • My stats seem to be one month in the future

    My stats seem to be one month in the future

    Hi! I am not sure if I am mistaking something, but it appears that my stats are being dated one month ahead of now --- it is november now, but these stats are claiming to be from december. Any ideas?

    Screen Shot 2021-11-30 at 11 15 20 AM
    opened by jonsterling 12
  • Possibly a new way to do privacy preserving session tracking - address split session tracking

    Possibly a new way to do privacy preserving session tracking - address split session tracking

    https://notes.normally.com/cookieless-unique-visitor-counts/

    outlines a new way to do privacy session tracking. It preserves sessions across IP address changes. It seems similar to the simpleweb anlaytics, I am not sure if it has a similar downside as it gets updated for each request, not just once per day.

    I think this is an issue for me as I have a number of sessions that change session id's but seem to be the same session. I am connecting the sessions since the last page viewed in the prior session is the referer for the page in the new session.

    From what I can tell this is the only thing that can cause a change in the session computation for the same browser as it occurs within a 1 hour time window so salt changeover shouldn't be breaking the session chain.

    opened by rouilj 0
  • Cross compile with or without CGO

    Cross compile with or without CGO

    Pocketbase can be cross compiled with or without CGO. This is because it imports modernc SQLite.

    I just wanted to point this out as I saw in the readme that this is blocking the project easily producing releases that work in all OS / ARCH.

    the non cgo SQLite IS Slower. About 30%. It may however get better and better as modernc is in constant updates .

    opened by gedw99 2
  • Facets

    Facets

    I did not look at the underlying aggregation logic , but this thing would be awesome if it also had facets .

    So you can do cross referencing of a specific page against location of visitors , etc etc

    i expect the vision is to keep this out of the feature set ? YAGNI o guess for most people ?

    opened by gedw99 6
  • API for page views for a page

    API for page views for a page

    From what I can tell, I can get page views as a whole, /api/v0/stats/hits, but I can't get it for a page. There is an API for referrals for a page, but not page views.

    Related - the API for referrals for a page mentions you have to pass a page ID, but what if you don't know the ID, just the path? Can we support passing a path and getting info that way?

    opened by cfjedimaster 4
  • Proxied usage: Admin/Dashboard: Chrome problem

    Proxied usage: Admin/Dashboard: Chrome problem

    Thanks for a great tool! I`m using it with nginx by proxing access and this works well except admin area, details below.

    Basically it works in FireFox, but not working in Chrome. Subdomain for goat Dashboard is served under http (don`t need another certificate). But any login attempt just show login page again. I believe this is because in chrome login cookie is blocked, see screenshot:

    Screenshot 2022-12-07 at 11 40 43

    Details:

    • goatcounter started with this commandline params goatcounter serve -automigrate -db sqlite3+/<my_path>/goatcounter.sqlite3 -listen localhost:5000 -tls http latest release from release download was used for install

    • proxied admin access setup (nginx.conf) for subdomain

    	server {
    		listen       80;
    		server_name  goat.<my_domain.com>;
    		root         /;
    
    		location / {
    				proxy_set_header Host $http_host;
    				proxy_set_header X-Forwarded-For $remote_addr;
    				proxy_set_header X-Forwarded-Proto $scheme;
    				proxy_set_header X-Real-IP $remote_addr;
    				#proxy_set_header Connection "";
    				#proxy_http_version 1.1;
    				#proxy_redirect off;
    				proxy_pass http://127.0.0.1:5000;
    		}
    	}
    
    • proxied counter access setup (nginx.conf)
    location ~ /goatcounter
    {
    	# headers etc for parsing - https://github.com/arp242/goatcounter/blob/306a482eb28c9603f3c7fba684a3326432637a31/handlers/count.go
    	proxy_set_header Host "goat.gamerotor.com";
    	proxy_set_header X-Forwarded-For $remote_addr;
    	proxy_set_header X-Forwarded-Proto $scheme;
    	proxy_set_header X-Real-IP $remote_addr;
    	proxy_pass http://127.0.0.1:5000/count$is_args$args;
    }
    
    opened by IPv6 8
  • Added an automatic Docker Container Deployment

    Added an automatic Docker Container Deployment

    An official Docker container would be awesome. It simplifies the deployment a lot and opens the ability to deploy GoatCounter easily on services like Kubernetes. #643

    You just need to add a secret for your Docker-Hub password / token and your username. The Docker container gets automatically build and pushed to the repository.

    Special thanks to @baethon who originally created the Docker file.

    opened by LNA-DEV 0
Releases(v2.4.1)
  • v2.4.0(Nov 8, 2022)

    • Add a more fully-featured API that can also retrieve the dashboard statistics. See https://www.goatcounter.com/help/api for documentation.

      This is still as "v0" because some details may still change.

    • Default API ratelimit is now 4 requests/second, rather than 4 requests/10 seconds. You can use the -ratelimit flag to configure this.

    • Can now also merge paths instead of just deleting them (the "Settings → Delete pageviews" tab was changed to "Manage pageviews").

    • Add goatcounter dashboard, which uses the new API to display the dashboard in the terminal (only a basic non-interactive overview for now).

    • Add a "Show fewer numbers" user setting; this is intended to still give a reasonably useful overview of what happens on your site but prevent an “obsession” over the exact number of visitors and stats.

    • No longer store or display "pageviews": always store and display "visitors" instead.

      The visitor count is the only thing that's interesting in pretty much all cases; the "raw" pageviews are still stored for some future purposes (such as "time on page"), but are no longer stored in most other contexts.

    • Add infrastructure for "dark mode".

      This is not yet enabled by default because all "dark mode" themes look "bad" on my eyes, and I'm not really sure what works well for people who do like it.

      So some help is needed here. See: https://github.com/arp242/goatcounter/issues/586#issuecomment-1287995673

    Source code(tar.gz)
    Source code(zip)
    goatcounter-v2.4.0-freebsd-amd64.gz(10.22 MB)
    goatcounter-v2.4.0-linux-amd64.gz(10.43 MB)
    goatcounter-v2.4.0-linux-arm.gz(9.58 MB)
    goatcounter-v2.4.0-linux-arm64.gz(9.39 MB)
    goatcounter-v2.4.0-macos-amd64.gz(10.24 MB)
    goatcounter-v2.4.0-macos-arm64.gz(10.24 MB)
    goatcounter-v2.4.0-openbsd-amd64.gz(10.21 MB)
    goatcounter-v2.4.0-windows-amd64.exe.gz(10.06 MB)
  • v2.3.0(Oct 17, 2022)

    2022-10-17 v2.3.0

    • Expand campaigns: the utm_campaign or campaign parameter now is tracked separately, and add a dashboard panel for campaigns. See: https://www.goatcounter.com/help/campaigns

      Old data isn't backfilled as this information wasn't stored.

    • There are now binaries for Windows, macOS, {Free,Open}BSD, and illumos.

    • WebSockets are now disabled by default, as it turned out a lot of people had trouble proxying them. You can enable it with goatcounter serve -websocket.

    • Add -dbconn flag for serve to allow setting the maximum number of connections. The default is also lowered from 25 to 16 for PostgreSQL.

    • Add -store-every flag to control how often to persist pageviews to the database.

    • Add "Sites that can embed GoatCounter" setting to allow embedding GoatCounter in a frame.

    • Add "Hide UI for public view" setting to allow hiding the UI chrome and display only the charts.

    • Quite a few bugfixes and minor additions.

    Source code(tar.gz)
    Source code(zip)
    goatcounter-v2.3.0-darwin-amd64.gz(17.19 MB)
    goatcounter-v2.3.0-darwin-arm64.gz(13.47 MB)
    goatcounter-v2.3.0-freebsd-amd64.gz(10.14 MB)
    goatcounter-v2.3.0-linux-amd64.gz(10.35 MB)
    goatcounter-v2.3.0-linux-arm.gz(9.50 MB)
    goatcounter-v2.3.0-linux-arm64.gz(9.33 MB)
    goatcounter-v2.3.0-openbsd-amd64.gz(10.13 MB)
    goatcounter-v2.3.0-windows-amd64.exe.gz(9.98 MB)
  • v2.2.0(Feb 16, 2022)

    • The database connection string changed; you now need to use -db engine+connect string rather than engine://connect string:

      -db sqlite+[sqlite connection string]
      -db postgresql+[sqlite connection string]
      

      Various aliases such a sqlite3, postgres also work.

      The previous "url-like" strings conflicted with PostgreSQL's URL connection strings, causing confusion.

      ://-type strings without a + will be rewritten, but will issue a warning.

    • GoatCounter can now collect language statistics as well, from the Accept-Language HTTP header. This is disabled by default, but can be enabled in the site settings.

    • Charts are now drawn as a line chart by default; you can choose to use bar charts in the widget settings menu by selecting the "chart style" for the "Paths overview" and/or "Total site pageviews"

      Both charts are also completely reïmplemented by drawing on a canvas instead of aligning divs in a flexbox because rendering thousands of divs in a flexbox is actually fairly slow.

    • The "View as text table" button in the header moved to the "Chart style" section mentioned above; this checkbox was added before the configurable dashboard feature, and especially now that you can set a chart style it makes more sense to set it there.

    • Data is now sent over a WebSocket, rather than rendering everything. The upshot of this is that the perceived performance is better: it only needs to calculate the data that's initially visible, and it's okay to wait a bit for the data that's not. The downside is that you need JavaScript, but that was already the case to render the charts.

    • There is a "server management" tab in the settings which allows viewing and editing some server internals. This page is only available to users with the (new) "server management" access.

      All sites with just one user have this user's permissions automatically "upgraded"; sites with more than one user since I don't know which user should have which permissions.

      To prevent updating users, you can use (before running migrations):

      % goatcounter db query "insert into version values ('2021-12-13-2-superuser')"
      

      To update an existing user, you can use:

      % goatcounter db update users -access superuser [email protected]
      
    • Add -ratelimit flag to configure the built-in ratelimits (the default values are unchanged). See goatcounter help serve for details.

    • New translations: Italian, Spanish (Chilean), Turkish.

    Source code(tar.gz)
    Source code(zip)
    goatcounter-v2.2.0-linux-amd64.gz(9.97 MB)
    goatcounter-v2.2.0-linux-arm.gz(9.01 MB)
    goatcounter-v2.2.0-linux-arm64.gz(9.03 MB)
  • v2.1.1(Dec 25, 2021)

  • v2.1.0(Dec 1, 2021)

    Aside from a number of small fixes and improvements, major changes include:

    • Support for translations; see https://www.goatcounter.com/translating for details how to translate GoatCounter.

    • The import path is now updated to use "zgo.at/goatcounter/v2" so that e.g. "go install zgo.at/goatcounter/v2" works. This should have been done with the 2.0 release, but I didn't realize how this all worked.

    • The visitor counter now supports the start and end parameters and the JSON endpoint returns count as well, to get the total pageview count.

    • You can now make the dashboard viewable to anyone who has a secret token (e.g. https://mystats.example.com?access-token=5g4..)

    This release requires Go 1.17 to build.

    Source code(tar.gz)
    Source code(zip)
    goatcounter-v2.1.0-linux-amd64.gz(9.99 MB)
    goatcounter-v2.1.0-linux-arm.gz(9.04 MB)
    goatcounter-v2.1.0-linux-arm64.gz(9.05 MB)
  • v2.0.4(Apr 13, 2021)

  • v2.0.3(Apr 2, 2021)

  • v2.0.2(Apr 1, 2021)

    • Fix migration order.

    • Don't display the expected "Memstore.Init: json: cannot unmarshal number / into Go struct field storedSession.paths of type int64" error log on startup; this got displayed once, but was a bit confusing.

    • Display a message on startup after the first update to direct people towards the 2.0 release notes and "goatcounter reindex".

    Be sure to read the release notes for 2.0.0 as there are some incompatibilities and manual actions!

    Source code(tar.gz)
    Source code(zip)
    goatcounter-v2.0.2-linux-amd64.gz(8.22 MB)
    goatcounter-v2.0.2-linux-arm.gz(7.38 MB)
    goatcounter-v2.0.2-linux-arm64.gz(7.33 MB)
  • v2.0.1(Mar 30, 2021)

    • Fix migrations 🤦 They worked when they were written, but a bunch of things changed in GoatCounter and some older ones didn't run any more.

    • Add -test flag to goatcounter db migrate to rollback a migration, so it's easier to test if migrations will run correctly without actually changing the database.

    Be sure to read the release notes for 2.0.0 as there are some incompatibilities and manual actions!

    Source code(tar.gz)
    Source code(zip)
    goatcounter-v2.0.1-linux-amd64.gz(8.22 MB)
    goatcounter-v2.0.1-linux-arm.gz(7.38 MB)
    goatcounter-v2.0.1-linux-arm64.gz(7.33 MB)
  • v2.0.0(Mar 30, 2021)

    The version is bumped to 2.0 because this contains a number of incompatible changes: several CLI commands got changed, and it includes some large database migrations – running them is a bit more complex than the standard migrations.

    An overview of incompatible changes:

    • There are some rather large changes to the database layout for better efficiency; this means:

      • Somewhat faster queries.
      • Greatly reduced disk space requirements for the database.
      • The Browsers, systems, size, and location stats are filtered if you enter something in "filter paths". Previously this always displayed the site totals.
      • "Purge path" now works as expected for all stats.
      • Easier to add new statistics in the future.

      To update:

      1. You must first update to 1.4.2 and run all migrations from that. Updating from older versions directly to 2.0.0 will not work!

      2. Run the migrations with goatcounter serve -automigrate or goatcounter migrate.

      3. You probably want to manually run VACUUM (or VACUUM FULL for PostgreSQL) after the migration to free up unused rows. This isn't strictly required, but frees up disk space, and removes some of the autovacuum pressure that will run in the background.

      4. Run goatcounter reindex.

      All of this may take a while if you've got a lot of data. For about 500,000 pageviews it takes about 3 minutes on SQLite, but if you've got millions of pageviews it may take an hour or more.

      If you want to keep pageviews while this is running you can:

      1. Write it to a logfile from a proxy or temporary HTTP server and run goatcounter import on this after the migrations are done.

      2. Use goatcounter buffer.

    • goatcounter migrate is now goatcounter db migrate. It also behaves a bit different:

      • goatcounter db migrate pending lists only pending migrations, and will use exit code 1 if there are any pending migrations.
      • goatcounter db migrate list lists all migrations, always exits with 0.
    • If you use PostgreSQL you need PostgreSQL 12 or newer; this was already the case before and you could run in to some edge cases where things didn't work, but this is enforced now.

    • The none value got removed from the -tls flag; use tls=http to not serve TLS. This was confusingly named as you can do -tls=none,acme to still generate ACME certificates, but none implies that nothing is done.

    • goatcounter create is now goatcounter db site create, and some flags got changed:

      • -domain is now -vhost.
      • -parent is now -link.
      • -email is now -user.email.
      • -password is now -user.password.
    • The -port flag for goatcounter serve is renamed to -public-port. This should clarify that this isn't the listen port, but just the port GoatCounter is publicly accessible on.

    • The -site flag got removed from goatcounter import; you can now only use -url to set a GoatCounter site to import to. The automagic API key creation was more confusing than anything else.

      You can use goatcounter db create apitoken to create an API key from the CLI.

    • If you build from source, the build flag to set the version changed from:

      -ldflags="-X main.version=..."
      

      to:

      -ldflags="-X zgo.at/goatcounter.Version=..."
      
    • The CSV export format was increased to 2; it now includes the parsed browser and system values in addition to the User-Agent header. Version 2.0 will not be able to import the older exports from version 1.

    Other changes:

    • You can read pageviews from logfiles with the goatcounter import command; you can also send pageviews to goatcounter.com with this (you don’t need to self-host it). See goatcounter help import and the site code documentation for details.

    • You can now create multiple users; before there was always a single one. You can add users in Settings → Users.

      As a consequence, "Site settings" and "User preferences" are now split in to two screens. The Settings button in the top-right now displays only site settings, and clicking on your email address in the top right displays user preferences, which every user can configure to their liking.

    • You can now configure what's displayed on the dashboard, in what order, and configure some aspects of various "widgets". You can set it in User preferences → Dashboard. Some settings from the main settings page have moved there.

    • You can save a default view for the dashboard. Instead of always loading the last week by default, you can now configure it to load the last month, or view by day, or anything you want really.

    • You can choose which data to collect; you can disable collecting any User-Agent, location, Referrer information.

    • Ability to record state/province/district in addition to country, so it records "US-TX" or "NL-NB" instead of "United States" or "Netherlands".

      This option can be disabled separately from recording the country (enabled by default) and you can set which countries to record it for (defaults to US, RU, CH).

      This requires specifying the path to a GeoIP City database, which isn't included since it's ~30M.

    • There are now stable count.v*.js scripts that can use subresource integrity. See the integration code for a list and hashes.

    • You can use data-goatcounter-settings on the <script> tag to load the settings (requires count.v2.js or newer).

    • New goatcounter buffer command; this allows buffering of pageviews in case the backend is down, running migrations, etc. See goatcounter help buffer for more information.

    • The database for PostgreSQL is now created automatically; you no longer need to do this manually.

    • You can copy settings from a site to other sites in Settings → Sites.

    • Add goatcounter db command; you can now edit and delete sites, users, and API keys from the CLI. The create and migrate commands are now merged in to this as subcommands.

    • Add a gcbench utility for inserting random pageviews in a database; for testing and comparing performance. This might be useful for end-users too in some cases, for example to see how much performance difference SQLite and PostgreSQL will give you, or to test if frobbing with server settings makes a difference:

      $ go run ./cmd/gcbench -db sqlite://db/gcbench.sqlite3 -ndays=90 -npaths=100 -nhits=1_000_000
      $ go run ./cmd/gcbench -db postgresql://dbname=gcbench -ndays=90 -npaths=100 -nhits=1_000_000
      

      Right now it doesn't try super-hard to simulate read-world usage patterns: the distribution is always uniform, but it still gives a reasonably accurate indication for comparison purposes.

    • Many other minor changes and improvements.

    • For changes since RC1 see: https://github.com/zgoat/goatcounter/compare/v2.0.0-rc1...v2.0.0

    Source code(tar.gz)
    Source code(zip)
    goatcounter-v2.0.0-linux-amd64.gz(8.22 MB)
    goatcounter-v2.0.0-linux-arm.gz(7.38 MB)
    goatcounter-v2.0.0-linux-arm64.gz(7.32 MB)
  • v2.0.0-rc1(Mar 20, 2021)

    The version is bumped to 2.0 because this contains a number of incompatible changes: several CLI commands got changed, and it includes some large database migrations – running them is a bit more complex than the standard migrations.

    Because this includes so many changes I'll do a Release Candidate first. Please report issues if you have any problems! Barring unexpected large issues I'll do a 2.0 release next week or so.

    An overview of incompatible changes:

    • There are some rather large changes to the database layout for better efficiency; this means:

      • Somewhat faster queries.
      • Greatly reduced disk space requirements for the database.
      • The Browsers, systems, size, and location stats are filtered if you enter something in "filter paths". Previously this always displayed the site totals.
      • "Purge path" now works as expected for all stats.
      • Easier to add new statistics in the future.

      To update:

      1. You must first update to 1.4.2 and run all migrations from that. Updating from older versions directly to 2.0.0 will not work!

      2. Run the migrations with goatcounter serve -automigrate or goatcounter migrate.

      3. You probably want to manually run VACUUM (or VACUUM FULL for PostgreSQL) after the migration to free up unused rows. This isn't strictly required, but frees up disk space, and removes some of the autovacuum pressure that will run in the background.

      4. Run goatcounter reindex.

      All of this may take a while if you've got a lot of data. For about 500,000 pageviews it takes about 3 minutes on SQLite, but if you've got millions of pageviews it may take an hour or more.

      If you want to keep pageviews while this is running you can:

      1. Write it to a logfile from a proxy or temporary HTTP server and run goatcounter import on this after the migrations are done.

      2. Use goatcounter buffer.

    • goatcounter migrate is now goatcounter db migrate. It also behaves a bit different:

      • goatcounter db migrate pending lists only pending migrations, and will use exit code 1 if there are any pending migrations.
      • goatcounter db migrate list lists all migrations, always exits with 0.
    • The none value got removed from the -tls flag; use tls=http to not serve TLS. This was confusingly named as you can do -tls=none,acme to still generate ACME certificates, but none implies that nothing is done.

    • goatcounter create is now goatcounter db site create, and some flags got changed:

      • -domain is now -vhost.
      • -parent is now -link.
      • -email is now -user.email.
      • -password is now -user.password.
    • The -port flag for goatcounter serve is renamed to -public-port. This should clarify that this isn't the listen port, but just the port GoatCounter is publicly accessible on.

    • The -site flag got removed from goatcounter import; you can now only use -url to set a GoatCounter site to import to. The automagic API key creation was more confusing than anything else.

      You can use goatcounter db create apitoken to create an API key from the CLI.

    • If you build from source, the build flag to set the version changed from:

      -ldflags="-X main.version=..."
      

      to:

      -ldflags="-X zgo.at/goatcounter.Version=..."
      
    • The CSV export format was increased to 2; it now includes the parsed browser and system values in addition to the User-Agent header. Version 2.0 will not be able to import the older exports from version 1.

    Other changes:

    • You can read pageviews from logfiles with the goatcounter import command; you can also send pageviews to goatcounter.com with this (you don’t need to self-host it). See goatcounter help import and the site code documentation for details.

    • You can now create multiple users; before there was always a single one. You can add users in Settings → Users.

      As a consequence, "Site settings" and "User preferences" are now split in to two screens. The Settings button in the top-right now displays only site settings, and clicking on your email address in the top right displays user preferences, which every user can configure to their liking.

    • You can now configure what's displayed on the dashboard, in what order, and configure some aspects of various "widgets". You can set it in User preferences → Dashboard. Some settings from the main settings page have moved there.

    • You can save a default view for the dashboard. Instead of always loading the last week by default, you can now configure it to load the last month, or view by day, or anything you want really.

    • You can choose which data to collect; you can disable collecting any User-Agent, location, Referrer information.

    • Ability to record state/province/district in addition to country, so it records "US-TX" or "NL-NB" instead of "United States" or "Netherlands".

      This option can be disabled separately from recording the country (enabled by default) and you can set which countries to record it for (defaults to US, RU, CH).

      This requires specifying the path to a GeoIP City database, which isn't included since it's ~30M.

    • There are now stable count.v*.js scripts that can use subresource integrity. See the integration code for a list and hashes.

    • You can use data-goatcounter-settings on the <script> tag to load the settings (requires count.v2.js or newer).

    • New goatcounter buffer command; this allows buffering of pageviews in case the backend is down, running migrations, etc. See goatcounter help buffer for more information.

    • The database for PostgreSQL is now created automatically; you no longer need to do this manually.

    • You can copy settings from a site to other sites in Settings → Sites.

    • Add goatcounter db command; you can now edit and delete sites, users, and API keys from the CLI. The create and migrate commands are now merged in to this as subcommands.

    • Add a gcbench utility for inserting random pageviews in a database; for testing and comparing performance. This might be useful for end-users too in some cases, for example to see how much performance difference SQLite and PostgreSQL will give you, or to test if frobbing with server settings makes a difference:

      $ go run ./cmd/gcbench -db sqlite://db/gcbench.sqlite3 -ndays=90 -npaths=100 -nhits=1_000_000
      $ go run ./cmd/gcbench -db postgresql://dbname=gcbench -ndays=90 -npaths=100 -nhits=1_000_000
      

      Right now it doesn't try super-hard to simulate read-world usage patterns: the distribution is always uniform, but it still gives a reasonably accurate indication for comparison purposes.

    • Many other minor changes and improvements.

    Source code(tar.gz)
    Source code(zip)
    goatcounter-v2.0.0-rc1-linux-amd64.gz(8.18 MB)
    goatcounter-v2.0.0-rc1-linux-arm.gz(7.35 MB)
    goatcounter-v2.0.0-rc1-linux-arm64.gz(7.29 MB)
  • v1.4.2(Nov 10, 2020)

  • v1.4.1(Sep 4, 2020)

  • v1.4.0(Aug 24, 2020)

    Major changes:

    • Change defaults for -listen (#336)

      The default for the -listen flag changed from localhost:8081 to :443, which is probably a better and less confusing default for most people. There is also some more detailed docs available in goatcounter help listen.

    • Set Cache-Control header for static files (#348)

      The Cache-Control header is now set for static files. Since the "cache busting" happens based on the goatcounter version it's now recommended to set this if you're compiling GoatCounter yourself. See the updated README for instructions.

    • Add multi-factor auth (#306)

      TOTP-based multi-factor auth is now supported.

    • Better export, export API, add import feature (#316, #318, #329)

      You can now import the CSV exports, useful for migrating from self-hosted to goatcounter.com or vice versa, or for migrating from other systems. There is a web interface and a goatcounter import command.

      The export now supports a "pagination cursor", so you can export only rows you didn't previously export. This is especially useful with the new export API. which should make it easy to sync GoatCounter data with another external platform.

      See http://goatcounter.com/api for details on the export API.

    • API for sending pageviews (#357)

      Doing that with the regular /count is actually quite painful, as you quickly run in to ratelimits, need to set specific headers, etc. Adding an API endpoint for that makes things much easier.

    • API for creating and editing additional sites (#361)

    • Some redesigns (#324, #315, #321 #320)

      The "Totals" is now placed below the Pages; I think it makes more sense there. The Y-axis for the totals is now also independent. There's also been a quite a few restylings.

    • Add "text view" mode (#359)

      View your data as a simple table without too much graphics; only the main "Pages" overview is implemented for now.

    • Make it easier to skip your own views (#290)

      Previously this required adding custom code, but now loading any page with #toggle-goatcounter added will enable/disable the GoatCounter tracking for that browser.

    • Can now manage "additional sites" from self-hosted GoatCounter (#363)

      This wasn't possible before for no other reason than laziness on my part 🙃

    • public/count.js is now ISC licensed (#309)

      Previously the EUPL applied, which is fairly restrictive and may prevent people from including/self-hosting the count.js script.

    • Add goatcounter db command

      This is mostly useful for writing deploy scripts: goatcounter db schema-sqlite prints the SQLite schema, schema-pgsql prints the PostgreSQL schema, and goatcounter db test tests if the database exists.

    • Session hashes are no longer persisted to the database

      This is kind of an internal change, but session hashes are now stored in memory only and never recorded to the database. There's no real reason to persistently store this information, and this is a (small) privacy/GDPR compliance improvement.

    Source code(tar.gz)
    Source code(zip)
    goatcounter-v1.4.0-linux-amd64.gz(7.56 MB)
    goatcounter-v1.4.0-linux-arm.gz(6.80 MB)
    goatcounter-v1.4.0-linux-arm64.gz(6.80 MB)
  • v1.3.2(Jul 17, 2020)

    This is a small fix to set some server http timeouts; this is especially relevant if you run GoatCounter "directly" internet-facing, without using a proxy such as HAPRoxy, Varnish, etc.

    When using GoatCounter directly internet-facing it's liable to keep connections around for far too long, exhausting the max. number of open file descriptors, especially with "idle" HTTP/2 connections which, unlike HTTP/1.1 Keep-Alive don't have an explicit timeout.

    This isn't much of a problem if you're using a proxy in front of it, as most will have some timeouts set by default (unlike Go, which has no timeouts at all by default).

    For the backend interface, keeping a long timeout makes sense; it reduces overhead on requests (TLS setup alone can be >200ms), but for the /count request we typically want a much shorter timeout.

    Unfortunately, configuring timeouts per-endpoint isn't really supported at this point, although some possible workarounds are mentioned in 1, it's all pretty ugly. We can add "Connection: close" to just close the connection, which is probably much better for almost all cases than keeping a connection open since most people only visit a single page, and keeping a connection open in the off-chance they click somewhere again probably isn't really worth it.

    And setting any timeout is better than setting no timeout at all!

    Source code(tar.gz)
    Source code(zip)
    goatcounter-v1.3.2-linux-amd64.gz(7.55 MB)
    goatcounter-v1.3.2-linux-arm.gz(6.85 MB)
    goatcounter-v1.3.2-linux-arm64.gz(6.84 MB)
  • v1.3.1(Jul 4, 2020)

    Fixes for SQLite concurrency issues

    In some busy workloads various SQLite operations would fail due to "locked tables"; most of this is related to the session code:

    • On every pageview a new session is either read (OK) or written (LOCK!)
    • At the same time, the cron may be writing data to the db (LOCK!)

    On smaller instances this isn't much of an issue since everything is fast enough to not lock for too long, but on longer instances this can be a problem.

    Setting SetMaxOpenConns(1) solves this by limiting the connections writing to the database.

    Also set the default journal mode to WAL, which should give better performance. Both of this is done in the zgo.at/zdb update.

    Add "goatcounter help db" to document database usage a bit better.

    Source code(tar.gz)
    Source code(zip)
    goatcounter-v1.3.1-linux-amd64.gz(7.55 MB)
    goatcounter-v1.3.1-linux-arm.gz(6.85 MB)
    goatcounter-v1.3.1-linux-arm64.gz(6.84 MB)
  • v1.3.0(Jun 1, 2020)

    Note: this release contains quite a few database migrations; they make take a minute to run (depending on your table size), and you may want to run a VACUUM afterwards.

    • Remove email auth, replace -auth with -email-from (#263, #270)

      As mentioned in the 1.2 release the email authentication is now removed. You can still reset the password for old accounts.

      Since the email auth no longer exists the -auth parameter no longer makes sense. It's now replaced with -email-from, which can be set to just an email address.

      Action required: if you set the email address with -auth you'll have to change it to -email-from.

    • Add OS stats, improve accuracy of browser stats (#261)

      GoatCounter now tracks the OS/platform in addition to just the browser, and the accuracy of the browser stats should be improved.

      Action required: you'll need to populate the system_stats table:

      $ goatcounter reindex -table system_stats
      

      If you want to process all browser stats with the new logic too, then use this instead:

      $ goatcounter reindex -table system_stats,browser_stats
      
    • Improve performance (#265, #273, #274)

      Increase performance by quite a bit on large sites and time ranges.

    • Remove the per-path scaling (#267)

      Previously GoatCounter would scale the Y-axis different for every path in the dashboard, but this was more confusing than helpful. It's now always scaled to the maximum of all paths in the selected date range and filter, with a field to scale it lower on-demand if desired.

    • Add totals overview (#271)

      Add chart with totals for the selected date range and filter.

    • Add goatcounter.url(), goatcounter.filter() (#272, #253)

      Adds two new methods to the count.js script so it's easier to use write own implementation. In addition the script will now issue a console.warn() if a request isn't being counted for some reason.

    Source code(tar.gz)
    Source code(zip)
    goatcounter-v1.3.0-linux-amd64.gz(7.55 MB)
    goatcounter-v1.3.0-linux-arm.gz(6.86 MB)
    goatcounter-v1.3.0-linux-arm64.gz(6.84 MB)
  • v1.2.0(May 18, 2020)

    There are a number of changes in 1.2, and a few which require a bit of action when updating. Also see: https://www.arp242.net/goatcounter-1.2.html

    • Password authentication (#232)

      The email-based authentication has been deprecated in favour of password authentication.

      Action required Use the interface to set a password (you will get a notification about this). Email authentication still works, but will be removed in the next release, after which updating the password will be tricky.

    • Unique visit tracking (#212)

      GoatCounter now tracks unique visits (without using cookies).

      Technical documentation about the implementation is in doc/sessions.markdown.

      There are two ways to display the older stats:

      1. Do nothing; meaning that "visits" will be 0 for previous date ranges.

      2. Assign a new 'session' to every hit, so that unique visits will be the same as the number of pageviews.

      Doing option 2 is a potentially expensive database operation and not everyone may care so it's not done automatically; instructions for doing this are:

      • SQLite (do not do this on a running system; as far as I can tell there's no good way to get the next sequence ID while incrementing it):

        delete from sessions;
        update hits set session=id, first_visit=1;
        update sqlite_sequence set seq = (select max(session) from hits) where name='sessions';
        
      • PostgreSQL:

        update hits set session=nextval('sessions_id_seq'), first_visit=1;
        

      And then run goatcounter reindex.

    • Improve bot detection (#219)

      The bot detection is now improved; this will be applied to older pageviews in the database with a migration, but the cached statistics aren't updated automatically (as it can take a while for larger sites). Use the reindex command to fully update older pageviews (this is entirely optional).

    • Track events (#215)

      There is now better support to track events; see the updated documentation on the Site Code page for details.

    • Better support for campaigns (#238)

      There is now a "campaign parameters" setting; if the URL matches one of these parameters it will be set as the referrer (overriding the Referer header).

      The default is utm_campaign, utm_source, ref.

    • Better export (#221)

      The export was a quick feature added in the first version, but didn't scale well to larger sites with a lot of pageviews. This now works well for any number of pageviews.

    • Many small improvements and bug fixes

      It's almost 2 months of work, and there have been many small changes, fixes, and improvements. I didn’t keep track of them all 😅

    Source code(tar.gz)
    Source code(zip)
    goatcounter-v1.2.0-linux-amd64.gz(7.39 MB)
    goatcounter-v1.2.0-linux-arm.gz(6.73 MB)
    goatcounter-v1.2.0-linux-arm64.gz(6.71 MB)
  • v1.1.1(Mar 27, 2020)

    • Small bugfix release which fixes some small issues and improves a few small documentation issues. List of changes: https://github.com/zgoat/goatcounter/compare/v1.1.0...v1.1.1

    • The biggest change is that the saas command no longer works (and is no longer documented). It was only ever useful for hosting goatcounter.com, and has a number of assumptions and hard-coded values.

      If you're using saas, then you can migrate to serve by setting a custom domain (sites.cname) for all the sites. The serve command should work after that.

    Source code(tar.gz)
    Source code(zip)
  • v1.1.0(Mar 18, 2020)

    This list is not comprehensive, and only lists new features and major changes.

    • Incompatible Improve CLI UX (#154, #173, #175, #181)

      The entire CLI has been redone; the original wasn't very user-friendly for self-hosting. See goatcounter help for the full docs, but in brief:

      o Use "goatcounter serve" instead of just "goatcounter".
      o Create new sites with "goatcounter create".
      o Good support for TLS hosting and ACME certificates (see -tls flag).
      o Invert -prod to -dev (i.e. just drop -prod for production services, add -dev for development).
      o -smtp flag is no longer required.
      o -dbconnect                 →  -db
      o -pgsql                     →  -db postgresql://...
      o -staticdomain              →  no longer needed, but if you really want it you can
                                      append to domain: -domain example.com,static.example.com
      o -emailerrors               →  -errors mailto:...
      o goatcounter -migrate       →  goatcounter migrate
      o goatcounter -migrate auto  →  goatcounter serve -automigrate
      
    • Action required Show top referrals (#192)

      To populate the ref_stats and size_stats tables for older data, update first and then run:

      $ goatcounter reindex -confirm -table ref_stats
      $ goatcounter reindex -confirm -table size_stats
      
    • Charts are displayed in local timezone (#155)

    • Add "IgnoreIPs" setting to ignore your own views (#128)

    • Link to paths by adding a new domain setting (#138)

    • Add configurable data retention (#134)

    • Allow configuring the thousands separator (#132)

    • Allow filtering pages in the dashboard (#106)

    • Improve the integration code (#122)

    • Allow sending emails without a relay (#184)

    • Add get_query() to count.js to get query parameter (#199)

    • Allow viewing the charts by day, instead of only by hour (#169)

    Source code(tar.gz)
    Source code(zip)
  • v1.0.0(Jan 13, 2020)

Minimalist open-source web analytics

Zero-effort web analytics. This is a self-hosted open-source version of Nullitics.

null 92 Nov 10, 2022
Focalboard is an open source, self-hosted alternative to Trello, Notion, and Asana.

Focalboard Like what you see? ?? Give us a GitHub Star! ⭐ Focalboard is an open source, self-hosted alternative to Trello, Notion, and Asana. It helps

Mattermost 14k Jan 9, 2023
GoTrue is a small open-source API written in Golang, that can act as a self-standing API service for handling user registration and authentication for Jamstack projects.

GoTrue is a small open-source API written in Golang, that can act as a self-standing API service for handling user registration and authentication for Jamstack projects.

null 2 Dec 13, 2021
listmonk is a standalone high performance, self-hosted newsletter and mailing list manager with a modern dashboard. Single binary app.

listmonk is a standalone, self-hosted, newsletter and mailing list manager. It is fast, feature-rich, and packed into a single binary. It uses a PostgreSQL database as its data store.

Kailash Nadh 9.2k Jan 1, 2023
longurl is a self-hosted short url service.

longurl Introduction longurl is a self-hosted short url service. Try It Out curl -H "Content-Type:application/json" -X POST --data '{"url": "https://g

long2ice 44 Oct 24, 2022
🖖🏻 A self-hosted Quora like web application written in Go

Guora ???? A self-hosted Quora like web application written in Go 基于 Golang 类似知乎的私有部署问答应用 包含问答、评论、点赞、管理后台等功能 Quick Start (Docker Deploy) $ docker-comp

meloalright 618 Dec 27, 2022
記帳-PWA-web-app (Bookkeeping-PWA-web-app)

GoKeep (bookkeeping web app) 記帳-PWA-web-app (Bookkeeping-PWA-web-app) demo link : https://bookkepping.herokuapp.com/ 測試用帳密 : tester002 , tester002 (亦可

Yu-Zhuang Lin 5 Jan 31, 2022
Remark42 is a self-hosted, lightweight, and simple comment engine

Remark42 is a self-hosted, lightweight, and simple (yet functional) comment engine, which doesn't spy on users. It can be embedded into blogs, articles or any other place where readers add comments.

Umputun 4.1k Dec 28, 2022
Mouthful is a self-hosted alternative to Disqus.

Mouthful is a lightweight commenting server written in GO and Preact. It's a self hosted alternative

Viktoras 743 Dec 20, 2022
Hammond is a self hosted vehicle management system to track fuel and other expenses related to all of your vehicles.

Hammond is a self hosted vehicle management system to track fuel and other expenses related to all of your vehicles. It supports multiple users sharing multiple vehicles. It is the logical successor to Clarkson which has not been updated for quite some time now.

Akhil Gupta 356 Jan 2, 2023
Self-hosted video-hosting website and video archival manager for Niconico, Bilibili, and Youtube

Self-hosted video-hosting website and video archival manager for Niconico, Bilibili, and Youtube

null 793 Jan 1, 2023
listmonk is a standalone, self-hosted, newsletter and mailing list manager

listmonk is a standalone, self-hosted, newsletter and mailing list manager. It is fast, feature-rich, and packed into a single binary. It uses a Postg

Super-Smile 16 Aug 15, 2022
A self-hosted golang application that listens for Terraform pull request events via webhooks.

Atlantis Terraform Pull Request Automation Resources What is Atlantis? What does it do? Why should you use it? Stargazers over time Resources How to g

null 0 Dec 9, 2021
Mattermost is an open source platform for secure collaboration across the entire software development lifecycle.

Mattermost is an open source platform for secure collaboration across the entire software development lifecycle. This repo is the primary source for c

Mattermost 24.6k Jan 2, 2023
A simple and privacy focused analytics tool written in go.

Analytics Box Hello guys, this is privacy friendly analytics tool, Analytics Box for web written in go. It ensures user privacy but at the same time a

Ketan Iralepatil 26 Nov 27, 2022
📈 Reincarnation of mrratality - MRR analytics system for SaaS-apps

remrratality Перерождение проекта mrratality с улучшенной архитектурой и стеком. Данный проект будет использован для лабораторных работ по курсам "Тес

Sergey Kononenko 7 Sep 25, 2022
Go-web-scaffold - A simple scaffold for building web app quickly

Go-web-scaffold A simple scaffold for building web app quickly. features This sc

Statrue 3 Jan 21, 2022
A job queue and scheduler written in Go, backed by Postgres, and available over HTTP

Rickover This holds the code for a scheduler and a job queue written in Go and backed by Postgres. The goals/features of this project are: Visibility

Shyp 172 Dec 31, 2022
log4jScanner: provides you with the ability to scan internal (only) subnets for vulnerable log4j web servicelog4jScanner: provides you with the ability to scan internal (only) subnets for vulnerable log4j web service

log4jScanner Goals This tool provides you with the ability to scan internal (only) subnets for vulnerable log4j web services. It will attempt to send

Profero 482 Jan 5, 2023