Design proposal: jaws new, jaws routes, jaws deploy about serverless HOT 7 CLOSED

👍 Yes, I agree that making the JAWS CLI standalone needs to happen. This weekend, I plan on moving it to a separate repo.

Also, I'm a fan of those Rails commands and I would love to incorporate them.

This weekend, I will be publishing the JAWS Road Map. I will include your suggestions in the JAWS CLI section. If you would like to help out with these it would be greatly appreciated. All source contributors will be publicly acknowledged wherever JAWS has a presence.

If anyone has suggestions for useful commands and overall JAWS CLI design, please write them in this issue for the time being.

from serverless.

Awesome! Looking forward to the roadmap 🍻 👍

from serverless.

This could be out of scope (or you might have already considered it), but has any thought gone into versioning on AWS? Since AWS doesn't support any versioning system, could we have a sort of namespacing config option to preface "staging" or "qa" or some other environment name to the lambda function names when uploading non-prod-ready functions?

from serverless.

@nateupstairs i like that idea too.

from serverless.

Why not use yeoman to scaffold a jaws app? New lambda function could be created with a dedicated generator (yo jaws:lambda) and all the other task (run, test, deploy, etc.) could be done with gulp.

from serverless.

@remi I like yeoman a lot, really easy to work with and build complex
generators / cli tools

Here is a yeoman generator someone made for lambda's already. He uses make files, so it's not a perfect fit, but it is a nice head start.

from serverless.

@remicastaing @austinrivas I like Yeoman as well. However, I'm going to investigate a JAWS CLI redesign first. I think a robust JAWS CLI can significantly reduce time-to-action and get people started right away, without having to mess with anything else.

For example, getting started with JAWS could/should be as simple as this:

• npm install jaws-cli -g
• jaws new --name new-app

I'm going to draw out some ideas for a JAWS CLI redesign in the new JAWS-cli repo. Let's move this discussion here: https://github.com/jaws-stack/JAWS-cli/issues/1

from serverless.