travelynx | Traewelling-inspired journey logger with realtime data

travelynx depends on a set of Perl modules which are documented in cpanfile. After installing the dependencies mentioned above, you can use carton or cpanminus to install Perl depenencies locally. In the project root directory (where cpanfile resides), run either. and set PERL5LIB=.../local/lib/perl5 before executing any travelynx commands (see configs in the examples directory) or wrap them with carton exec, e.g. carton exec hypnotoad index.pl.
First, you need to set up a PostgreSQL database so that travelynx can store user accounts and journeys. It must be at least version 9.4 and must use a UTF-8 locale. The following steps describe setup on a Debian 9 system; setup on other distributions should be similar. Your server also needs to be able to send mail. Set up your MTA of choice and make sure that the sendmail binary can be used for outgoing mails. Mail reception on the server is not required.
Write down a strong random password
Create a postgres user for travelynx: sudo -u postgres createuser -P travelynx (enter password when prompted)
Create the database: sudo -u postgres createdb -O travelynx travelynx
Copy examples/travelynx.conf to the application root directory (the one in which index.pl resides) and edit it. Make sure to configure db, cache, mail, and secrets.
Initialize the database: carton exec perl index.pl database migrate or PERL5LIB=local/lib/perl5 perl index.pl database migrate
Set up a travelynx service using the service supervisor of your choice (see examples/travelynx.service for a systemd unit file)
Configure your web server to reverse-provy requests to the travelynx instance. See examples/nginx-site for an nginx config.
Install a timeout 5m perl index.pl work -m production cronjob. It is used to update realtime data and perform automatic checkout and should run every three minutes or so, see examples/cron.
Note that travelynx Docker support is experimental and, in its current form, far from best practices. Pull requests are appreciated. First, you need to set up a PostgreSQL database so that travelynx can store user accounts and journeys. It must be at least version 9.4 and must use a UTF-8 locale. See above (or examples/docker/postgres-init.sh) for database initialization. You do not need to perform the database migrate step. Next, you need to prepare three files that will be mounted into the travelynx container: travelynx configuration, e-mail configuration, and imprint and privacy policy. For the sake of this readme, we assume that you are using the local/ directory to store these. travelynx consists of two runtimes: the web application and a background worker. Your service supervisor (or docker compose / docker stack / kubernetes setup) should orchestrate them somewhere along these lines. To install an update: stop worker and web application, update the travelynx image, and start them again. Database migrations will be performed automatically. Note that downgrades are not supported.
mkdir local
copy examples/travelynx.conf to local/travelynx.conf and configure it.
copy examples/docker/email-transport.sh to local/email-transport.sh and configure it. The travelynx container does not contain a mail server, so it needs a separate SMTP server to send mail. It does not receive mail.
create local/imprint.html.ep and enter imprint as well as privacy policy data.
Configure your web server to reverse-provy requests to the travelynx instance. See examples/nginx-site for an nginx config.
docker pull derfnull/travelynx:latest
Start web application: docker run -p 8093:8093 -v ${PWD}/local:/local:ro travelynx:latest
Wait until localhost:8093 responds to requests
Start worker: docker run -v ${PWD}/local:/local:ro travelynx:latest worker