Move to Heroku

[daniely]

To get puzzlenode moved over to Heroku we need:

• [x] @jkorz File uploads converted to use Carrierwave (#85).
• [x] @johnnymugs Configuration files config/initializers/*.example converted to use environment variables (#94)
• [x] @semmons99 Setup an account on heroku and add new project maintainers
• [x] Determine who will be the main project maintainers (IE have push access) (@semmons99, @jordanbyron, ...)
• [x] @jordanbyron setup an S3 bucket for file uploads
• [x] @jordanbyron restore the database on Heroku
• [x] Cut over DNS

from mendicant univ mailing list

If there is anything else missing please comment below.

[jordanbyron]

Thanks @daniely for getting the ball rolling. I've expanded my original list so we can see all of the steps necessary to make this migration happen. Now we just need people to roll up their selves and start code'n :smile:

[johnnymugs]

Whoa, PuzzleNode was the way I learned Ruby. How can I help? I can handle the carrierwave migration and the configuration files tasks. How is the work being organized? (don't want to duplicate anyone's work)

[semmons99]

I'll take on the job of getting heroku setup and config moved to ENV vars.

[johnnymugs]

Oops! Hey Shane lemme know if you wanna pair on anything this weekend. The holiday, Monday, would be ideal!

[jkorz]

I'll take a stab at the carrierwave conversion.

[jordanbyron]

@jkorz awesome. Feel free to ping me on #85 if you need help. I just recently worked with Carrierwave so I'm up to speed :wink:

[jkorz]

@jordanbyron thanks!

[semmons99]

@johnnymugs I'll leave the ENV stuff to you and focus on getting heroku ready for contributors.

[semmons99]

should we move puzzlenode to it's own organization?

[semmons99]

PuzzleNode is now active on Heroku at http://puzzlenode.herokuapp.com. The site is in maintenance mode until everything is working. I've made Jordan a collaborator.

[jordanbyron]

should we move puzzlenode to it's own organization?

Meh I don't see what the advantage is at this point. Just another thing to do. We can always move it later once things have stabilized and there is a need for it.

[jordanbyron]

PuzzleNode is now active on Heroku at http://puzzlenode.herokuapp.com. The site is in maintenance mode until everything is working. I've made Jordan a collaborator.

Got it thanks! I've also set the project up on Travis :metal: https://travis-ci.org/mendicant-original/puzzlenode

[yangchenyun]

I recomand use figaro to manage the environment variables. As it requires no change in the application code for the usage of ENV[...] variable while easy to maintain them at one place. It is also compatible with the way heroku manages its environment variables.

[jordanbyron]

@yangchenyun figaro looks like a great fit. Would you like to integrate it into Puzzlenode once #91 is merged?

[yangchenyun]

@jordanbyron definitely, once #91 is done, if is one gem modificaiton away. I could certainly do that. If my understanding is right, I will also need to update the README.md and you will in charge of placing the real deployment-ready environment variables in your local machine?

[jordanbyron]

@yangchenyun the production server is good to go, so no need to worry about that. Before I merge the env-config branch into master I'd like to get your piece in place. Can you pull down that branch and work off of that? Thanks

[jordanbyron]

http://puzzlenode.herokuapp.com/ is alive :metal: Thanks everyone who pitched in to get it working on Heroku. We should be able to make the cutover soon.

[semmons99]

:point_up: Wow, killer work everyone!

[yangchenyun]

@jordanbyron check out #95

[jordanbyron]

I believe we are ready to make the migration happen. I'll need:

• [x] Restore the database
• [x] Re-upload all of the puzzle attachments
• [x] Update the Github keys
• [x] Cut over the DNS

Anything I am missing?

[semmons99]

That sounds right to me.

[jordanbyron]

It's official. We are on Heroku:

http://www.puzzlenode.com/announcements/13

Thanks everyone who helped make this happen: @semmons99, @daniely, @jkorz, @johnnymugs, @yangchenyun, @sandal