TRIP (Tourism and Recreational Interest Points) is a self-hosted POI map and trip planner. You can save places, plan multi-day trips, track details, share routes, and keep everything on your own server.

This fork runs a hosted personal TRIP instance. It keeps the base app and adds the pieces I need for real trip planning: local Docker deploys, itinerary fields, map handoff links, imports, printable roadbooks, and automation helpers.

Use this README and DEPLOYMENT.md for this fork's Docker setup.

This fork adds:

• Local deploys with make deploy, docker-compose.yml, .env.example, health checks, persistent storage defaults, and closed registration.
• Source-built Docker images. The compose stack builds trip-local from this checkout, so deployed code matches the repo.
• Itinerary fields for home/start coordinates, day start times, stop duration, nullable arrival and check-in times, currency, booking status, references, cancellation deadlines, cost status, fees, checkout details, and trip-only places.
• Faster trip editing: collapsible days, stronger mobile layout, clearer selected-place and selected-item actions, a better time picker, and retiming previews based on duration and travel time.
• Accommodation planning across multiple days, with booking/cost metadata and routing from the right base location.
• Map handoff tools for Mapy.com tiles, Mapy.com roadbook QR links, Google Maps shortcuts, coordinate navigation, Plus Codes, lat/lng parsing, and Google Maps share-link resolution.
• Place tools for category icons, saved URLs, visit duration, Google-backed creation, Google My Maps/list imports, and temporary trip-only places.
• Shared and printed trip views with a cleaner itinerary, roadbook output, route links, QR codes, and a JPG cover.
• Offline support for cached API reads and map tiles.
• A local API helper at skills/trip-planner/scripts/trip_api.py for API docs, token-backed place creation, roadtrip JSON validation, dry runs, and idempotent imports.
• Public-repo guardrails for .env, storage, backups, SQLite files, and temporary working files.

Alembic migrations for the local data model live in backend/trip/alembic/versions/.

Full deployment guide: https://martin-gomola.github.io/trip/docs/getting-started/deploy

Copy the example config, edit it, then deploy:

cp .env.example .env
make deploy

Open the app at:

http://localhost:8050

For a server, replace localhost with the server IP or point your reverse proxy at port 8050.

After you create the first user, keep registration closed:

REGISTER_ENABLE=false

make deploy        # build local image, recreate container, wait for health
make build         # build the local Docker image
make restart       # recreate the container without rebuilding
make logs          # follow logs for the trip service
make ps            # show service status
make down          # stop the stack

make deploy is the normal path for this fork. Plain docker compose up -d can try to pull an image before the local image exists, so use the Makefile when you change code.

Edit .env for host-level settings:

Keep real values in .env; do not commit them.

TRIP stores runtime data under:

${DATA_DIR}/trip/storage/

That directory contains the SQLite database, uploaded assets, attachments, backups, and optional config.env. Back it up from the host:

tar -czf trip-backup-$(date +%Y%m%d-%H%M%S).tar.gz -C "${DATA_DIR:-/srv/docker}" trip/storage

TRIP uses the MIT License. See LICENSE.

Based on the original TRIP project by itskovacs.