question: next steps for developer workflow for Node.js

[lance]

@DonSchenck this is a great introduction to the fundamentals of k8s for developers. One of the things I am most interested in is the developer workflow. What happens after they get all of this up and running and need to continue regular cycles of application development.

• How does a developer deal with the build, deploy, reload/restart development loop?
• What tools can a developer use to optimize this loop - including things like Chrome debugging, oc rsync, VSCode plugins, and basic oc and kubectl commands that would be typically used in this kind of development cycle?
• How does a developer deploy to staging and then roll that out to production?

These are the kinds of activities I would love to include in workshops like this. @lholmquist and I have been working on different tools and techniques that we think could be helpful in this area, and might have a place in a project like this one.

Currently the focus is on the overall installation, getting started and some tips and information for next steps - eg database. It's great that there is a .Net section as well as a Node section. But I wonder what the best way would be to organize the developer workflow sections I would like to work on adding, if you think it makes sense.

Would a new repository as a "Part Two" of the series make sense? And should this focus only on a single language workflow? I would like to hear your thoughts.

@inoxx03 tagging you here, as this may be of interest to docs folks.

[DonSchenck]

I'm going to prioritize:

1. Debugging.
2. Deploying to staging and then roll that out to production.
3. Reload/restart/resiliency tips & techniques. THIS is where Istio will be introduced.
4. More, to be determined later.

My thinking is that this top-down tutorial can be started at the beginning -- obviously -- and the user can get as far as they're able. They can always "take the assignment home" to finish it.