Added instructions to generate Twitter consumer keys and access tokens to READMEs

This commit is contained in:
Andrew Phillips 2011-06-01 21:16:33 +02:00
parent bc3c0e6597
commit 20b32e77a9
4 changed files with 76 additions and 64 deletions

View File

@ -1,48 +0,0 @@
====
Copyright (C) 2011 Cloud Conscious, LLC. <info@cloudconscious.com>
====================================================================
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
====================================================================
====
Please modify your maven settings.xml like below before attempting to run 'mvn -Plive install'
<profile>
<id>cloudbees</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<properties>
<bees.appid>yourappid</bees.appid>
<bees.environment>yourenv</bees.environment>
</properties>
</profile>
<profile>
<id>keys</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<properties>
<jclouds.aws-s3.identity>YOUR_ACCESS_KEY_ID</jclouds.aws-s3.identity>
<jclouds.aws-s3.credential>YOUR_SECRET_KEY</jclouds.aws-s3.credential>
<jclouds.cloudfiles-us.identity>YOUR_USER</jclouds.cloudfiles-us.identity>
<jclouds.cloudfiles-us.credential>YOUR_HEX_KEY</jclouds.cloudfiles-us.credential>
<jclouds.azureblob.identity>YOUR_ACCOUNT</jclouds.azureblob.identity>
<jclouds.azureblob.credential>YOUR_BASE64_ENCODED_KEY</jclouds.azureblob.credential>
<jclouds.twitter.identity>YOUR_TWITTER_USERNAME</jclouds.twitter.identity>
<jclouds.twitter.credential>YOUR_TWITTER_PASSWORD</jclouds.twitter.credential>
</properties>
</profile>

View File

@ -25,6 +25,8 @@ It should not be regarded as a sample of how to write a web application using Sp
however! The original jclouds-demo-gae-tweetstore has been modified in as few places as however! The original jclouds-demo-gae-tweetstore has been modified in as few places as
possible; it has not been rewritten in the style of a Spring MVC application. possible; it has not been rewritten in the style of a Spring MVC application.
A guide to generating Twitter consumer keys and access tokens is at http://tinyurl.com/2fhebgb
This sample uses the Google App Engine for Java SDK located at This sample uses the Google App Engine for Java SDK located at
http://code.google.com/p/googleappengine/downloads/list http://code.google.com/p/googleappengine/downloads/list
@ -48,13 +50,15 @@ attempting to run 'mvn -Plive install'
<activeByDefault>true</activeByDefault> <activeByDefault>true</activeByDefault>
</activation> </activation>
<properties> <properties>
<jclouds.aws-s3.identity>YOUR_ACCESS_KEY_ID</jclouds.aws-s3.identity> <test.aws-s3.identity>YOUR_ACCESS_KEY_ID</test.aws-s3.identity>
<jclouds.aws-s3.credential>YOUR_SECRET_KEY</jclouds.aws-s3.credential> <test.aws-s3.credential>YOUR_SECRET_KEY</test.aws-s3.credential>
<jclouds.cloudfiles-us.identity>YOUR_USER</jclouds.cloudfiles-us.identity> <test.cloudfiles-us.identity>YOUR_USER</test.cloudfiles-us.identity>
<jclouds.cloudfiles-us.credential>YOUR_HEX_KEY</jclouds.cloudfiles-us.credential> <test.cloudfiles-us.credential>YOUR_HEX_KEY</test.cloudfiles-us.credential>
<jclouds.azureblob.identity>YOUR_ACCOUNT</jclouds.azureblob.identity> <test.azureblob.identity>YOUR_ACCOUNT</test.azureblob.identity>
<jclouds.azureblob.credential>YOUR_BASE64_ENCODED_KEY</jclouds.azureblob.credential> <test.azureblob.credential>YOUR_BASE64_ENCODED_KEY</test.azureblob.credential>
<jclouds.twitter.identity>YOUR_TWITTER_USERNAME</jclouds.twitter.identity> <test.twitter.gae-tweetstore-spring.consumer.identity>YOUR_TWITTER_CONSUMER_KEY</test.twitter.gae-tweetstore-spring.consumer.identity>
<jclouds.twitter.credential>YOUR_TWITTER_PASSWORD</jclouds.twitter.credential> <test.twitter.gae-tweetstore-spring.consumer.credential>YOUR_TWITTER_CONSUMER_SECRET</test.twitter.gae-tweetstore-spring.consumer.credential>
<test.twitter.gae-tweetstore-spring.access.identity>YOUR_TWITTER_ACCESSTOKEN</test.twitter.gae-tweetstore-spring.access.identity>
<test.twitter.gae-tweetstore-spring.access.credential>YOUR_TWITTER_ACCESSTOKEN_SECRET</test.twitter.gae-tweetstore-spring.access.credential>
</properties> </properties>
</profile> </profile>

