Choose a run model

One alpha — four practical ways in

Start with a local test. Move to an installed app, container stack, or long-running web host only when that lifecycle matches what you need.

01 Windows · macOS · Linux

Direct source

An agent keeps the three live source repositories connected, prepares PostgreSQL, and starts the app.

Copy the source prompt

02 Windows · macOS · Linux

Docker Compose

An agent prepares the complete Linux web app and private PostgreSQL stack, then waits for health.

Copy the Docker prompt

03 Windows x64

Agent-guided Windows app

Use the experimental per-user workflow with an agent operating the app and database setup.

Copy the Windows prompt

04 Windows · Linux · macOS

Headless web host

Publish a long-running web service when you are ready to own its runtime, security, and backups.

Copy the host prompt

macOS status: interactive source runs are supported for alpha testing. macOS x64 and arm64 publish targets are also present, while actual-host evidence for long-running headless macOS deployment is still pending.

01

Clone the complete alpha source graph

Run these commands from one parent folder. Use the exact names and casing because the default build replaces package references with direct project references from these sibling repositories.

git clone --branch main --single-branch https://github.com/fyziktom/CanDoItAll.git
git clone --branch main --single-branch https://github.com/fyziktom/CanDoItAll.Components.git
git clone --branch main --single-branch https://github.com/fyziktom/CanDoItAll.FileTools.git
cd CanDoItAll

02

Use the prepared direct-source prompt

Open the parent folder or CanDoItAll repository in Codex or Claude Code, then paste this request:

Prepare and run the current CanDoItAll public alpha from source on this Windows, macOS, or Linux machine. In one parent directory, clone or update only the main branches of https://github.com/fyziktom/CanDoItAll, https://github.com/fyziktom/CanDoItAll.Components, and https://github.com/fyziktom/CanDoItAll.FileTools using the exact sibling folder names CanDoItAll, CanDoItAll.Components, and CanDoItAll.FileTools. Before updating an existing clone, inspect its origin, branch, and working tree; preserve local changes and ask before any conflicting operation. Keep the default local source dependency mode and direct project references; do not replace Components or FileTools with package builds. Record the commit SHA of all three repositories. Read the current README and installing-instances documentation, use the SDK selected by global.json, prepare and start PostgreSQL 16 as documented for this host, apply the required database setup, and start the CanDoItAll web app. Stay with the setup until both /health and /api/runtime/operations pass. Then tell me the local URL, all three source commits, where app and database data are stored, and exactly how to stop and start everything again. Ask before requesting administrator access, installing system-wide software, changing external services, or replacing or removing existing data.

03
Keep the agent until both checks pass

The health endpoint confirms the app and database are ready. The runtime operations endpoint reports the active platform, host profile, capabilities, and path readiness without exposing secrets.
```
curl --fail http://127.0.0.1:5032/health
curl --fail http://127.0.0.1:5032/api/runtime/operations
```
The selected route may use a different port. Use the local URL reported by the running app or setup agent.

Prepared agent prompt

Ask the agent to own the Compose startup

The agent should prepare the complete source graph, database secret, containers, readiness checks, and safe shutdown instructions.

Prepare and run the current CanDoItAll public alpha with Docker Compose on this machine. In one parent directory, clone or update only the main branches of https://github.com/fyziktom/CanDoItAll, https://github.com/fyziktom/CanDoItAll.Components, and https://github.com/fyziktom/CanDoItAll.FileTools using those exact sibling folder names. Before updating an existing clone, inspect its origin, branch, and working tree; preserve local changes and ask before any conflicting operation. Keep all three repositories connected as source build contexts and record their commit SHAs. Read the current container operations documentation, prove that a working Linux Docker Compose v2 engine is available, prepare the ignored .env and .secrets/db-password files with a new local-only password, validate the resolved Compose model without printing secrets, then run the complete app and PostgreSQL stack with docker compose up -d --build --wait. Stay with the setup until the app is healthy at http://localhost:8080 and the runtime operations endpoint responds. Tell me the three source commits, container and volume status, where durable data lives, and how to stop and restart the stack without deleting volumes. Ask before changing shared Docker resources, requesting administrator access, or removing any container, volume, repository, or existing data.

Before you start

