extra-apps

Extra Applications

The AutomateLinux ecosystem integrates several external applications. These are typically stored outside the main automateLinux repository but are linked for easy access.

Locating Applications

The extraApps/ Directory

The primary entry point for finding external apps is the extraApps/ directory in the root of the automateLinux workspace.

ls -l ~/coding/automateLinux/extraApps

This directory contains symlinks to the actual source locations:

• cad: Points to ~/coding/cad/
• loom: Points to ~/coding/loom/
• publicTransportation: Points to ~/coding/publicTransportation/

Direct Paths

• CAD App: /home/yaniv/coding/cad
• Public Transportation (PT) App: /home/yaniv/coding/publicTransportation

Port Management

External apps often run local development servers. Their ports are managed centrally by the daemon.

Current Standard Mappings

Updating Ports

If you move an app to a different port, update the daemon so macros and proxies continue to work:

d setPort --key pt --value 3005

Editing and Permissions

[!IMPORTANT] Use Symlinks for Access: When accessing or editing files for these external applications, ALWAYS use the symlinks located in ~/coding/automateLinux/extraApps/.

Correct: ~/coding/automateLinux/extraApps/cad/src/file.ts Incorrect: ~/coding/cad/src/file.ts

Using the extraApps path prevents redundant permission requests and maintains workspace context. The user has granted permission for the automateLinux workspace, so staying within its directory structure (via symlinks) is preferred.

Related Commands

• d listPorts: See all currently registered app ports.
• d publicTransportationOpenApp: Opens the PT app in Chrome based on the registered port.
• d restartLoom: Management for the Loom screen recording integration.