Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation links to unmaintained dotenv repo #3168

Closed
ethan-sargent opened this issue Apr 3, 2024 · 3 comments · May be fixed by #3169
Closed

Documentation links to unmaintained dotenv repo #3168

ethan-sargent opened this issue Apr 3, 2024 · 3 comments · May be fixed by #3169
Labels

Comments

@ethan-sargent
Copy link

Bug Description

The Readme links to dotenv, which is unmaintained as per RUSTSEC-2021-0141.

Propose updating the link to https://github.com/allan2/dotenvy which is a maintained fork.

@abonander
Copy link
Collaborator

The dotenvy readme does not show what a .env file should look like. That is the reason we still link to dotenv. We already have a superscript note explaining that in both the README and the documentation.

@abonander abonander closed this as not planned Won't fix, can't repro, duplicate, stale Apr 3, 2024
@ethan-sargent
Copy link
Author

@abonander Sorry about that - I didn't see the superscript note.

Not sure if you are aware of this open issue in dotenvy where someone else seems to have missed the superscript note a couple of weeks ago.

Would you be happy with the suggestion from the maintainer of dotenvy to link directly to the repo instead of to an example? Or do you believe it is important to link directly to an example?

@ethan-sargent
Copy link
Author

For what it's worth, I'm happy to raise the PRs to update the documentation in dotenvy and here - I opened the issue first to have an issue to link to in my PR (and to get this kind of feedback), not to create documentation work for others.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants