 |
Concept : Understanding Application Posting and DeploymentFrom $1Table of contentsDescriptionWhen working in Bungee Builder, you work in your own work space. To enable others to collaborate on your solution, you must first create a DesignGroup and invite others to your DesignGroup. This allows each of you to separately check in and check out different parts of a solution. When you want to deploy an application, you must post your solution to Production. Once your solution is posted, you can deploy your application. The general procedure to deploy an application is:
(See the "Hello Bungee Connect" tutorial in the Start Tab for step by step example) Currently, there are two models for deploying an application from Bungee Builder. Test (Free) DeploymentWhen you deploy an application with a Test Deployment, you are given a hard-coded URL in the Bungee Grid and there no charges are accrued. You may deploy in either HTTP or HTTS mode (if you choose HTTPS, Bungee takes care of the certificate for you). Test deployments have the following limitations:
Commercial (Full) Deployment to a Bungee URLCommercially deployed applications require you to establish a billing relationship with Bungee Labs. Deployed applications accrue Bungee Units and you are periodically billed at the current rate. Using this mode of deployment allows you to use HTTP or HTTPS. If you choose HTTPS however, you must provide your own certificates. You can direct users from your own or business Web site through a redirected URL. During Beta phase, deploying live Bungee powered apps is free to developers. Arbitrary URL in CName MappingDuring Bungee Connect's early Beta release, choosing to create a proprietary URL limits you to an HTTP deployment. See this blog post - How To: Use a Custom URL for Your Bungee powered apps. Deployment ArgumentsOnce you have deployed your application, you can easily add deployment arguments to customize your deployed application so that you can easily update a deployment without the need to create multiple deployments of the same application. Common UsesScenarios in which you might want to add deployment arguments might include an application that makes use of live data from a database. During design time (when simulating) you might have a "sandbox" database you access for testing purposes. You could then deploy your application, and add deployment arguments that direct your application to use the proper live database. Another example might include use of a web service requires that you use a different license key for testing as opposed to production use. Adding deployment arguments with the proper runtime key makes your application very configurable. Working with Deployment ArgumentsIn order to make deployment arguments useful, you must also make use of the AppGlobal functionality. In order to do this, you need to add a call function statement, then set the site to AppGlobal. Then, click the ellipsis button [...] and select the getState function. The arguments to getState are key and value. The key is the key you need to give your deployment arguments, and value, is whatever string you enter in the value deployment argument. See AlsoPosting, Sharing, Deploying, and Managing your Applications Blog Post: How To: Use a Customer URL for Your Bungee powered apps Tags
Tags:
|