Tool to quickly manage permissions for an entire directory of Google Drive Files

This project uses Maven to manage dependencies. This allows us to specify the different libraries we need without having to manually download them all and add them to the git repository.

1. Make sure you have the "Ultimate Edition" of IntelliJ. The community edition does not include the Google App Engine plugin. You can register as a student at https://www.jetbrains.com/student/
2. Check out the project using GitHub. Go to VCS > Checkout from version control > Github.
3. You will be prompted about the project containing a pom file. Choose to open it.
4. By default, a debug server run configuration will be created. You can add a deployment run configuration by going to edit configurations in the run menu.
5. Click the green plus in the Run/Debug configurations windo and choose Google App Engine Deployment
6. You may need to configure a server. Click on the ... button. This opens the Clouds window.
7. Click the green plus and enter your gmail address and password

1. On project explorer, right click and choose import
2. Choose Maven > Existing Maven Projects
3. Navigate to the git checkout and load the project that is found.
4. After the import, right click on the main gimme-your-files-please project, and choose Maven > Update project to download the dependencies.

1. Right click on the server and select "Run As"
2. select Run on Server
3. Create a new local AppEngine server (if necessary). The default configuration show be fine
4. Hit finish!

From then on, you should be able to start the server using the run configuration "Google App Engine at localhost" (or something to that effect). This also works for debugging.

1. From , run the following command to build the project mvn clean install
2. Run the following command to start the server mvn appengine:devserver
3. Use the tool! http://localhost:8888/gyfp#/manage/ will let you list the people with permissions on a folder that you own.

1. Deploy your version to AppEngine. Unfortunately the devserver ALWAYS returns the same user even after authentication (example@example.com). In order to test with actual drive API calls it must be running "in production"
2. Go to http://gimmeyourfilesplease.appspot.com/_ah/api/explorer. Between runs you may need to clear cache and/or cookies to get the changes to appear
3. Find and run the API call you want to test
4. If you are not authenticated, use the "main" version of the app first. Go to https://gimmeyourfilesplease.appspot.com/list?folderId=0BwyAT8fk8FVDTGpNbnlmQ09KTGM This request should ensure that you are properly authenticated for future API calls.