ActoEngine captures what documentation can't: the "why" behind your database.

What if your database could explain itself?

ActoEngine builds a semantic layer that answers the questions your documentation doesn’t: “What breaks if I change this?” “Why does this exist?”

It maps hidden relationships, detects drift between reality and documentation, and simulates change impact before you deploy. The Form Builder and SP Generator aren’t just code tools — they’re proof that when systems understand their own context, automation becomes intelligent.

• Semantic Context: Document the "why" behind database entities with drift detection.
• Impact Analysis: Visualize dependencies and simulate change impact before deployment.
• Smart Automation: Generate Stored Procedures and Forms using schema context.
• Entity Explorer: Unified browsing for tables, SPs, views, and functions.
• RBAC & Security: Fine-grained permissions, audit logging, and secure authentication.

Backend: .NET 8.0, ASP.NET Core, Dapper, SQL Server/Postgres
Frontend: React 18, TypeScript, Vite, TanStack Query, Shadcn UI
Infrastructure: Docker, Nginx, JWT

The fastest way to get ActoEngine running is using Docker Compose.

1. Create Secret Files (passwords stored securely):

   # Create secrets directory if not exists
   mkdir -p secrets
   
   # Create password files (no trailing newline)
   echo -n "YourStrong@Passw0rd" > secrets/SA_PASSWORD
   echo -n "YourAppPassword123!" > secrets/DB_PASSWORD

2. Configure Environment: Edit Backend/.env:

   DB_NAME=ActoEngine
   SEED_ADMIN_PASSWORD=Admin@123

3. Launch:

   docker-compose up --build

4. Access:

   • Web UI: http://localhost:3000
   • API Docs: http://localhost:5093/swagger
   • Default Login: admin / (value of SEED_ADMIN_PASSWORD)

If you encounter issues running Docker on Windows, here are common problems and solutions:

Symptom: db-init container fails with errors like:

/scripts/init-db.sh: line 2: set: -: invalid option
/scripts/init-db.sh: line 3: $'\r': command not found

Cause: Windows uses CRLF (\r\n) line endings, but Linux containers expect LF (\n).

Fix: Convert init-db.sh to LF line endings:

# PowerShell: Remove carriage returns
$content = [System.IO.File]::ReadAllText("Backend\Infrastructure\Database\init-db.sh")
$content = $content -replace "`r", ""
[System.IO.File]::WriteAllText("Backend\Infrastructure\Database\init-db.sh", $content)

Prevention: Add .gitattributes to your repo:

*.sh text eol=lf

Symptom: Backend fails with Login failed for user 'app_user' or Login failed for user 'sa'.

Cause: Secret files created on Windows may have UTF-16 encoding with BOM, causing null bytes in passwords.

Fix: Recreate secrets with UTF-8 encoding (no BOM):

[System.IO.File]::WriteAllText("secrets\SA_PASSWORD", "YourStrong@Passw0rd", [System.Text.UTF8Encoding]::new($false))
[System.IO.File]::WriteAllText("secrets\DB_PASSWORD", "YourAppPassword123!", [System.Text.UTF8Encoding]::new($false))

Then restart Docker:

docker compose down -v
docker compose up --build

For local development without Docker, please refer to the Development Guide.

Contributions are welcome! This project is licensed under the MIT License.