Portainer Templates logo

Portainer Templates

Traggo Traggo

Stack

Time Tracking

Traggo is a tag-based time tracking tool. In Traggo there are no tasks, only tagged time spans.

Image details

Pulls: 2.0M
Architecture: amd64, arm64, arm/v7, 386, ppc64le, s390x
Image size: 7 MB
Latest: 0.8.3
User: traggo
Created: Apr 28, 2019
Updated: 4 months ago
Status: active

Source details

Repo: traggo/server
Stars: 2k
Forks: 90
Language: Go
License: GPL-3.0
Latest: v0.8.3 · 4 months ago
Updated: 4 months ago
Website: traggo.net/

Configuration

Type
Compose
Platform
linux
Image
traggo/server:latest
Ports
3030:3030
Volumes
/opt/traggo/data : /portainer/Files/AppData/Config/traggo/data
Env vars
TRAGGO_DEFAULT_USER_NAME=adminTRAGGO_DEFAULT_USER_PASS=mynewpassword
Source
Repo

Template by xneo1·Source

Standalone Install

Select an install method, to see config/commands for deploying Traggo

Installation method

Install on Portainer

Import all app templates into your Portainer instance, for easy 1-click deploys

  1. Ensure both Docker and Portainer are installed, and up-to-date
  2. Log into your Portainer web UI
  3. Under Settings → App Templates, paste the below URL
  4. Head to Home → App Templates, and the list of apps will show up
  5. Select Traggo, fill in any config options, and hit Deploy

Template Import URL

https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me demo
Original stackfile

The compose file this template deploys, straight from its repo:

services:
  traggo:
    image: traggo/server:latest
    ports:
      - 3030:3030
    environment:
      TRAGGO_DEFAULT_USER_NAME: "admin"
      TRAGGO_DEFAULT_USER_PASS: "mynewpassword"
    volumes:
      - /portainer/Files/AppData/Config/traggo/data:/opt/traggo/data

Or deploy it directly from the source:

git clone https://github.com/xneo1/portainer_templates
cd portainer_templates
docker compose -f Template/Stack/traggo.yml up -d

More install options in our documentation, or see traggo/server for app-specific guidance.

<a href="https://github.com/traggo/logo">
    <img height="300px" src="https://raw.githubusercontent.com/traggo/logo/master/logo.png" />
</a>


traggo/server

tag-based time tracking


<a href="https://travis-ci.com/traggo/server">
    <img alt="Build Status" src="https://travis-ci.com/traggo/server.svg?branch=master">
</a>
 <a href="https://codecov.io/gh/traggo/server">
    <img alt="codecov" src="https://codecov.io/gh/traggo/server/branch/master/graph/badge.svg">
</a>
<a href="https://goreportcard.com/report/github.com/traggo/server">
    <img alt="Go Report Card" src="https://goreportcard.com/badge/github.com/traggo/server">
</a>
<a href="https://hub.docker.com/r/traggo/server">
    <img alt="Docker Pulls" src="https://img.shields.io/docker/pulls/traggo/server.svg">
</a>
<a href="https://github.com/traggo/server/releases/latest">
    <img alt="latest release" src="https://img.shields.io/github/release/traggo/server.svg">
</a>


Traggo is a tag-based time tracking tool. In Traggo there are no tasks, only tagged time spans.
With tags, Traggo tries to be as customizable as possible, f.ex. if you work on different projects you could add a project-tag. If you like to see statistics from the different things you do, you could add a type-tag with values like email, programming, meeting. You can do it just as you like.
If you want to use Traggo, you need to host it yourself. This way, you have the full control over your data and no third-party may be able to read it. Have a look at our Install Guide.

Features

  • easy to setup
  • time tracking (obviously)
  • customizable dashboards with diagrams
  • a list and calendar view of the tracked time
  • sleek web ui with multiple themes
  • simple user management
<img width="265" alt="traggo list" src="https://raw.githubusercontent.com/traggo/server/HEAD/.github/traggo_list.png">
 
<img width="265" alt="traggo list" src="https://raw.githubusercontent.com/traggo/server/HEAD/.github/traggo_calendar.png">
 
<img width="265" alt="traggo list" src="https://raw.githubusercontent.com/traggo/server/HEAD/.github/traggo_dashboard.png">

