SyncApp Deployment — Using the Deploy UI (Part 1)
Why This Matters
Shipping your code to a real SyncApp instance is the final step in every development cycle. Understanding the Deploy UI and the deploy-then-update flow is essential for testing your changes on real offices.
What You'll Learn
- What the SyncApp Deploy UI is and how to access it (prod and dev URLs provided in KT notes)
- The two deployment tabs: Main (merged changes) and Branch (in-progress development)
- The three deploy target options: All (all sync apps), By PMS ID, By Source ID
- The OS + architecture combinations: Linux/AMD64 for cloud PMSs, Windows/386 for on-prem PMSs
- The deploy → update sequence: deploying pushes a new version tag; clicking Update triggers the actual restart
Watch Video
Lesson Summary
The SyncApp Deploy UI (accessible via direct URLs — no port forwarding needed) shows all available builds organized by main branch tags and feature branches. Select a tag, choose the OS/architecture (Linux+AMD64 for cloud, Windows+386 for on-prem), and deploy target (specific source ID for testing, All for production releases). Clicking OK deploys the version tag to the SyncApp's configuration. To load the new version immediately, click Update — this triggers a restart/reload. Without Update, the SyncApp will self-update within 14 hours via its built-in cron job.