Concept : Understanding Application Posting and Deployment
Contents |
[edit] Description
When 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:
- Add an App Project to the solution.
- Add a page to the App Project.
- Set the Main Page for Application property (on the App Project).
- Open the App Project page
- Add the form you want embeded in the page (from the Solution Detail, open the class the form is in and drag and drop it into the page)
- Save the solution
- Check in the entire solution into the Depot.
- Post the application
- Deploy the application
- Add any needed Deployment Arguments
(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.
[edit] Test (Free) Deployment
When 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:
- Days Live—Applications deployed for free are only available for 15 days unless you confirm your email address with Bungee Labs. After your email address has been confirmed, your Free Deploy applications stay live for 60 days. After the time limit has expired, the application is disabled.
- Session Count—Applications deployed for free only allow a maximum of 5000 total user sessions. After the session threshold has been met, the application is disabled.
- Concurrency—Applications deployed for free only allow a maximum of 10 concurrent users. After the concurrency threshold has been met, the application sheds additional connection attempts. Once the number of concurrent users goes below 5, additional connection attempts are allowed until the concurrency threshold has been met again.
- Bungee Unit Count—Applications deployed for free only allow a maximum of 60,000 total Bungee Units. After the Bungee Unit threshold has been met, the application is disabled.
- Bandwidth—Applications deployed for free are rate limited to 500kb of transfer bandwidth.
- Storage—Applications deployed for free only allow a maximum of 500MB of storage in Bungee. After the storage threshold has been met, the application is disabled.
[edit] Commercial (Full) Deployment to a Bungee URL
Commercially 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.
[edit] Arbitrary URL in CName Mapping
During 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.
[edit] Deployment Arguments
Once 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.
[edit] Common Uses
Scenarios 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.
[edit] Working with Deployment Arguments
In 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.
[edit] See Also
Posting Your Application
Deploying Your Application
Managing a Deployed Application
Blog Post: How To: Use a Customer URL for Your Bungee powered apps