| tag | f4aa33a0f977671733c5089fac16d90383be1efd | |
|---|---|---|
| tagger | Todd Nine <tnine@apigee.com> | Tue Mar 04 10:44:33 2014 -0700 |
| object | 754aa1f525aebac624fa12068da8b988d11b347e |
| commit | 754aa1f525aebac624fa12068da8b988d11b347e | [log] [tgz] |
|---|---|---|
| author | Dave Johnson <dave.johnson@rollerweblogger.org> | Mon Mar 03 21:27:45 2014 -0500 |
| committer | Dave Johnson <dave.johnson@rollerweblogger.org> | Mon Mar 03 21:27:45 2014 -0500 |
| tree | fd4fce71945a595ba1ec8f682f32bf4fa6ae8368 | |
| parent | 2891b5483696b4414ce301e4c202f0ef253b021c [diff] | |
| parent | 65064baf4551ccbec49c5ded9dad320c639d9a6b [diff] |
Merge pull request #68 from usergrid/applimitfix Removed 10 app limit
Apache Usergrid is a multi-tenant Backend-as-a-Service stack for web & mobile applications, based on RESTful APIs. It is currently incubating at the Apache Software Foundation.
This repository contains all the code for Apache Usergrid, including the server stack, portal, client and SDKs. Each of them have their own, much more detailed README in the corresponding subdirectories.
/stack. You can install dependencies and compile it with maven. See stack/README.md for instructions./ugc. You can install it on your machine with a simple sudo gem install ugc/portal/sdks.It‘s easy to build and run Usergrid locally. All you need is the Java JDK 1.7 and Maven 3.0.5 installed and on your path. Here’s how you do it. First you get the source code like this:
git clone git@github.com:usergrid/usergrid.git
Next, you change directories into the Java SDK package and build the SDK:
cd usergrid/sdks/java mvn clean install
Next, you change directory into the stack directory and build the Usergrid WAR and launcher:
cd ../.. cd stack mvn clean install
Finally, you can run Usergrid locally by using the all-in-one launcher, which includes a web server (Grizzly) and the database (Cassandra):
cd launcher java -jar target/usergrid-launcher-0.0.29-SNAPSHOT.jar
(you might have to substitute 0.0.29-SNAPSHOT with something newer)
You should see the Usergrid launcher UI and from there you can start Usergrid and access the admin console.
If not, subscribe to the user mailing list and we can help you out.
If you previously developed with Apache Usergrid, you know our code used to be structured into separate repositories: usergrid-stack, usergrid-portal, etc. We are now using a merged repository.
You just need to clone this repository, and use git subtree (usually requires git 1.8+) to merge your changes under the new structure. Here’s an example for a portal fork. Adjust the prefix, repository address and branch you want to pull from as necessary.
git clone git@github.com:usergrid/usergrid.git cd usergrid git subtree pull --prefix=portal git@github.com:my-github-account/my-usergrid-portal-fork.git master
This will pull (i.e. merge) the changes you made from the master branch of github.com/my-github-account/my-usergrid-portal-fork into the portal/ subfolder. It should ask you to provide a commit message for the merge. There’s lot of flexibility on how to fetch and merge, please see the git subtree manual for details. Then please do consider sending us a pull request with these changes ;)
You should really update your old repositories to the new structure with the instructions above, but the following may work for you, although we make no guarantee they will work in the future.
You can produce a branch compatible with the old repos by using git subtree (usually requires git 1.8+). Then from this repository you can
git clone git@github.com:usergrid/usergrid.git cd usergrid git checkout master git subtree split --prefix=portal -b portal git checkout portal
This will create a “portal” branch that is compatible with the old usergrid-portal repository, from the code under the portal/ directory. You can pull from that branch (or push changes to it, although we will not accept pull requests sent thusly).
The git subtree split above should function for portal, ugc, and any of the SDKs, but will not work for the stack, due to some anonymous comments left in the tree that prevent a split, and cannot be corrected lest we break the history and force a rebase on all forks.
Please update your code setup as soon as possible and ask the dev list if you have any questions!