Project status? about figaro HOT 15 OPEN

We have a fork with a couple of changes (looks like 255 other people do too!). It may mean someone (...) will have to make a statement of intent to hard fork, rename and release as a new gem if we can't get hold him. I see he actually works at Github. I will try contacting him there.

from figaro.

Not everyone is moving to Kubernetes and this gem works fine with Heroku. I'd like to see a new release simply because the current one is preventing me from keeping my dependencies up-to-date. If that's not going to happen I'll try to switch to dotenv-rails.

from figaro.

Looks like @laserlemon is offline ... is anyone maintaining a fork of this project?

from figaro.

Hello and sorry for dropping off the map! I have all of the excuses you'd expect: family and full-time job. I still care very much about Figaro but have had difficulty finding and prioritizing time for its developemnt and gauging its continued value in the community. I'm attempting to provide some solution to both of those problems by opening my sponsorship profile and I've added an UPDATE section to the README with this information as well.

Sorry this answer doesn't provide more immediate results, but I hope that you'll stick with me as I try to navigate back to active Figaro development! 💛

from figaro.

@laserlemon are you open to taking on additional maintainers?

from figaro.

Yes, I'll offer too. Its a great gem, we'd be very keen to keep it maintained.

from figaro.

Yes, I'll offer too. Its a great gem, we'd be very keen to keep it maintained.

from figaro.

What is the status of the version 2 branch? If it's far from releasable, it may be best to release a new 1.x version with updated dependencies.

from figaro.

Rails is pushing for using encrypted secrets now, but I still prefer the approach of this Gem. I have mostly worked with Heroku and VPS / Capistrano setups. Not sure if there is still a place for with Kubernetes...

from figaro.

Yes, agree, if we can just get a simple 1.x update with newer dependency ranges, that would be helpful.

from figaro.

+1 for a dependency update!

from figaro.

+2 for a dependency update!

from figaro.

@dotconde version 1.2.0 was released some time ago and should be fully up-to-date regarding dependencies.

from figaro.

Thank you @mvz

from figaro.

Note, figaro has now been forked to a new gem called figjam.

It can be found here:

https://github.com/hlascelles/figjam
https://rubygems.org/gems/figjam

It is initially a direct fork of figaro (without the heroku functionality), even replicating the Figaro module namespace. . PRs from the figaro repo will be ported over in the coming weeks/months.

Do submit PRs there!

from figaro.