Install ᛫ Configuration ᛫ Setup Dev Environment

Versioning

We use SemVer for versioning. For the versions available, see the tags on this repository.

Serve Traggo on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.

Proxying traggo.example.com to http://traggo:3030

Add this to your Caddyfile

traggo.example.com {
	reverse_proxy http://traggo:3030
}

Check the logs first

Nine times out of ten the logs tell you exactly what went wrong.

  • In Portainer, go to Containers, click the container, then Logs. Or run docker logs <container>
  • Exit codes help too: 137 means killed, usually out of memory. 126 or 127 means the command inside the image is broken.

Port already in use

If deployment fails with "Bind for 0.0.0.0:3030 failed: port is already allocated", something else on your server is using that port.

  • Find what's using it: sudo ss -tlnp | grep :3030
  • Stop the other service, or pick a different host port. In 3030:3030 only the left number is yours to change, the right one belongs to the app.

Running but the page won't load

The container is up but nothing appears in your browser.

  • Use your server's real IP: http://your-server-ip:3030. The 0.0.0.0 link Portainer shows isn't a real address.
  • Give it a minute after first deploy, traggo can take a while to initialise.
  • Make sure your firewall allows the port, e.g. sudo ufw allow 3030

Permission denied on volumes

If the logs show "permission denied", the app can't write to its data folder on the host.

  • Fix the ownership: sudo chown -R 1000:1000 /portainer/Files/AppData/Config/traggo/data

Image won't pull

Test the pull directly on the host: docker pull traggo/server:latest

  • "manifest unknown" means the tag no longer exists. This template uses latest, so try pinning a specific version instead.
  • "toomanyrequests" is the Docker Hub rate limit. Log in with docker login to raise it.
  • "no space left on device" means a full disk. Reclaim space with docker system prune

"exec format error"

This means the image was built for a different CPU architecture than your server.

  • This image supports: amd64, arm64, arm/v7, 386, ppc64le, s390x
  • Check yours with uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.

Stack won't deploy

Compose stacks fail fast on small mistakes, and Portainer shows the reason just above the editor.

  • YAML only accepts spaces for indentation, a single tab breaks the whole file.

Raise an issue

Found something which isn't working as it should? Here's how to report it.

A Compose stack

Traggo is a Compose stack, a set of containers defined in one file and brought up together by Portainer, then started and stopped as a single app.

The app image

An image is the app packed up ready to go, everything Traggo needs bundled into one download. This template pulls traggo/server:latest, which Docker fetches once (about 7 MB) and then starts your own copy from.

Where the image comes from

Docker pulls its images from registries, public libraries of ready-built apps. Traggo's comes from Docker Hub, published by traggo.

Version tags

The bit after the colon in the image name is the version tag. Here it's latest, which always points at the newest build, so a redeploy can bump you to a newer release without you asking. Newest right now is 0.8.3. Pin a specific tag if you would rather stay on one version.

Which machines it runs on

Every image is built for particular CPU types. This one ships for amd64, arm64, arm/v7, 386, ppc64le, s390x, so it runs on both regular x86 servers and ARM boards like a Raspberry Pi.

Ports

A port is the door the app answers on. A mapping like 3030:3030 means it's reachable on port 3030 of your server, where the left number is yours to change and the right one belongs to the app. It opens:

  • 3030:3030

Volumes

A volume is where Traggo keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:

  • /opt/traggo/data from /portainer/Files/AppData/Config/traggo/data on the host

Environment variables

Environment variables are the settings you hand over when you deploy, things like a password or a timezone. Traggo takes 2 of them, all with defaults you can leave alone or tweak:

  • TRAGGO_DEFAULT_USER_NAME, defaults to admin
  • TRAGGO_DEFAULT_USER_PASS, defaults to mynewpassword

Networking

Nothing custom is set, so Traggo sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.

Container name

Once it's deployed, Portainer names the container traggo. That's what you'll spot in the containers list and use in commands like docker logs traggo.

Platform

The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.

Open source license

Traggo is open source, released under the GPL-3.0 license. In plain terms the code is out in the open, so you're free to run it and change it to fit what you need.

Portainer app templates

Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Traggo up. Add the template list to Portainer once, then deploying Traggo is a click rather than a wall of config.