Projects & Environments

This page documents the current implementation, not the older idealized flow.

Today, A8S is organized around:

Monolithic projects
Microservice projects
Database deployments

Current Create Flow

Choose an Architecture First

From New Project, the first screen asks you to choose:

Monolithic
Microservice
Database

Follow the Matching Path

Each architecture goes to its own setup experience:

Monolithic uses the repository import/config flow
Microservice uses repository selection plus service setup
Database uses the database provisioning flow

Continue into the Workspace

After creation, each item becomes manageable from the workspace detail pages and dashboard lists.

The current app does not use one universal “connect repository or upload archive” project wizard. It branches by architecture first.

Monolithic Projects

Monolithic projects are the most complete app-project flow today.

Current backend and frontend behavior includes:

repository connection
project detail retrieval
custom domain set and sync
environment/config update
.env import support
auto-deploy toggle
webhook create, rotate, fetch, and delete
manual sync
release history
rollback
delete

This makes monolith the clearest “full app lifecycle” path in the current product.

Microservice Projects

Microservice projects currently focus on repository-driven setup and live project management.

Current behavior includes:

repository selection through GitHub or GitLab
service-oriented setup flow
project detail retrieval
domain updates
readiness checks
delete

The current product surface is more focused on project structure and delivery orchestration than on a full per-service environment editor.

Database Deployments

Database deployments are created through the dedicated database setup flow and are grouped into project-style views in the frontend.

The current self-service database flow supports:

PostgreSQL
MySQL
MongoDB
Redis
Cassandra
Oracle Database
Microsoft SQL Server

Current database capabilities include:

asynchronous provisioning
generated connection profile
credential retrieval
built-in browser database console
backup settings
manual backup
restore
download
delete

The database setup screen shows both Single instance and Cluster modes, but in the current frontend the Cluster option is not available for self-service creation yet.

Workspace Sections That Exist Today

For app projects, the current detail page sections are:

Section	What it currently covers
Deployments	Live deployment/runtime summaries
Logs	Project log surface
Analytics	Project summary and analytics-style cards
Domains	Domain and routing management
Settings	Project settings surface

There is not currently a dedicated shared Environments tab or Secrets tab in the main project workspace UI.

Environment Configuration Today

The current product still has configuration and runtime settings, but they are not exposed as one generic dev / staging / production editor across every project type.

What is real today:

monolith projects store runtime configuration through their project APIs
.env import exists in the monolith flow
database deployments store their own engine-specific connection and backup settings
project settings in the frontend are still partially local/mock until a fuller backend settings API is finished

The current frontend settings screen even states that some project settings are mocked locally until the backend settings API is ready, so avoid documenting that area as fully server-backed.