Difference between revisions of "Collaborative Development Configurations"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
| Line 8: | Line 8: | ||
production instances. With that architecture, collaboration is achieved by sharing the [[Metadata Repository]] using a Version Control System like Subversion. | production instances. With that architecture, collaboration is achieved by sharing the [[Metadata Repository]] using a Version Control System like Subversion. | ||
:''Learn more:'' [[Service Provider Settings#Instance Configuration]] | :''Learn more:'' [[Service Provider Settings#Instance Configuration|Instance Configuration]] | ||
==Develop in the Cloud== | ==Develop in the Cloud== | ||
--> | --> | ||
Tenants are created, and their IDs listed in the [[Service Provider Settings#Tenant Configuration]]. | Tenants are created, and their IDs listed in the [[Service Provider Settings#Tenant Configuration|Tenant Configuration]]. | ||
Those tenancies then become [[Development Tenancy|Development Tenancies]]. With that architecture, collaboration is achieved by publishing and subscribing to packages. | Those tenancies then become [[Development Tenancy|Development Tenancies]]. With that architecture, collaboration is achieved by publishing and subscribing to packages. | ||
Revision as of 21:28, 24 July 2012
Any tenant can develop new applications and customize existing ones. Service Providers have additional capabilities, designed to allow for collaborative development, testing, and production deployment in the cloud Tenants are created, and their IDs listed in the Tenant Configuration. Those tenancies then become Development Tenancies. With that architecture, collaboration is achieved by publishing and subscribing to packages.
- Learn more:
- Service Provider Settings#Tenant Configuration
- Read the Collaborative Development Models whitepaper.