rpicard / explore-flask

Source of Explore Flask book
http://exploreflask.com
1.69k stars 199 forks source link

content suggestion - add basic development to deployment workflow #73

Open mjhea0 opened 9 years ago

mjhea0 commented 9 years ago

For example -

  1. Feature Branch
  2. Create PR
  3. Run CI
  4. Merge
  5. Auto deploy to staging
  6. Test
  7. Auto deploy to production

I'm a fan of Docker for this. Docker, Jenkins, Digital Ocean

rpicard commented 9 years ago

That sounds like we'd be leaving the scope of the book. How much of that would be Flask specific?

mjhea0 commented 9 years ago

Scope is subjective. Are databases really part of Flask? What about front end? I always struggle with this as well. Developing a Flask app is so much more than just about Flask, as you know. From time to time you have to deviate out of Flask to show those other things. It's up to you, though.

Pretty much that entire workflow has very little to do with Flask, but it's about getting your dev. environment setup and then deploying a Flask app the right way.

rpicard commented 9 years ago

In the case of databases, I tried to deal with that by focusing on the Flask-specific tools for working with databases (e.g. Flask-SQLAlchemy, organizing models, etc.). I think this content would be better suited to a general "Dev-Ops Guide" medium (book, blog post, etc.)