exacttarget / fuel-throttle-node Goto Github PK

Simplify developer's lives by watching specific directories and files for saves and automatically test, build and reload the server without requiring refresh in the browser.

Using windows command prompt when I run npm install I get the following warns and I believe because of this the project is not working properly:

npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] 'repositories' (plural) Not supported
.
npm WARN package.json Please pick one as the 'repository' field
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.

I don't remember which names changed and to what, but, just wanted to note that docs are now out of date...

New Relic is a handy tool for application monitoring, they (New Relic) are currently working on their Node.js version. But it will be BETA, and so "use at own risk" state at first.

There is a Github repo available here: https://github.com/newrelic/node-newrelic/
I'm not sure how current this is, it appears to have been a little while since it was last committed.

If anyone has any thoughts on this or suggestions (besides AppDynamics) they are welcomed. :)

If the goal of fuel-throttle is to build a single page app, which I think it is, then the route configuration in the app.js file (node server) should be changed.

The App Center login URL should point to either:

• "http://localhost:3000/"
• "http://app-name.xexacttargetapps.com/"

and not

• "http://localhost:3000/login"
• "http://app-name.xexacttargetapps.com/login"

This will make sure the app is started on the correct page for the SSO flow instead of loading itself at "/login" when the app is looking to initialize itself on "/"

For this, code changes required in /app.js. Below is what should be changed.

// FROM 
app.post('/login', tokenManager, routes.login );

// TO
app.post('/', tokenManager, routes.login );

Need to remove:

• Token Manager (possibly convert to a Node module for registry)
• Fuel Node
• JWT handling
• App Center specific data:
  • client id
  • client secret
  • app signature

NOTE: Fuel UX must remain in place, as it is a useful tool for any developer outside of ExactTarget.

The little Travis CI graphic is a nice feature and should be simple to implement. This will be for the actual repository.

Would this be helpful to implement in the template code as well?

Need to fix this, the pointer was going to an "undefined" value.

In order to instill confidence in the code and prevent unwanted changes by other contributors, all unit tests for the base code should be implemented.

Currently, this repository is using grunt-init, which will be deprecated by Yeoman generators.

Since Fuel Throttle will be released in multiple languages to support cloud deployments (typically to Cloud Foundry based environments) - implementing a language agnostic scaffolding engine in DASH which is 100% POSIX compliant would be an elegant way to reduce the support footprint across multiple languages and provide a consistent developer experience while using Fuel Throttle in different languages.

The timeout for the memoization of the token fetching in fuel is keyed off the response's expiresIn value. When a legacyToken is included the actual expiration is much shorter.

Perhaps if a legacyToken is included set that timeout to something much shorter.

Need to include the following in the documentation:

• Primary Goals
• Optional Goals
• Describe development approach
• Better describe the prompt flow so developers better understand what they'll want/need
• Describe tools required to operate and possibly more links to other learning resources
• Describe optional available tools
• Provide list of known issues w/ development approach
• Provide list of known issues w/o development approach
• Outline potential use cases

Current directions are for linux or mac systems. Need to add instructions for Windows installation and operations.

I think this would be helpful, but would like input from others.

In order to reduce the learning curve for developers who are new to NoSQL systems - providing a simple, but complete working example for MongoDB would be helpful.

When adding this feature, make sure to add it to the prompt system for implementation during the scaffolding run. Default to having it in place.