Keep the three source repositories together

The image build expects CanDoItAll, CanDoItAll.Components, and CanDoItAll.FileTools as sibling folders. The guided setup above can prepare this layout for you.

PowerShell

Prepare local configuration and start Compose

Copy-Item .env.example .env
New-Item -ItemType Directory -Force .secrets | Out-Null
Set-Content -NoNewline .secrets/db-password 'change-this-local-password'
docker compose up -d --build --wait

Bash or zsh

Use the same stack on macOS or Linux

cp .env.example .env
mkdir -p .secrets
printf '%s' 'change-this-local-password' > .secrets/db-password
docker compose up -d --build --wait

Keep your data

Stop cleanly when you finish testing

Normal shutdown preserves the app-data and db-data volumes. Do not add --volumes unless you deliberately want to delete both data stores.

docker compose down

Read container operations

Prepared agent prompt · Windows x64

Keep the agent responsible through database health

Prepare the current CanDoItAll public alpha as an agent-guided per-user Windows x64 app. This is an experimental source-based workflow, not a conventional released installer. In one parent directory, clone or update only the main branches of https://github.com/fyziktom/CanDoItAll, https://github.com/fyziktom/CanDoItAll.Components, and https://github.com/fyziktom/CanDoItAll.FileTools using the exact sibling folder names CanDoItAll, CanDoItAll.Components, and CanDoItAll.FileTools. Before updating an existing clone, inspect its origin, branch, and working tree; preserve local changes and ask before any conflicting operation. Keep direct source project references enabled and record all three commit SHAs. Read the current installed-web-app and installing-instances documentation, use the SDK selected by global.json, inspect whether a working Linux Docker engine or the documented per-user native PostgreSQL 16 route is appropriate, and let the current Windows setup workflow create, start, and verify the dedicated database. Publish and start the per-user Release app, keep the session open until both /health and /api/runtime/operations pass, then tell me the local URL, source commits, install root, database engine and data location, and how to start, stop, repair, back up, and update the alpha. Ask before requesting administrator access, installing system-wide software, changing shared Docker resources, or replacing or removing existing data.

Agent-operated command

The agent may run the current workflow from the app repository

& .\tools\install\Install-CanDoItAllWebApp.ps1 -StartAfterInstall

Do not treat this as a finished one-click installer

The agent must inspect prerequisites and remain responsible for the database and health checks. The app installs under %LOCALAPPDATA%\CanDoItAll\WebApp and uses a dedicated PostgreSQL backend through a working Linux Docker engine or the documented per-user PostgreSQL 16 path.

The installed app opens at http://127.0.0.1:38473/ after it becomes healthy.

Read the installer details

Prepared agent prompt · advanced

Make the target host and lifecycle explicit

Prepare a framework-dependent CanDoItAll public-alpha web host for this target operating system and architecture. Before changing the host, read the current installing-instances, headless-web-host, secure-configuration, and backup-and-restore documentation and ask me to confirm the target host, service identity, exposure boundary, database ownership, and backup expectations. In one source parent directory, clone or update only the main branches of https://github.com/fyziktom/CanDoItAll, https://github.com/fyziktom/CanDoItAll.Components, and https://github.com/fyziktom/CanDoItAll.FileTools using those exact sibling names. Preserve local changes, keep direct source project references enabled, record all three commit SHAs, and use the same recorded commits for restore and publish. Provision or connect PostgreSQL 16, explicit writable purpose roots, a stable host-binding ID, secret injection, certificate-backed Data Protection where required, service restart policy, and backup and rollback procedures. Publish the correct framework-dependent RID, install without silently elevating privileges, start the database and web service, and verify both /health and /api/runtime/operations on the actual host. Report the source commits, artifact, runtime profile, service status, data roots, database state, URL, and tested lifecycle commands. Retain the repository's ActualHostUnverified status for macOS headless targets until accepted actual-host evidence exists. Ask before administrator access, service registration, network exposure, secret changes, or replacing or removing any application or database data.

Read the deployment models

Next · 02

The app is healthy — make it yours

Configure workspace storage, secrets, AI providers, model prices, agents, and your first project only after the selected runtime and database checks pass.

Configure the app

CanDoItAll. Now runs where you do