Documentation
EU Aptible Isolation Setup
Project-Agent / arxsec-api/EU_APTIBLE_SETUP.md
This repo now supports split Aptible deployments for US and EU environments.
Required GitHub Secrets
US
APTIBLE_US_USERNAMEAPTIBLE_US_PASSWORDAPTIBLE_US_ENVIRONMENTAPTIBLE_US_API_APPAPTIBLE_US_FRONTEND_APPNEXT_PUBLIC_SUPABASE_URL_USNEXT_PUBLIC_SUPABASE_ANON_KEY_USNEXT_PUBLIC_API_URL_US
EU
APTIBLE_EU_USERNAMEAPTIBLE_EU_PASSWORDAPTIBLE_EU_ENVIRONMENTAPTIBLE_EU_API_APPAPTIBLE_EU_FRONTEND_APPNEXT_PUBLIC_SUPABASE_URL_EUNEXT_PUBLIC_SUPABASE_ANON_KEY_EUNEXT_PUBLIC_API_URL_EU
Deploy Behavior
- Pushes to
maindeploy the US stack by default. - EU deploys run via manual workflow dispatch with
region=eu(orall).
Runtime Configuration
Set these API env vars per deployment:
APTIBLE_DEFAULT_REGION(usoreu)APTIBLE_US_ENVIRONMENT,APTIBLE_US_API_APP,APTIBLE_US_FRONTEND_APPAPTIBLE_EU_ENVIRONMENT,APTIBLE_EU_API_APP,APTIBLE_EU_FRONTEND_APPARXSEC_API_URL_US,ARXSEC_API_URL_EUARXSEC_APP_URL_US,ARXSEC_APP_URL_EU
Tenant Routing Guidance
Use app/core/tenant_region.py to resolve tenant region from org attributes:
- explicit
region/data_region - fallback inferred from
country_code - fallback to
APTIBLE_DEFAULT_REGION
Requests for EU tenants should be routed only to EU API/frontend domains. The auth layer now enforces host-region affinity when ARXSEC_API_URL_US/EU are configured.