Skip to content

Instantly share code, notes, and snippets.

@naomifeehan

naomifeehan/doc-requests.md

Created April 28, 2016 09:51
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save naomifeehan/e3ea78bcff6b66c71afe2b68bad151dc to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save naomifeehan/e3ea78bcff6b66c71afe2b68bad151dc to your computer and use it in GitHub Desktop.
Download ZIP
Seneca Documentation requests
Raw
doc-requests.md

We are in the process of updating our documentation and want to ensure that we are providing valuable resources for the Seneca community.

This would be a great place to gather feedback from the community on any areas they wish to see documented.

@kevin-madhu
Copy link

kevin-madhu commented Apr 29, 2016 •
edited
Loading

Only simple examples and documentation which only gives a small side of the story are available. Make the canvas bigger if possible:

  • Like seneca in a production setup, what all configurations and setup are likely to be done. Best practices.
  • Docker seneca combination.
  • Security architecture
  • Architectures in production environment like choosing different scenarios and explaining what's the best thing to do. For eg, like I need to do photo upload, and I'm planning on using a proxy for serving content. I think it'll be a bad idea to be forwarding that data to the microservices. Okay then I'll keep the copy somewhere and send only a reference to the microservices, then where do I really keep the real data. How do I manage the credentials to the actual storage which is most likely to be held my a microservice somewhere. Questions like this. When we can see how you people manage a couple of situations like this, it'll be great :)

Sorry, not an expert myself, but that's why I'm here in the first place :) - just blurting out whatever came to mind. In short more PRACTICAL scenarios based on PRODUCTION setup.

@naomifeehan
Copy link
Author

naomifeehan commented Apr 29, 2016

thanks guys this is all very useful to us

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment