TRIP

Name: TRIP
Author: itskovacs

Stack

Minimalist Map tracker and Trip planner to visualize your points of interest (POI) and organize your next adventure details. Self-hosted with no telemetry, no tracking, no ads.

Image details

Architecture: amd64, arm64

Image size: 88 MB

User: itskovacs

Source details

Repo: itskovacs/trip

Stars: 2k

Forks: 111

Language: TypeScript

License: MIT

Latest: 1.47.0 · 14 days ago

Updated: 14 days ago

Website: itskovacs-trip.netlify.app/

Configuration

Type

Compose

Platform

linux

Image

ghcr.io/itskovacs/trip:1

Ports

${PORT:-8080}:8000

Volumes

/app/storage : /portainer/Files/AppData/Config/trip/storage

Env vars

TRIP_SECRET_KEY=${TRIP_SECRET_KEY}TRIP_OIDC_ISSUER=${TRIP_OIDC_ISSUER}TRIP_OIDC_CLIENT_ID=${TRIP_OIDC_CLIENT_ID}TRIP_OIDC_CLIENT_SECRET=${TRIP_OIDC_CLIENT_SECRET}TRIP_OIDC_REDIRECT_URI=${TRIP_OIDC_REDIRECT_URI:-http://localhost:8080/auth/callback}TRIP_OIDC_SCOPES=${TRIP_OIDC_SCOPES:-openid profile email}

Restart

unless-stopped

Source

Repo

Template by xneo1·Source

Standalone Install

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

Install on Portainer

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

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

Template Import URL

https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json

Show Me

Original stackfile

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

version: '3.8'

services:
  trip:
    image: ghcr.io/itskovacs/trip:1
    container_name: trip
    restart: unless-stopped
    ports:
      - ${PORT:-8080}:8000
    environment:
      - TRIP_SECRET_KEY=${TRIP_SECRET_KEY}
      - TRIP_OIDC_ISSUER=${TRIP_OIDC_ISSUER}
      - TRIP_OIDC_CLIENT_ID=${TRIP_OIDC_CLIENT_ID}
      - TRIP_OIDC_CLIENT_SECRET=${TRIP_OIDC_CLIENT_SECRET}
      - TRIP_OIDC_REDIRECT_URI=${TRIP_OIDC_REDIRECT_URI:-http://localhost:8080/auth/callback}
      - TRIP_OIDC_SCOPES=${TRIP_OIDC_SCOPES:-openid profile email}
    volumes:
      - /portainer/Files/AppData/Config/trip/storage:/app/storage
    networks:
      - trip-network

networks:
  trip-network:
    driver: bridge

Or deploy it directly from the source:

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

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

TRIP

📝 Table of Contents

📦 About
🌱 Getting Started
📸 Demo

📦 About

TRIP (Tourism and Recreational Interest Points) is a self-hostable minimalist Map tracker and Trip planner to visualize your points of interest (POI) and organize your next adventure details.
Core Features:

Map and manage POIs on interactive maps
Plan multi-day trips with detailed itineraries
Collaborate and share with travel companions

No telemetry. No tracking. No ads. Free, forever.
See the 📸 demo to explore TRIP in action.

🌱 Getting Started

If you need help, feel free to open a discussion.
Deployment is designed to be simple using Docker.

Option 1: Docker Compose (Recommended)

Use the docker-compose.yml file provided in this repository. No changes are required, though you may customize it to suit your needs.
Run the container:

docker-compose up -d

Option 2: Docker Run

# Ensure you have the latest image
docker pull ghcr.io/itskovacs/trip:1

# Run the container
docker run -d -p 8080:8000 -v ./storage:/app/storage ghcr.io/itskovacs/trip:1

Configuration

Refer to the configuration documentation to set up OIDC authentication and other settings.

!TIP See Documentation to learn more.

📸 Demo

A demo is available at itskovacs-trip.netlify.app.

Made with ❤️ in BZH

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.

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/trip/storage

Image won't pull

Test the pull directly on the host: docker pull ghcr.io/itskovacs/trip:1

"manifest unknown" means the tag no longer exists.
"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
Check yours with uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.

Container keeps restarting

The unless-stopped restart policy relaunches the app after every crash, so the real error can scroll past.

Check the logs right after a restart, the last few lines before it died are the useful ones.
Get the exit code with docker inspect <container> --format '{{.State.ExitCode}}'
Still stuck? Redeploy once with the restart policy set to no so the failure stays visible.

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.

Bug within the app: Open an issue on itskovacs/trip
Template not working: Open an issue on xneo1/portainer_templates
This website not working: Open an issue on lissy93/portainer-templates

A Compose stack

TRIP 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 TRIP needs bundled into one download. This template pulls ghcr.io/itskovacs/trip:1, which Docker fetches once (about 88 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. TRIP's comes from the GitHub Container Registry, published by itskovacs.

Version tags

The bit after the colon in the image name is the version tag. This one pins 1, so every redeploy gives you that exact build until you bump it yourself.

Which machines it runs on

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

Volumes

A volume is where TRIP 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:

/app/storage from /portainer/Files/AppData/Config/trip/storage on the host

Environment variables

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

TRIP_SECRET_KEY, pulled from your own environment
TRIP_OIDC_ISSUER, pulled from your own environment
TRIP_OIDC_CLIENT_ID, pulled from your own environment
TRIP_OIDC_CLIENT_SECRET, pulled from your own environment
TRIP_OIDC_REDIRECT_URI, defaults to http://localhost:8080/auth/callback
TRIP_OIDC_SCOPES, defaults to openid profile email

Restart policy

The restart policy here is unless-stopped, so Docker restarts TRIP after a crash or reboot, but leaves it off when you stop it on purpose. You can change this on the deploy screen. The choices are no (never restart), on-failure (only after a crash), unless-stopped (restart unless you stop it), and always (bring it back no matter what).

Networking

Nothing custom is set, so TRIP 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 trip. That's what you'll spot in the containers list and use in commands like docker logs trip.

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

TRIP is open source, released under the MIT 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 TRIP up. Add the template list to Portainer once, then deploying TRIP is a click rather than a wall of config.

TRIP

Image details

Source details

Configuration

Standalone Install

Install on Portainer

Template Import URL

Project Documentation

TRIP

📝 Table of Contents

📦 About

🌱 Getting Started

Option 1: Docker Compose (Recommended)

Option 2: Docker Run

Configuration

📸 Demo

Troubleshooting

Check the logs first

Permission denied on volumes

Image won't pull

"exec format error"

Container keeps restarting

Stack won't deploy

Raise an issue

Config glossary

A Compose stack

The app image

Where the image comes from

Version tags

Which machines it runs on

Volumes

Environment variables

Restart policy

Networking

Container name

Platform

Open source license

Portainer app templates

Similar apps