Linux installer

The Linux installer sets up Grafioschtrader (GT) as a classic installation on Debian or Ubuntu: the backend runs as a system service, a web server delivers the user interface, and MariaDB stores the data. The result corresponds to a manual installation following the wiki, with the differences described below. How the installer is started and operated is described in the wiki under Installation with the Linux installer; this page explains the structure.

Structure of the installation

The following diagram shows the data flow in operation. Only the web server is reachable from outside.

graph LR
    U["Browser"]
    M["SMTP mail server"]
    Q["External data sources"]
    L["Let's Encrypt"]
    DNS["DuckDNS"]
    subgraph H["Computer with Debian or Ubuntu"]
        direction LR
        W["nginx or Apache<br/>user interface"] -->|"API, GTNet and WebSocket"| B["Service grafioschtrader<br/>backend on 127.0.0.1"]
        B -->|"Database access"| D[("MariaDB")]
        C["certbot"]
        T["DuckDNS timer<br/>(optional)"]
    end
    U <-->|"HTTP/HTTPS"| W
    B -->|"E-mail"| M
    B -->|"Prices and events"| Q
    C -.->|"Certificate"| L
    T -.->|"Updates the domain"| DNS

Course of the installation

The installer first examines the computer and then asks only the questions that apply to it. Before changing anything, it shows the complete plan with all packages, files and services; only after confirmation does it carry it out. Every step is recorded in a journal. If the installation is interrupted, for example by a power failure or a failed step, running it again continues at the same point, with the same answers and passwords.

graph TD
    I["Examination of the computer"] --> F["Questions in dialogs"]
    F --> P["Plan with all changes"]
    P -->|"Confirmation"| K["Core: packages, user, source code,<br/>database, encrypted configuration"]
    K --> A["Application: build, service,<br/>first start with database migration"]
    A --> W["Web and TLS: sites, certificate, DuckDNS"]
    W --> E["Mail check"]
    E --> R["Result"]
    K -.->|"Interruption"| N["Running again continues"]
    A -.->|"Interruption"| N
    W -.->|"Interruption"| N

Where are configuration and data?

Living with existing services

The installer changes nothing it does not own. An existing MariaDB is reused, also when root can log in only with a password; the password is asked once. Other websites on the same nginx or Apache, also those with PHP, answer after the installation as before; the installer checks this before and after every reload of the web server. Other Java and Node.js versions remain the default versions of the computer, and occupied ports are replaced by free ones. An already running DuckDNS updater is recognised, so that no second one is created. If another proxy such as Caddy owns ports 80 and 443, the installer sets up no web server of its own and writes the routes as a proposal for that proxy to /root/gt-install-webserver.conf.

Update

An update works as for every classic installation with ./gtupdate.sh as user grafioschtrader, see Update Grafioschtrader. It fetches the new source code, carries your values from application.properties over into the new template, leaves application-production.properties unchanged and rebuilds backend and user interface.

Differences to the manual installation

The manual installation following the wiki and the Linux installer lead to the same result. In some points the installer takes another way, so that it does not change other programs on the computer and can be removed completely again.