fdean/trip-server repository overview

⁠TRIP - Trip Recording and Itinerary Planner

Note: this project is no longer supported. It has been superseded by trip-server-2⁠ See the project's README⁠ for details.

⁠AngularJS Unsupported

This web application uses the AngularJS⁠ framework, Google's support for which, officially ended as of January 2022. There are now a number of vulnerabilities in the dependencies and sub-dependencies of the unsupported AngularJS which I am not in a position to fix.

The application has been rewritten, mostly in C++ running on Unix/Linux/macOS, with fundamentally the same PostgreSQL database, with minimal dependencies.

The rewrite in C++ of [Trip Server v2][trip-server-2] is now complete, supporting all the use cases of this version (Trip Server v1). See the README⁠ for further details. It can be run alongside v1.

You should migrate to v2 which should be relatively easy in most environments. The Trip Server v1 project will be archived in the near future.

The Docker Containers for Trip Server v2 are here⁠.

⁠Introduction

TRIP is a JavaScript web-based application supporting trip recording and itinerary planning. It is designed to be a lightweight server application such that it can be run on relatively low power devices like the Raspberry Pi⁠.

The intended use is for a hiker, mountain-biker or other adventurer, to be able to publish and share their planned itinerary, then subsequently log their positions at intervals, allowing someone else to be able to monitor their progress.

In the event of contact being lost, the plans and tracking information can be passed to rescue services etc., to assist with locating the missing adventurer.

The web client⁠ is an AngularJS⁠ single-page application (SPA⁠) which can be served as static files using a web server such as Apache⁠, or served by the TRIP server application itself.

The following features are provided:

• Remote tracking server—client applications such as TripLogger Remote for iOS⁠ – (on the App Store⁠) or GPSLogger for Android⁠ can be used to submit locations to the server.

• Sharing tracks with others.

• Viewing tracks on a map provided by a tile server, e.g. OpenStreetMap tiles.

• Creating and sharing itineraries using the Markdown markup language.

• Using the map, interactively creating routes and waypoints for an itinerary.

• Uploading and downloading routes, tracks and waypoints for an itinerary as a GPX⁠ file.

• Viewing routes, tracks and waypoints of an itinerary on the map.

• Splitting and joining routes and tracks.

• Deleting individual points from routes and tracks.

⁠Tags and Dockerfile links

• 1.11.7⁠

⁠How to use this image

$ docker network create trip-server
$ docker run --network trip-server --network-alias postgis -e POSTGRES_PASSWORD=secret -d fdean/trip-database
$ docker run --network trip-server -e TRIP_SIGNING_KEY=secret -e TRIP_RESOURCE_SIGNING_KEY=secret -e POSTGRES_PASSWORD=secret --publish 8080:8080 -d fdean/trip-server

The application contains a small amount of test data. Login using one of the following users and credentials:

[email protected]  rasHuthlutcew7
[email protected] 7TwilfOrucFeug

See the user documentation⁠ for information on using the application.

The source is on GitHub⁠.