Configure Application Settings
Manage and update your application configuration after creation. All settings can be modified and will take effect after redeployment.
Accessing Settings
To access application settings:
- 1
Go to Applications in the dashboard
- 2
Click on the application you want to configure
- 3
Navigate to the Settings tab
- 4
Click "Edit" to modify settings
Configurable Settings
Repository
Change the repository or branch your application uses. Useful when you want to switch between development and production branches.
Note: Changing repository will trigger a new build and deployment. Make sure the new repository has a compatible Dockerfile.
Deployment Package
Upgrade or downgrade your package to change CPU and Memory allocations. This affects performance and cost.
When to change package:
- • Upgrade: If your app needs more CPU/Memory (handling more traffic, processing larger data)
- • Downgrade: To reduce costs if your app is underutilized
- • Monitor: Check Resource Usage charts to see if you're hitting limits
Package changes require redeployment. Existing pods will be gracefully terminated and new pods with updated resources will be created.
Min & Max Pods
Adjust auto-scaling parameters based on your traffic patterns.
Min Pods Strategy
- • 0 pods: Scale to zero when idle (save costs, cold start delay)
- • 1 pod: Always available (recommended for production)
- • 2+ pods: High availability, load distribution
Max Pods Strategy
- • Low traffic: Max 2-3 pods
- • Medium traffic: Max 5-10 pods
- • High traffic: Max 20+ pods (or unlimited)
Container Port
Update the port if you've changed your application to listen on a different port.
Important: The container port must match the port your application listens on. Check your Dockerfile's EXPOSE directive.
Custom Domain
Add or change your custom domain. ScallerFox automatically provisions SSL certificates.
DNS Configuration:
- Add a CNAME record in your DNS provider
- Point it to ScallerFox's load balancer (provided after domain setup)
- Wait for DNS propagation (usually 5-30 minutes)
- SSL certificate will be automatically issued
Environment Variables
Manage environment variables that are injected into your containers at runtime.
Operations:
- • Add: Add new environment variables
- • Edit: Update existing variable values
- • Delete: Remove environment variables
Environment variable changes require a redeployment to take effect. Existing containers will continue using old values until redeployed.
Saving Changes
After editing settings, click "Save" to persist your changes. You'll be prompted to redeploy your application.
Deployment Required: Most configuration changes require a redeployment to take effect. Click "Deploy Now" after saving to apply changes immediately, or deploy later from the Deployment tab.