How to put your first app online without managing a server
Move from localhost to an HTTPS URL: prepare your project, check its services, choose a pod and verify the first deployment.
Simple answers to help you launch your app, keep your data and understand what's happening.
Move from localhost to an HTTPS URL: prepare your project, check its services, choose a pod and verify the first deployment.
Understand the App Cities pod: an isolated home for your Docker services, not an empty VPS or a database you have to buy separately.
Learn what services, images, builds, variables and volumes mean in a Compose file before uploading a project.
Avoid localhost and CORS mistakes by separating browser URLs from private Docker service addresses.
Plan database connections, persistent storage, initialization and recovery before deploying an app with real data.
Diagnose connection refused errors by identifying which container or browser a localhost address refers to.
Understand image building versus service orchestration, and when a single Dockerfile is enough for a deployment.
Separate public configuration from private credentials and keep secrets out of uploads, images, logs and AI chats.
Understand named volumes, database paths and the difference between restarting a service and protecting data.
Find the first useful error, separate build failures from runtime failures and give your AI a focused debugging request.
Choose Base, M, L or XL by what your app needs, then check its RAM and CPU use with real tasks.
Connect your AI to App Cities, prepare a project and keep control of spending and changes.
Make a clean project archive with the code and build files, without dependencies, secrets or local clutter.
Check more than a running container before sharing your app's HTTPS link.
Plan updates without confusing an older app version with a restored database.
Use the platform's DNS instructions, verify ownership and test the finished HTTPS address.
Make a simple recovery plan for your app files, database and settings, then test it away from production.
Understand your balance, pod usage, spending approval and what happens when credits run out.
Understand why install scripts and Docker builds must be isolated, timed and limited before code reaches a pod.
Check access, data, costs, email, HTTPS and recovery before inviting your first real users.