Is porcelaim dead?

[beardedeagle]

Is this project dead? There hasn't been a release for years or a commit for a long while as well and PR's have been waiting for a bit. Even the goon driver hasn't seen an update in years. I'm just wondering what the status of this project is as I would like to use it if possible.

[lpil]

Porcelain has a well defined stable feature-set. No new ones are currently being developed, but that doesn't mean the existing features are not working as intended :)

[alco]

Sadly, I've been doing a bad job maintaining the project, not for the lack of enthusiasm though. Truth is, both Porcelain and goon have some design flaws that make it easy to end up with a zombie process in some cases, even if the Erlang process terminates normally.

I have a new design planned which addresses all of the existing problems and I have tried to kick-start its implementation a few a times over the past several years, but every time I just couldn't carve enough time out of my life to bring it to a publishable state.

I'm just wondering what the status of this project is as I would like to use it if possible.

What use case do you have in mind, @beardedeagle? I would like to at least advise on whether Porcelain would work for you or maybe there's an alternative solution.

[beardedeagle]

I've written a monitoring system that runs checks kinda a la sensu style by shelling out and running the script/binary/whathaveyou from the OS, and this happens A LOT every second since I have a ton of checks to run. To clarify, it's unlikely these checks are long living and I take steps to ensure the BEAM VM doesn't crash, but I can't catch them all and I can't predict what users will set up for checks. So basically right up Port/Porcelain's alley, but I know the lack of development as well as your comment above about it "still being easy to end up with zombie processes" will make management leery about using Porcelain and unfortunately I answer to them.