Stick with Heroku or also test AWS? If the latter...
Move latest three commits to new branch, Heroku, and perform the following:
git branch Heroku
git reset --hard HEAD~3
That will rollback our "BCC-Structure" branch to non-Heroku and move the Heroku-specific configuration to the new branch. Will also be making a new AWS branch as well. That way we can easily test AWS vs. Heroku by checking out the particular branch without adding a bunch of commits to the main codebase by switching back and forth for developmental reasons.
Alternatively deciding to stick with the Heroku dev instance during development. And later configuring another Heroku instance for production.
Stick with Heroku or also test AWS? If the latter... Move latest three commits to new branch, Heroku, and perform the following:
That will rollback our "BCC-Structure" branch to non-Heroku and move the Heroku-specific configuration to the new branch. Will also be making a new AWS branch as well. That way we can easily test AWS vs. Heroku by checking out the particular branch without adding a bunch of commits to the main codebase by switching back and forth for developmental reasons.
Alternatively deciding to stick with the Heroku dev instance during development. And later configuring another Heroku instance for production.