When changes require redeployment

2 min read Updated 21 hours ago

When changes require redeployment

Some configuration changes to your application require a new deployment to take effect, while others are applied immediately. Understanding which changes require redeployment helps you plan updates more effectively.

Changes that require redeployment

The following changes will mark your application as needing deployment:

Build and initialization

  • Build commands - Changes to commands that run during image building
  • Init commands - Changes to commands that run before your application starts
  • PHP configuration - PHP version, extensions, or php.ini settings
  • Node.js version - Changing or enabling Node.js runtime

Environment and secrets

  • Environment variables - Adding, updating, or removing secrets
  • Custom domains - Adding or removing domains

Resources and scaling

  • CPU requests - Changing CPU resource allocation
  • Memory requests - Changing memory resource allocation
  • Replicas - Changing the number of application instances
  • Scheduler - Enabling or disabling the Laravel scheduler (cron)

Services and storage

  • Services - Adding or removing database, cache, or other services
  • Volume mounts - Adding or modifying persistent storage paths

Application settings

  • Application name - Renaming your application
  • Special configurations - Platform-specific fixes or adjustments

Changes applied immediately

These changes take effect without requiring a deployment:

  • Repository settings - Changing repository URL, owner, name, or default branch
  • Health check path - Updating the health check endpoint (for monitoring only)
  • Service restarts - Restarting a service applies immediately
  • Debug access - Enabling or disabling temporary service access

How to deploy changes

When your application needs deployment:

  1. You'll see a notification banner at the top of your application page

  2. Click the Deploy now button to start the deployment

  3. The deployment will build a new image with your changes and update your application

  4. Your application remains available during deployment with zero downtime

Dismissing deployment notifications

If you've made changes but don't want to deploy yet, you can dismiss the notification. However, the changes won't take effect until you deploy. The notification can be dismissed through the API or by clicking the dismiss button in the interface.

Best practices

  • Group multiple configuration changes together to minimize deployments

  • Test changes in a staging environment first

  • Deploy during low-traffic periods when possible

  • Monitor your application after deployment to ensure changes work as expected