{"id":437,"date":"2013-10-17T10:02:00","date_gmt":"2013-10-17T10:02:00","guid":{"rendered":"https:\/\/opstree.com\/blog\/\/2013\/10\/17\/puppet-module-to-setup-nodejs-deployment-2\/"},"modified":"2025-11-27T15:10:24","modified_gmt":"2025-11-27T09:40:24","slug":"puppet-module-to-setup-nodejs-deployment-2","status":"publish","type":"post","link":"https:\/\/opstree.com\/blog\/2013\/10\/17\/puppet-module-to-setup-nodejs-deployment-2\/","title":{"rendered":"Puppet module to setup nodejs deployment 2"},"content":{"rendered":"
\n

As I said in the previous blog Puppet module to setup nodejs deployment, the nodejs module was for providing the basic infrastructure for automated node app’s deployment & as promised I’ve released the next module “nodeapp” that can be used to setup a node app on the target server.<\/p>\n

First of all I’ll talk about what this module will do to facilitate the automated deployment of a nodejs app, as already discussed we are following a convention that all the node app’s code will be present at \/home\/nodejs\/<\/b><\/i> which is referred by startNodeApp.sh<\/b><\/i> script so we create the directory of nodejs app. The deployNodeApp.sh<\/b><\/i> script was using the upstart to manage the nodejs app instance i.e starting\/stoppping the nodejs app, the nodeapp module takes care of creating the require upstart<\/b> configuration at \/etc\/init\/.conf<\/b><\/i>. Also we use monit to monitor the nodejs app’s so that we can start\/stop the nodejs app’s using the web ui of monit<\/b><\/i> & also see various stats such as cpu, memory, load.. consumption of nodejs app.<\/p>\n

This nodeapp module is a userdefined<\/b> type which takes the name of nodeapp as an argument, as a result of which you can setup any number of nodejs app’s on a system.
\ni.e nodeapp{‘search-demo’: app_name => “search-demo”}
\nThis entry will create below files<\/p>\n

\/etc\/init\/search-demo.con<\/b><\/i>f : An upstart configuration file, using which search demo nodejs app can be managed as a service.<\/p>\n

#!upstart
\ndescription “node.js search-demo server”
\nauthor\u00a0\u00a0\u00a0\u00a0\u00a0 “sandy”<\/i><\/i>start on startup
\nstop on shutdownscript
\nexport HOME=”\/home\/nodejs”<\/p>\n

echo $$ > \/var\/run\/search-demo.pid
\nexec sudo -u nodejs \/home\/nodejs\/startNodeApp.sh search-demo
\nend script<\/p>\n

pre-start script
\n# Date format same as (new Date()).toISOString() for consistency
\necho “[`date -u +%Y-%m-%dT%T.%3NZ`] (sys) Starting” >> \/var\/log\/search-demo.sys.log
\nend script<\/p>\n

 <\/p>\n

<\/i><\/i>pre-stop script
\nrm \/var\/run\/search-demo.pid
\necho “[`date -u +%Y-%m-%dT%T.%3NZ`] (sys) Stopping” >> \/var\/log\/search-demo.sys.log
\nend script<\/i>\/etc\/monit\/conf.d\/search-demo.monit<\/b><\/i> : A monit configuration file, using which search-demo nodejs app can be monitored & even automatedly restarted<\/p>\n

check process search-demo with pidfile \/var\/run\/search-demo.pid
\nstop program = “\/sbin\/stop search-demo”
\nstart program = “\/sbin\/start search-demo”<\/p>\n

So using these 2 modules nodejs & nodeapp you can make any system up & running for nodejs app’s automated deployment<\/p>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

As I said in the previous blog Puppet module to setup nodejs deployment, the nodejs module was for providing the basic infrastructure for automated node app’s deployment & as promised I’ve released the next module “nodeapp” that can be used to setup a node app on the target server. First of all I’ll talk about … Continue reading “Puppet module to setup nodejs deployment 2”<\/span><\/a><\/p>\n","protected":false},"author":171775670,"featured_media":29900,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_coblocks_attr":"","_coblocks_dimensions":"","_coblocks_responsive_height":"","_coblocks_accordion_ie_support":"","jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","enabled":false},"version":2}},"categories":[28070474,3548],"tags":[44070,30871489,31896918,768739288],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"https:\/\/opstree.com\/blog\/wp-content\/uploads\/2025\/11\/DevSecOps-1.jpg","jetpack_likes_enabled":true,"jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/pfDBOm-73","jetpack-related-posts":[],"_links":{"self":[{"href":"https:\/\/opstree.com\/blog\/wp-json\/wp\/v2\/posts\/437"}],"collection":[{"href":"https:\/\/opstree.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/opstree.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/opstree.com\/blog\/wp-json\/wp\/v2\/users\/171775670"}],"replies":[{"embeddable":true,"href":"https:\/\/opstree.com\/blog\/wp-json\/wp\/v2\/comments?post=437"}],"version-history":[{"count":5,"href":"https:\/\/opstree.com\/blog\/wp-json\/wp\/v2\/posts\/437\/revisions"}],"predecessor-version":[{"id":30073,"href":"https:\/\/opstree.com\/blog\/wp-json\/wp\/v2\/posts\/437\/revisions\/30073"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/opstree.com\/blog\/wp-json\/wp\/v2\/media\/29900"}],"wp:attachment":[{"href":"https:\/\/opstree.com\/blog\/wp-json\/wp\/v2\/media?parent=437"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/opstree.com\/blog\/wp-json\/wp\/v2\/categories?post=437"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/opstree.com\/blog\/wp-json\/wp\/v2\/tags?post=437"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}