Project status (2022)
hlascelles opened this issue · comments
Hi @laserlemon, can we get another cut of this gem please, with a few of the open PRs? Maybe a request to rebase / fix builds will be done if a new gem version was definitely coming.
I can see a number of PRs now have merge conflicts, but this is mostly due to them lying fallow for so long.
Can we request again that more maintainers are added to this project? #279 (comment)
If not, I hope you don't mind if we pursue a hard fork of the gem with a new name. It would be a shame, but I'd hate this gem to fade away!
For many years I relied on the Figaro gem, but it has unfortunately not been maintained. The latest problem Psych::BadAlias led me to roll my own solution.
This turned out to be pretty simple, and I continue to use the application.yml file originally defined for Figaro.
See this SO post for details. Comments welcome there.
@scarroll32 I have decided to fork this gem, so that its inspiration may live again. The new gem is called figjam.
It can be found here:
https://github.com/hlascelles/figjam
https://rubygems.org/gems/figjam
It is initially a direct fork (without the heroku functionality). I started with the same version number and code as Figaro, and aliased the Figjam namespace to Figaro to allow it to be used as a drop-in replacement.
@laserlemon I hope you don't mind this move. Figjam will stay in the yaml world, whereas the Figaro gem was going to change with v2.x anyway, so I feel they can cover different spaces for different users.
@scarroll32, and anyone else, do open PRs against the figjam repo, I will be actively maintaining it. I will also go through open PRs on Figaro and apply them to that gem (with author attribution).
Thank you again @laserlemon, your gem has been a huge help to us over the years!