- Who is this for?
- Mobile application and backend teams.
- Before you start
- An owned staging environment, sample user journey and access model.
1. Understand the current scope
The public site and guides are open. New registration and customer allocation are closed on the live site. Local development preview can store project and service definitions, but it does not execute code or create real databases or domains. The console steps below apply to that local preview.
2. Define the project boundary
A project brings services for one application together. Use a readable name, unique address and a clear development / production environment choice. A mobile API and its database may belong to one project; keep separate customers apart.
3. Separate application and database
An app service receives HTTP while a database service stores SQL data. Node.js, Laravel, Python or Docker refers to backend code. MySQL / PostgreSQL refers to the data model. Separate responsibilities rather than forcing every need into one process.
4. Prepare environment values
Keys and values are entered separately in the service screen. Values are encrypted; lists show keys and a masked representation. Document the variables your app needs. Never use example values as real passwords or commit secrets to Git.
APP_ENV=development
# Keep secret values such as DATABASE_URL outside the repository.5. Interpret release states correctly
The local provider simulates queues and service lifecycle. Pending or ready does not prove a real server exists; logs identify simulation explicitly. Application URLs, IP addresses and SQL passwords are not offered before live allocation opens.
6. Plan domains and files
A domain record does not establish DNS ownership or create a TLS certificate. Local console records may remain pending. The object storage provider is also unconnected. Plan persistent files, authorization and deletion rules in your application design.
7. Validate before a real release
Test the start command, port, health check and access rules. Clarify database backups and restoration with your provider. Keep passwords and session details out of logs. A functioning screen does not prove the entire operational infrastructure is ready.
8. Choose the next guide
Use the matching product page for runtime preparation. Continue to the private database guide for the boundary between clients and SQL. Status and pricing pages explain the current live-service scope.
7. Inventory environments and secrets
Keep development, staging and production connections distinct. Do not mix fixtures with customer records. Store server configuration outside application source and never treat a mobile-bundled secret as confidential. Record where keys are used and which services need a restart after rotation.
Describe API, SQL, worker and storage ownership. Naming a service does not deploy a runtime: DNS/TLS, health checks and recovery remain separate steps.
| Service | Role | Check |
|---|---|---|
| API | HTTP and business rules | Permissions / timeout |
| SQL | Persistent data | Private access / restore |
| Worker | Long tasks | Retry / idempotency |
| Storage | User objects | Ownership / retention |
8. Define a first release journey
Exercise sign-in, list, creation, upload, logout and a fresh session. Add invalid-session and cross-user cases. Disconnect foreground and background clients. Loading must not remain stuck indefinitely.
- Local preview does not open real customer resources.
- Test your own staging contract.
- Trace failures with safe request identifiers.
- Retain the previous configuration for rollback.
Action summary
- Inventory environments and secrets
- Define a first release journey
Common questions
Does this enable live Uygulama Cloud resources?
No. Customer provisioning is closed; adapt the architectural examples to your environment.
What counts as validation?
Verified data, permissions and failure cases for your workload, rather than one successful screen or a backup file.
Sources and scope
Technical references are listed below. Examples illustrate implementation in your own environment; they are not customer benchmarks or claims of live Uygulama Cloud services. Check the current provider documentation before applying settings.
Sources checked: