Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

content suggestion - add basic development to deployment workflow #73

Open
mjhea0 opened this issue Oct 2, 2014 · 3 comments
Open

content suggestion - add basic development to deployment workflow #73

mjhea0 opened this issue Oct 2, 2014 · 3 comments

Comments

@mjhea0
Copy link
Contributor

mjhea0 commented Oct 2, 2014

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
Copy link
Owner

rpicard commented Oct 2, 2014

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

@mjhea0
Copy link
Contributor Author

mjhea0 commented Oct 2, 2014

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
Copy link
Owner

rpicard commented Oct 2, 2014

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.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants