Versions Compared

Old Version 15

changes.mady.by.user Candide Kemmler

Saved on

compared with

New Version Current

changes.mady.by.user Candide Kemmler

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Setup properties files

...

When you're looking at your Jawbone Application, either because you just created it or because you clicked on a previously created one, you will see values for Client Id, App Secret, and OAuth redirect URLs.  These are the values you'll need to copy into  jawboneUp.client.id, jawboneUp.client.secret, and jawboneUp.validRedirectURL in oauth.properties.  You can have multiple OAuth redirect URLs associated with a given Jawbone application.  Just copy the one that's appropriate for a given Fluxtream instance into oauth.properties.  

Once you have set up the keys, rebuild, rerun, and check that Jawbone UP now appears when you do Add connectors.

Flickr

If flickrConsumerKey, flickrConsumerSecret, and flickr.validRedirectURL are set to a non xxx value in oauth.properties, Fluxtream can support the use of Flickr connectors.  If any are not set, Flickr will not be available via the add connector dialog.  

...

Set the flickr.validRedirectURL in oauth.properties to the same value you submitted for the Callback URL, and set flickrConsumerKey to the Key and flickrConsumerSecret to the Secret value Flickr gives you for the key request.

...

Set the moves.validRedirectURL in oauth.properties to the same value you submitted for the Redirect URI, set moves.client.id to the Client ID and moves.client.secret to the Client Secret value Moves gives you for the key request.

...

Note: you will need node.js for this

in a Terminal:

...

`clone git@github.com:fluxtream/swagger-ui.git`

`cd swagger-ui`

`npm run-script build`

...

`cd $TOMCAT_ROOT/webapps`

`ln -s ~/projects/swagger-ui/dist swagger-ui`