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

Improve remote-ign docs #430

Closed
bgilbert opened this issue Jul 14, 2022 · 1 comment · Fixed by #473
Closed

Improve remote-ign docs #430

bgilbert opened this issue Jul 14, 2022 · 1 comment · Fixed by #473

Comments

@bgilbert
Copy link
Contributor

We should discourage plain HTTP. Let's switch to HTTPS and give examples of gs and s3 URLs.

@dustymabe
Copy link
Member

Talking about this page? https://docs.fedoraproject.org/en-US/fedora-coreos/remote-ign/

I think it would be useful to keep an http example because people are inevitably going to need it, but maybe add warnings/notes?

Okeanos added a commit to Okeanos/fedora-coreos-docs that referenced this issue Oct 4, 2022
Convert basic examples to more secure HTTPS and separately explain plain HTTPS
with an added warning.

Add hint about other supported protocols and an HTTPS proxy example to expand
existing documentation with other supported (common) use cases.

Resolves coreos#430
Okeanos added a commit to Okeanos/fedora-coreos-docs that referenced this issue Oct 4, 2022
Convert basic examples to more secure HTTPS and separately explain plain HTTP
with an added warning.

Add hint about other supported protocols and an HTTPS proxy example to expand
existing documentation with other supported (common) use cases.

Resolves coreos#430
Okeanos added a commit to Okeanos/fedora-coreos-docs that referenced this issue Oct 5, 2022
Convert basic examples to more secure HTTPS and separately explain plain HTTP
with an added warning.

Add hint about other supported protocols and an HTTPS proxy example to expand
existing documentation with other supported (common) use cases.

Resolves coreos#430
bgilbert pushed a commit that referenced this issue Oct 11, 2022
Convert basic examples to more secure HTTPS and separately explain plain HTTP
with an added warning.

Add hint about other supported protocols and an HTTPS proxy example to expand
existing documentation with other supported (common) use cases.

Resolves #430
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 a pull request may close this issue.

2 participants