Skip to content

armgit / macro

Public Imported from GitHub
0

Macro is a unified workspace for teams: email, chat, docs, tasks, agents, calls, and CRM — @-linked together with shared AI memory.

3.7 KB
Raw Blame

Macro App Frontend

This is the root directory for the solidjs frontend application known as Macro

We use the bun as a javascript package manager and runtime for the vite development server.

The production application is compiled down to a static javascript bundle using a traditional SPA-like architecture.

Production analytics configuration

just ios-build uses an existing VITE_POSTHOG_API_KEY environment variable or fetches it from Doppler web-release/prd and exports it for the build. Install the Doppler CLI and authenticate with read access to that config. The build fails if the key cannot be fetched or is empty; no env file is created.

For other local production builds, set VITE_POSTHOG_API_KEY in the environment or the ignored apps/web/.env.production.local. Vite loads this file automatically. CI continues to inject the GitHub POSTHOG_API_KEY secret. Keep the value out of tracked env files.

Toolchain Management

If you have the nix package manager installed on your system then you can drop into a nix shell where everything you need is installed for you.

nix develop

Local Playwright

For the local smoke suite, prefer the repo-level harness:

just local-e2e

This starts a named headless stack through the same xtask orchestration as just run_local, seeds local fixture data into that isolated instance, and runs Playwright against a Vite server connected to the instance proxy. The harness generates local bearer-token auth from the stack's generated env; it does not need a refresh token or the legacy local-E2E compose overlay.

Set LOCAL_E2E_INSTANCE to reuse a different named stack. The default is local-e2e.

The local smoke suite can import localE2ESeed from tests/e2e/fixtures/local-e2e-seed.ts. That helper loads the actual seed files used by seed_cli (local_e2e/users.json, documents.json, channels.json, and channel_messages.json) and exposes raw rows plus lookup maps by id/name/email. The small local_e2e/manifest.json only names the smoke aliases.

For Playwright UI mode, run:

just local-e2e-ui

Tauri 🤝 Macro

We are currently in the process of bundling the frontend javascript application as a Tauri app. You will need the following dependencies installed on your system to develop in this environment.

  1. The rust programming language
  2. The Tauri CLI
  3. The bun runtime
  4. For Android Development The Android Studio IDE
  5. For iOS Development XCode for MacOS

The default shell contains the shared frontend and Tauri CLI tooling. Use the focused shells when developing targets with large platform dependencies:

nix develop .#tauri-linux    # GTK/WebKitGTK/GStreamer desktop stack
nix develop .#tauri-android  # Android Studio, SDK/NDK, emulator, and Rust targets

tauri-android is available on x86_64 Linux. On macOS, use the default shell with the platform IDE installed outside Nix (Xcode for iOS or Android Studio for Android).

Running Tauri

After the dependencies are installed you can use the tauri cli to run the app. Note the first command should be substituted with the package manager you used to install the cli e.g. cargo, bun, etc. In the nix shell the cli is installed for the cargo package manager.

Run the Desktop App for your host operating system

cargo tauri dev

Run the Android App

cargo tauri android dev

Run the iOS App (note: I haven't had the chance to test this yet)

cargo tauri ios dev