Hello Dimitri, Hopefully someone on this list can help you with Puppet Dashboard, unfortunately I am not that person.
That said, today if I were to choose a Web UI for reporting or as ENC, I personally would not use puppet dashboard. I would like to be proven wrong, but based on a quick search of this list's archives, it appears that many people that have moved away from it and on to other Web UIs. Looking at it's github repo's [1] activity, it looks like there are long standing pull requests and open issues with it. In fact the book's author has two open PRs from about 18 months ago. It makes me sad, and I wish that Puppet Dashboard had a lively & responsive community of users/contributors because I was at PuppetConf 2013 and sat in on the presentation from @sodabrew where he expressed his intent to keep it going. You might be better served by using the alternatives as explained in the book, perhaps PuppetDB together with puppetboard[2]. [1] https://github.com/sodabrew/puppet-dashboard [2] https://github.com/voxpupuli/puppetboard As an aside, I like many parts of the book. The author has done good job of the difficult task of distilling the vibrant puppet ecosystem and tooling into a comprehensive book. However, I find it a bit odd in that a book about learning puppet 4 that says: "PuppetDB is a full-featured product worthy of its own book. At this time, the best available documentation can be found at 'PuppetDB Overview' on the Puppet docs site." - p109; basically glosses over PuppetDB when PuppetDB brings a whole lot to the table. Regards, James On Fri, Feb 10, 2017 at 5:21 PM, Dimitri Yioulos <dyiou...@gmail.com> wrote: > A bit more information: > > - I used instructions from O'Reilly *Learning Puppet 4* > - I see the reports from nodes in /opt/puppetlabs/server/ > data/puppetserver/reports. > - If I click on the "Nodes" tab in Dashboard, I get "Forbidden You don't > have permission to access /nodes on this server." > - I used dashboard.conf (as provided with *Learning Puppet 4*) for > Apache. Of course, I did some tweaking. But, here's the part that may be > the bug-a-boo: > > Listen 3000 > <VirtualHost *:3000> > ServerName dashboard.example.com > DocumentRoot /opt/puppet-dashboard/public/ <--- there is no nodes > subdirectory here > RailsBaseURI / > > > On Friday, February 10, 2017 at 3:06:23 PM UTC-5, Dimitri Yioulos wrote: >> >> Hi, All. >> >> Previously, I had a Puppet server running version 3.x, and Puppet >> Dashboard 1.2. Worked a treat. Now, I created a new Puppet server version >> 4. I got that all working fine. I also installed Dashboard 2.0.0. While >> I can see the Dashboard, there are no nodes reported. Has anyone else >> installed Puppet Dashboard 2.0.0 to work with Puppet 4 that might give me >> some help? >> >> Thanks. >> > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/puppet-users/b975e1bf-a063-4055-b021-236ed8511857%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/b975e1bf-a063-4055-b021-236ed8511857%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAOsPUcigGRvGQfSiPpexMaoQsJVjrJaOzevBnH8AO8tCK7LPaQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
