Project structure

Our “Tract Stack as a service” does all this for you

Remember, this is a technical guide for self-install. If you want Tract Stack as a service, visit Tract Stack for managed hosting options.

Server set-up

On your server, you’ll have two or more users.

The t8k user holds the installer and admin scripts.

Each Tract Stack instance (website) will have a dedicated user account and /home/user folder.

The t8k user

Tract Stack reserves the t8k user. You’ll use this account when installing (or uninstalling) a new instance.

• Directorytractstack-installer/

  • Directoryscripts/

    • …
  • Directoryfiles/

    • …

Each tractstack instance

Once installed you’ll have a new /home/user folder. This is where all the magic happens! Everything you’ll need to configure can be done via the Story Keep.

• .env
• Directorybackup/

  • …
• Directorylog/

  • …
• Directoryreleases/

  • Directorystorykeep/

    • …
  • Directorytractstack/

    • …
  • Directorywatch/

    • …
• Directoryscripts/

  • …
• Directorysrc/

  • Directorygatsby-starter-storykeep/

    • .env.production
  • Directorytractstack-frontend/

    • .env
• Directorysrv/

  • Directorypublic_html/

    • Directorystorykeep/

      • …
    • Directorydrupal/

      • …
  • Directorytractstack-concierge/

    • .env

Systemd path unit

During the install process a service gets installed on your system. This is a build trigger that watches the /home/user/releases/watch folder. It allows a build to be called by the Story Keep.

Note: if you uninstall via the tractstack-uninstall.sh script, this service gets removed.

• Directory/etc/systemd/system/

  • t8k-user.path
  • t8k-user.service
  • …