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

Improved env var docs a bit. #1913

Merged
merged 1 commit into from
Jun 28, 2024
Merged

Improved env var docs a bit. #1913

merged 1 commit into from
Jun 28, 2024

Conversation

Martinsos
Copy link
Member

Copy link
Contributor

@sodic sodic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice work, I'm glad we're improving this!

How does the PR relate to these two issues:

Can we take care of those as well?

web/docs/project/env-vars.md Show resolved Hide resolved
web/docs/advanced/deployment/manually.md Outdated Show resolved Hide resolved
web/docs/advanced/deployment/manually.md Outdated Show resolved Hide resolved
web/docs/project/env-vars.md Show resolved Hide resolved
web/docs/project/env-vars.md Show resolved Hide resolved
web/docs/project/env-vars.md Show resolved Hide resolved
web/docs/project/env-vars.md Outdated Show resolved Hide resolved
web/docs/project/env-vars.md Outdated Show resolved Hide resolved
web/docs/project/env-vars.md Outdated Show resolved Hide resolved
web/docs/project/env-vars.md Show resolved Hide resolved
@Martinsos
Copy link
Member Author

Nice work, I'm glad we're improving this!

How does the PR relate to these two issues:

Can we take care of those as well?

For the context, this is 3 months old PR what was adding quite specific bits to the docs regarding env vars that were missing, which was made obviuos to me from the Discord convo I linked. Somehow we forgot about this PR, and I realized now it is still open, so thought let's merge it.

That's a good point regardin g the issues you linked, and there is a general initiative to improve the env vars situation, but from taking a quick look at those issues, it is clear to me they are going quite wider in their scope. So I wouldn't tackle those now as they are not trivial, this PR is a useful incremental change on its own, and this bigger issues we can independently do later.

Copy link
Member Author

@Martinsos Martinsos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did another iteration!

I accepted some of the changes, but some of them, that are about generally improving the pieces of docs we touched, I would propose not doing in this PR. It is 3 months old PR with specific small changes, I don't have all the context I had then and I would rather not get entangled into the rest of the docs here. We can have a separate effort where we rehaul the whole file to make it be closer to our writing guide. I did though make sure that additions do stick to writing guide.

Copy link
Contributor

@sodic sodic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm approving. You can merge this when you're satisfied.

Do what you want with all remaining unresolved comments (and resolve them when you're happy). None of them are important enough to take up more time.

Btw, I forgot this is three months old. If I had remembered, I wouldn't leave that many comments (since the changes have been out of your context for a while, and aren't that important)

@Martinsos
Copy link
Member Author

I'm approving. You can merge this when you're satisfied.

Do what you want with all remaining unresolved comments (and resolve them when you're happy). None of them are important enough to take up more time.

Btw, I forgot this is three months old. If I had remembered, I wouldn't leave that many comments (since the changes have been out of your context for a while, and aren't that important)

I forgot to mention it is that old! That would have helped.
Ok, I took care of the obvious improvements and resolved the rest as I saw fit.
I will be merging it once I resolve the conflicts.

@Martinsos Martinsos merged commit e60a56b into main Jun 28, 2024
@Martinsos Martinsos deleted the env-vars-docs-fix branch June 28, 2024 08:42
infomiho pushed a commit that referenced this pull request Jun 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants