One of the advantages of coding in the cloud with Codenvy is deploying to a PaaS of choice once the app has been built, run and tested in Codenvy. Users do not need to install any plugins or administer their workspaces in any way. Codenvy talks to API of most popular PaaS providers. Currently, the following PaaS are supported:
- AWS Elastic Beanstalk
- Google App Engine
- ManyMo (to run Android apps)
The mechanism of deploying, updating and configuring apps slightly differs depending on the chosen PaaS provider. To be able to deploy to a PaaS authentication is required (Login or Switch Account in PaaS menus). Codenvy will handle connection to a PaaS account, retrieving information on existing apps and providing tools to manage them.
Some providers will require deploy of SSH keys and git operations to update the apps (Heroku, OpenShift), while others (GAE, AWS) make it possible to update apps in one click.
When deploying an application, it is created in Codenvy and then deployed to a PaaS. OpenShift is an exception from this rule – the application is created there and then pulled to a Codenvy workspace.
It is possible to import existing apps deployed to some PaaS (Heroku) or overwrite existing applications (Google App Engine).
You can find detailed how-to guides on how to get started with PaaS in Codenvy in a PaaS menu on the left sidebar. Check out PaaS support chart:
|PaaS||Languages||Features||Cloud SDK Run|
EC2 and S3 console
|Java, PHP, Python, Ruby||Manage applications||No|
|Java, Ruby||Manage applications||Yes - Micro Cloud Foundry|
PHP (app IDs need to be whitelisted at GAE)
|Application management, Logs, Indexes, Pagespeed, Queues, DoS, Resource Limits, Crons, Backends||Yes|
|Java, PHP, Ruby, Python, Node.js||Manage applications||No|
|Java, Ruby||Manage applications||No|