We’re excited to announce the release of Targeted Deploy, a major enhancement to the deployment process in Appfarm Create. This feature is available now for customers on the Essential tier and above.
What is Targeted Deploy?
Targeted Deploy enables you to deploy specific apps, services, themes, and schedules to any environment—without waiting for other in-progress work. This gives you unprecedented control over what gets deployed and when, streamlining your development workflow and making it easier to ship changes faster.
Key benefits
Deploy what you want, when you want
With Targeted Deploy, you choose exactly what you want to deploy. Need to push just that one app you’ve been working on? No problem. Want to deploy directly to Production? You can do that too.
Work independently within the same Solution
No more coordinating deploys with your team. Each developer can work on and deploy their changes without affecting others’ work in progress. This means faster development cycles and fewer “is it OK to deploy?” messages.
Smarter dependency handling
Appfarm automatically identifies and includes any dependencies your selected components need. If your app requires data model changes, they’ll be bundled in automatically.
How it works
When you click the Deploy button, you’ll now see additional options:
- Choose between “All changes from [Environment]” or “Selected changes from [Environment]”
- If selecting specific changes, check the apps, services, themes, and schedules you want to deploy
- Choose your target environment (Test, Staging, or Production)
- Deploy instantly or schedule for later
Appfarm automatically checks for dependencies to ensure everything needed for your selected changes is included in the deployment.
Getting started
Targeted Deploy is available now for all customers on the Essential tier and above. Simply click the Deploy button in Appfarm Create to see the new options.
Check out the documentation for more details on how to use this feature.
We’d love to hear about your experience with Targeted Deploy. How is it going to change your deployment workflow? Please share your thoughts and feedback in the comments below!