Getting Started
Quick Start Guides
- Amazon Web Services
- Elastic Block Store Models
- Azure Storage Service
- BlueLock vCloud
- Cloud Sigma
- Eucalyptus
- File System
- Go Grid
- HP Cloud Services
- IBM Developer Cloud
- OpenStack
- Rackspace
- RimuHosting
- Terremark eCloud
- Terremark vCloud Express
Release Notes
- 1.5.0-alpha.6
- 1.5.0-alpha.5
- 1.5.0-alpha.4
- 1.5.0-alpha.3
- 1.5.0-alpha.2
- 1.5.0-alpha.1
- 1.4.0
- 1.4.0-rc.3
- 1.4.0-rc.2
- 1.4.0-rc.1
- 1.3.1
- 1.3.0
- 1.3.0-rc-2
- 1.3.0-rc-1
- 1.2.2
- 1.2.1
- 1.2.0
- 1.1.1
- 1.1.0
Maven Sites and Javadocs
- HEAD (Javadoc)
- latest release (Javadoc) permalink
- 1.5.0-alpha.6 (Javadoc)
- 1.5.0-alpha.5 (Javadoc)
- 1.5.0-alpha.4 (Javadoc)
- 1.5.0-alpha.3 (Javadoc)
- 1.5.0-alpha.2 (Javadoc)
- 1.5.0-alpha.1 (Javadoc)
- 1.4.0 (Javadoc)
- 1.4.0-rc.3 (Javadoc)
- 1.4.0-rc.2 (Javadoc)
- 1.4.0-rc.1 (Javadoc)
- 1.3.1 (Javadoc)
- 1.3.0 (Javadoc)
- 1.3.0-rc-2 (Javadoc)
- 1.3.0-rc-1 (Javadoc)
- 1.2.2 (Javadoc)
- 1.2.1 (Javadoc)
- 1.2.0 (Javadoc)
- 1.1.1 (Javadoc)
- 1.1.0 (Javadoc)
User Guides
- Using Blob Store API
- Using Compute API and Tools
- Google App Engine
- VMWare vCloud
- Terremark
- File System Provider
- Init Builder
- Using jclouds with Apache Karaf
- Using EC2
- Using Maven
Samples & Examples
FAQs
Reference
- jclouds Rationale and Design
- Location Metadata Design
- Compute API Design
- Columnar Data Design
- jclouds API
- jclouds OAuth Integration
- Using jclouds with Apache Felix OSGi Container
- Pool Design
- Load Balancer Design
- Logging in jclouds
- VMWare Integration Approach & Design
- Supported Providers
- Apps that use jclouds
- Using Provider Metadata
Developer Resources
- Contributing to jclouds
- Provider Testing
- Contributing to Documentation
- Using Eclipse
- jclouds Continuous Integration
- Provider Metadata
Old versions
Release Notes
- 1.0.0
- 1.0 Beta 8
- 1.0 Beta 7
Maven Sites and Javadocs
How to contribute to jClouds Documentation
The complete jclouds website (and documentation) is now served from github, and the code for the same is available the git repository
This site is rebuilt and updated whenever a new commit is pushed to the repository.
This makes it extremely easy for accepting the contributions to the documentation as well using the standard github fork/commit/pull-req based workflow.
To change or contribute to the documentation:
- Just fork, clone the repository & Update the source markdown [you can even use textile, if it is easier, more details on this below].
- Commit and push to your fork.
- Send in a pull-req so a core contributor will pull the changes and push them to the site.
More about the site:
As indicated above, the site is built using github pages which uses Jekyll, a static site generator written in Ruby, under the covers. To preview any changes you make, install Jekyll (from here, with Pygments too) then run jekyll -pygments --safe --server and open localhost:4000 in the browser.
The site structure is pretty simple as you can see in the source of this site. The _layouts folder contains the docs.html file which is used as the layout - containing main column and the sidebar. The sidebar is an include which is inside the _includes folder.
(Due a bug the sidebar can't be a markdown file, but this will be changed as soon as the bug is fixed. Also when running in the jekyll server, links without the .html are not resolved, and you'll have to manually append .html to some links; this runs fine on the server, so don't worry about it; however if you know a better way please let us know!)
Each folder under the documentation contains an index.markdown that will list all the pages that belong to this "section". You can even edit the pages directly on github if you don't want to clone the repo into your computer.
Please take a look at the site jclouds.org and let us know if we missed anything from the documentation, feel free to fork/contribute or open a bug on the issue tracker We'll be glad to fix them ASAP.