<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Chef on Scholion</title><link>https://scholion.thluiz.com/tags/chef/</link><description>Recent content in Chef on Scholion</description><generator>Hugo -- gohugo.io</generator><language>pt-BR</language><copyright>© 2026</copyright><lastBuildDate>Sat, 16 Mar 2013 14:10:21 -0300</lastBuildDate><atom:link href="https://scholion.thluiz.com/tags/chef/index.xml" rel="self" type="application/rss+xml"/><item><title>Vagrant, setuping machine for Node.js - Chef failure - Stack Overflow</title><link>https://scholion.thluiz.com/notes/vagrant-setuping-machine-for-node-js-chef-failure-stack-over/</link><pubDate>Sat, 16 Mar 2013 14:10:21 -0300</pubDate><guid>https://scholion.thluiz.com/notes/vagrant-setuping-machine-for-node-js-chef-failure-stack-over/</guid><description>The Chef run fails because Vagrant cannot find the &lt;code&gt;nodejs&lt;/code&gt; cookbook. The issue is resolved by renaming the cookbook folder to &lt;code&gt;nodejs&lt;/code&gt; and correcting the Vagrant recipe reference.</description></item></channel></rss>