Skip to content

DigitalOcean

DigitalOcean App Platform can build and run a web app from a Git repository or a compatible container image. Check that it starts correctly and know where any saved records will live.

Visit DigitalOcean

How does DigitalOcean App Platform know what to run?

App Platform can build an app from a supported Git repository or run a compatible container image. It can infer some build settings from the project, or use a Dockerfile that describes how to build it. Confirm which source branch, build command and run command you expect it to use.

Choose a web service when a running app needs to answer requests. A static component serves prepared files. The service’s HTTP port and health check need to match the process it will run.

Can the app be healthy and still show the wrong release?

Yes. A health check can pass while the page still shows an old value. Rehearse with a fake repair-shop notice on paper or in a disposable local project. Before running it, confirm the local address, test settings and disconnection from live records, credentials, payments and messages. Stay on paper if you cannot verify the setup.

  1. Write down which source should go out
    In version A, have the notice say “Drop off at the side door”. Keep a record of the version, the command that builds it and the command that starts the app.
  2. Check the visible change as well as health
    Change version B’s notice to “Drop off at the front desk”. With local copies, use the matching build and start steps. Stop the earlier copy if both use the same local address. Open the notice and its health path separately. A healthy response with the side-door instruction fails this release check.
  3. Check what a return to version A would bring back
    Run the recorded version A again locally or trace it on paper. Confirm it brings back the side-door instruction. List any data you would need to recover separately in a real app.

What can App Platform roll back after a bad deployment?

You can select one of the ten most recent successful deployments when the Region and database resources and configuration still match. The rollback restores the app code, configuration and app spec. Database data has a separate restore process.

An app spec is the description of how to run the app. For a later hosted rehearsal, use a distinct test app with its own source branch, settings and data. Treat its address as reachable until you have verified its access controls. Check exactly which source version reaches that address before testing.

What does an App Platform service cost as the app grows?

App Platform lists a monthly rate for each web service container size and prorates the charge by the second, with a one-minute minimum. Check how many components and copies you run. The static-only allowance applies to apps made entirely of static components.

Costs to estimate separately
PartWhat can change the bill
Web processThe size and number of components or copies. Include any separate test app that runs a web service.
Data transferThe plan contributes an outbound allowance. DigitalOcean pools that allowance at the team level and charges for excess outbound use.
Saved records and filesApp Platform bills databases by the hour, with a one-hour minimum. External file storage has its own pricing. Check the actual service and its backup options.

What should you back up outside App Platform?

Use durable storage for records and uploads. Treat the app’s local filesystem as temporary. Files saved there can disappear when the container is replaced.

Keep the source and build instructions, app spec and names of the settings needed to run it again. Protect secret values separately. A development database has no managed backup. Check the backup and restore coverage for the database you will use with real records.

Before trying a restore, verify an isolated destination, test-only credentials and a sample backup. Open a test record and a sample uploaded file after recovery. Check both again after a restart or replacement.