node.js app deploy to heroku PaaS
Download as PDF, PPTX3 likes2,684 views
The document outlines the steps for deploying a project to Heroku, including installation of the Heroku CLI, logging in, and configuring necessary files such as the Procfile and package.json. It emphasizes the importance of setting up a Git remote and ensuring the project meets specific requirements for successful deployment. Additional resources for troubleshooting and best practices are provided.
More Related Content
Similar to node.js app deploy to heroku PaaS (17)
node.js app deploy to heroku PaaS
- 1. Caesar Chi @clonncd deploy to https://www.heroku.com/ Monday, May 5, 14
- 2. Install Command line Monday, May 5, 14
- 3. install heroku cli parts install heroku-cli https://toolbelt.heroku.com/standalone Monday, May 5, 14
- 4. heroku login command line input, Monday, May 5, 14
- 5. Use Heroku dashboard Monday, May 5, 14
- 6. https://dashboard.heroku.com/apps have to login, of course Monday, May 5, 14
- 7. Monday, May 5, 14
- 8. Monday, May 5, 14
- 9. Monday, May 5, 14
- 10. Monday, May 5, 14
- 11. git remote add heroku [email protected]:example-test.git command line input, Monday, May 5, 14
- 12. Set Procfile Monday, May 5, 14
- 13. Procfile Added a file, called file content Monday, May 5, 14
- 14. Import RSA keys Monday, May 5, 14
- 16. updated, app.js change port config Monday, May 5, 14
- 17. Starting deploy Monday, May 5, 14
- 18. command line input, Monday, May 5, 14
- 19. create a worker for process, only 1 web is ok. command line input, Monday, May 5, 14
- 20. http://XXXXXXX.herokuapp.com/ command line input, open browser from local machine Monday, May 5, 14
- 21. Finished Monday, May 5, 14
- 22. heroku dashboard heroku open Monday, May 5, 14
- 23. Demo github reps https://github.com/nodejs-tw/example-week1 Monday, May 5, 14
- 24. Problem || Issue Monday, May 5, 14
- 25. Make sure • Your project already use via git • package.json is required • dependency should be setting • Procfile have to named Procfile • git remote have set to heroku rep in Monday, May 5, 14
- 27. Heroku getting start with node.js https://devcenter.heroku.com/articles/getting-started-with- nodejs Monday, May 5, 14
- 28. @clonncd Monday, May 5, 14
- 29. Its 201405 ver • every spec should be followed Heroku • node.js version should be notice • logo’s copyright be companys Monday, May 5, 14