Skip to main content

Documentation Index

Fetch the complete documentation index at: https://archie.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

System services are built-in capabilities your app uses — authentication, file storage, role management, email verification. This page covers how to edit them.

​
What is available

Archie ships with these system services:
  • Authentication providers — API key, AWS Cognito, Google OAuth, OAuth2, Apache Shiro
  • File storage — Azure Blob Storage, Filestack, Google Cloud Storage
  • Roles — fine-grained role definitions tied to user types
  • Email verification — verify user emails on signup
The system services card on the blueprint shows which services are selected and their key configuration.

​
Choosing an authentication provider

Open the System services card and select an auth provider. Each provider has its own configuration:
  • API key — header name and validation URL
  • AWS Cognito — user pool ID, region, identity pool ID
  • Google OAuth — client ID, redirect URI, hosted domain (optional), scopes
  • OAuth2 — authorization URL, token URL, user info URL, scopes
  • Apache Shiro — realm class, authentication strategy, session timeouts
Pick the one that matches your existing identity infrastructure. If you do not have one, the default provider is the simplest path.

​
Choosing a file storage provider

For apps that handle uploads, pick a storage backend:
  • Azure Blob Storage — container name, account name, access key
  • Filestack — bucket name and Filestack credentials
  • Google Cloud Storage — bucket name, GCP project ID, service credentials JSON
Configuration happens after the build in App settings → File storage. The blueprint just sets the backend choice.

​
Adding or removing services

Some services are required (authentication). Others (file storage, email verification) are optional. Toggle them on or off from the System services card.

​
FAQ

Yes, but it is nontrivial — you will need to migrate existing user records. Choose the right provider during blueprint editing if you can.
No. The blueprint just specifies which provider you will use. Add credentials in App settings after the build.
Yes. The OAuth2 provider lets you integrate any standards-compliant identity provider.