You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 26, 2024. It is now read-only.
Repository navigation
This repository was archived by the owner on Mar 26, 2024. It is now read-only.
What is the state of this project ? :)
I know everybody contribute on his free time, and I really appreciate your works.
I (still) use it in production as an ENC, and I think I'm not alone in view of all opened issues/pull requests.
There is some "active" forks ( https://github.com/swoopla/puppet-dashboard ) or usefull PR which need to be merged ( #336, #334 or #333 for debian packaging! etc). @sodabrew , is it a lake of time, interested, did you abandon the project ?
Do you need help or it is better to fork it to revive it ?
I second @Skunnyk - we use Puppet Dashboard (1.2.23) in my business, but would like to know if there is anyone actively working on it. Also, could we perhaps identify a fixed set of things to fix before a 2.0 release?
It doesn't do classes / groups, and thus can't be used as an ENC.
It only does the visualization.
Being self-contained it is less fragile and simpler to install. It was also a fun learning experience. In the absence of activity here it might be useful to some.
@sodabrew I'm using the Puppet Dashboard still heavily as it is in my opinion still one of the most accurate and presents the information I need in a very clear way. However there are some parts where I would like to extend on it.
It seems to me that the time you have to maintain this project is very limited, which is just natural and happens to a lot of projects around Puppet all the time.
Since I don't just want to make another fork which gets abandoned in a few months, would you be willing to transfer the project to Voxpupuli if possible so people interested (like me at the moment) can take over maintainership easily at a central location and continue the great project?
@bastelfreak I talked about this on the IRC channel a while ago and you told me you would have to think about it. Did you come to any conclusion if voxpupuli would be interested in hosting the repository of @sodabrew is willing to transfer the project?
There are a few PR ready to be merged which will put the project into a completely usable state with everything from newest Rails to all stable rubies and the newest Puppet 5 stuff.
a few things have been recently merged in; I'm going to try to wrap a few things up, do a 23.0 release, then get it migrated over to vox pupuli if possible
So I'm going to close this issue; the state is revived (at least for the short term) and we're planning on doing a 3.0 release soon! Please send your issues and PRs! we're in the process of figuring out longer-term plan.
Activity
larsnaesbye commentedon Nov 3, 2016
I second @Skunnyk - we use Puppet Dashboard (1.2.23) in my business, but would like to know if there is anyone actively working on it. Also, could we perhaps identify a fixed set of things to fix before a 2.0 release?
sodabrew commentedon Nov 3, 2016
larsnaesbye commentedon Nov 4, 2016
Will do. But if this is going to be the state for a long time, should we not make the repo version a 2.0 release?
sodabrew commentedon Nov 4, 2016
larsnaesbye commentedon Nov 4, 2016
If we can break it down into subtasks, maybe the rest of us can? :)
sodabrew commentedon Nov 4, 2016
larsnaesbye commentedon Nov 7, 2016
Sounds good. But maybe we can do what @Skunnyk hinted at: merge #336, #334 and #333 and then take it from there?
skx commentedon Aug 10, 2017
FWIW I put together a simple golang based alternative here.
Being self-contained it is less fragile and simpler to install. It was also a fun learning experience. In the absence of activity here it might be useful to some.
ZeroPointEnergy commentedon Jun 8, 2018
@sodabrew I'm using the Puppet Dashboard still heavily as it is in my opinion still one of the most accurate and presents the information I need in a very clear way. However there are some parts where I would like to extend on it.
It seems to me that the time you have to maintain this project is very limited, which is just natural and happens to a lot of projects around Puppet all the time.
Since I don't just want to make another fork which gets abandoned in a few months, would you be willing to transfer the project to Voxpupuli if possible so people interested (like me at the moment) can take over maintainership easily at a central location and continue the great project?
ZeroPointEnergy commentedon Jun 11, 2018
@bastelfreak I talked about this on the IRC channel a while ago and you told me you would have to think about it. Did you come to any conclusion if voxpupuli would be interested in hosting the repository of @sodabrew is willing to transfer the project?
There are a few PR ready to be merged which will put the project into a completely usable state with everything from newest Rails to all stable rubies and the newest Puppet 5 stuff.
bwitt commentedon Aug 22, 2018
a few things have been recently merged in; I'm going to try to wrap a few things up, do a
23.0 release, then get it migrated over to vox pupuli if possiblebwitt commentedon Aug 25, 2018
So I'm going to close this issue; the state is revived (at least for the short term) and we're planning on doing a 3.0 release soon! Please send your issues and PRs! we're in the process of figuring out longer-term plan.