View File

@ -17,6 +17,8 @@
==================================================================== ====================================================================
==== ====
A guide to generating Twitter consumer keys and access tokens is at http://tinyurl.com/2fhebgb
This sample uses the Google App Engine for Java SDK located at This sample uses the Google App Engine for Java SDK located at
http://code.google.com/p/googleappengine/downloads/list http://code.google.com/p/googleappengine/downloads/list
@ -40,13 +42,15 @@ attempting to run 'mvn -Plive install'
<activeByDefault>true</activeByDefault> <activeByDefault>true</activeByDefault>
</activation> </activation>
<properties> <properties>
<jclouds.aws-s3.identity>YOUR_ACCESS_KEY_ID</jclouds.aws-s3.identity> <test.aws-s3.identity>YOUR_ACCESS_KEY_ID</test.aws-s3.identity>
<jclouds.aws-s3.credential>YOUR_SECRET_KEY</jclouds.aws-s3.credential> <test.aws-s3.credential>YOUR_SECRET_KEY</test.aws-s3.credential>
<jclouds.cloudfiles-us.identity>YOUR_USER</jclouds.cloudfiles-us.identity> <test.cloudfiles-us.identity>YOUR_USER</test.cloudfiles-us.identity>
<jclouds.cloudfiles-us.credential>YOUR_HEX_KEY</jclouds.cloudfiles-us.credential> <test.cloudfiles-us.credential>YOUR_HEX_KEY</test.cloudfiles-us.credential>
<jclouds.azureblob.identity>YOUR_ACCOUNT</jclouds.azureblob.identity> <test.azureblob.identity>YOUR_ACCOUNT</test.azureblob.identity>
<jclouds.azureblob.credential>YOUR_BASE64_ENCODED_KEY</jclouds.azureblob.credential> <test.azureblob.credential>YOUR_BASE64_ENCODED_KEY</test.azureblob.credential>
<jclouds.twitter.identity>YOUR_TWITTER_USERNAME</jclouds.twitter.identity> <test.twitter.gae-tweetstore.consumer.identity>YOUR_TWITTER_CONSUMER_KEY</test.twitter.gae-tweetstore.consumer.identity>
<jclouds.twitter.credential>YOUR_TWITTER_PASSWORD</jclouds.twitter.credential> <test.twitter.gae-tweetstore.consumer.credential>YOUR_TWITTER_CONSUMER_SECRET</test.twitter.gae-tweetstore.consumer.credential>
<test.twitter.gae-tweetstore.access.identity>YOUR_TWITTER_ACCESSTOKEN</test.twitter.gae-tweetstore.access.identity>
<test.twitter.gae-tweetstore.access.credential>YOUR_TWITTER_ACCESSTOKEN_SECRET</test.twitter.gae-tweetstore.access.credential>
</properties> </properties>
</profile> </profile>

View File

@ -0,0 +1,52 @@
====
Copyright (C) 2011 Cloud Conscious, LLC. <info@cloudconscious.com>
====================================================================
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
====================================================================
====
A guide to generating Twitter consumer keys and access tokens is at http://tinyurl.com/2fhebgb
Please modify your maven settings.xml like below before attempting to run 'mvn -Plive install'
<profile>
<id>cloudbees</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<properties>
<bees.apikey>yourapikey</bees.apikey>
<bees.secret>yoursecret</bees.secret>
</properties>
</profile>
<profile>
<id>keys</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<properties>
<test.aws-s3.identity>YOUR_ACCESS_KEY_ID</test.aws-s3.identity>
<test.aws-s3.credential>YOUR_SECRET_KEY</test.aws-s3.credential>
<test.cloudfiles-us.identity>YOUR_USER</test.cloudfiles-us.identity>
<test.cloudfiles-us.credential>YOUR_HEX_KEY</test.cloudfiles-us.credential>
<test.azureblob.identity>YOUR_ACCOUNT</test.azureblob.identity>
<test.azureblob.credential>YOUR_BASE64_ENCODED_KEY</test.azureblob.credential>
<test.twitter.runatcloud-tweetstore.consumer.identity>YOUR_TWITTER_CONSUMER_KEY</test.twitter.runatcloud-tweetstore.consumer.identity>
<test.twitter.runatcloud-tweetstore.consumer.credential>YOUR_TWITTER_CONSUMER_SECRET</test.twitter.runatcloud-tweetstore.consumer.credential>
<test.twitter.runatcloud-tweetstore.access.identity>YOUR_TWITTER_ACCESSTOKEN</test.twitter.runatcloud-tweetstore.access.identity>
<test.twitter.runatcloud-tweetstore.access.credential>YOUR_TWITTER_ACCESSTOKEN_SECRET</test.twitter.runatcloud-tweetstore.access.credential>
</properties>
</profile>