- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Externalizing AppSync URL?
In our deployment model, we build ThinApp packages at our company and then deploy them out to different servers at customer intranet sites. We have been able to leverage the ThinApp scripting capability to externalize basically any file in the package. This allows us to build 1 core package, deploy it at multiple customer sites, and then just change any .config files outside of the package for each customer. This greatly simplifies the management of our packages, since we just need to build one version of the package and then can configure it per customer via configuration files.
We have been experimenting with the AppSync capability, and have found that it would be especially useful to externalize the AppSync URL in much the same way we can with our configuration files. This would open many doors for us in terms of flexible deployments. Namely, we could create a package at our company, test it internally by pointing to a local web server, then stage that package out to a customer site, and just update the AppSync URL to point to their customer web server. Another common scenario is that we will deploy a ThinApp package into a customer test environment, and then need to push the same package into the customer's live environment. We would like to be able to move the package from the test web server to the live web server, and just update the AppSync URL in the live environment to point to the live web server.
Is it possible to do this today with ThinApp? If this needs to be a feature request, where do I post it?