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

Document provider config options #40

Merged
merged 6 commits into from
Mar 23, 2022
Merged

Conversation

Fadiabb
Copy link
Contributor

@Fadiabb Fadiabb commented Jan 27, 2022

No description provided.

docs/provider-setup.md Outdated Show resolved Hide resolved
@bernhardreiter
Copy link
Collaborator

Again I think, we may improve the point by generating the documentation, if this is easily possible.
See #33 for a similar question.

@bernhardreiter
Copy link
Collaborator

As for implementing the documentation as part of the config code, e.g. in cmd/csaf_provider/config.go`: The toml library does not yet support handling of comments, see BurntSushi/toml#328

Default: `["csaf", "white", "amber", "green", "red"]`.
- upload_signature: Send signature with the request, an additional input-field in the web interface will be shown to let user enter an ascii armored signature. Default: `false`.
- openpgp_url: URL to OpenPGP key-server. Default: `https://openpgp.circl.lu`.
- domain: The domain name. Default: `http://$SERVER_NAME`.
Copy link
Collaborator

@bernhardreiter bernhardreiter Feb 10, 2022

Choose a reason for hiding this comment

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

@s-l-teichmann the domain config options is a bit unbalanced. It is called domain, but in the code, the value will be taken as base_url. And then there is http: which is okay for development, but not as default I guess. What about renaming it to serve_url and then default it to https://$SERVER_NAME or so. Where does the name SERVER_NAME come from? My search engine does not tell me it is a standard environment variable. For development either localhost or $hostname would be alternatives. What do you think?

Copy link
Collaborator

Choose a reason for hiding this comment

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

Copy link
Collaborator

Choose a reason for hiding this comment

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

Copy link
Collaborator

Choose a reason for hiding this comment

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

@s-l-teichmann Thanks for answering the second part. What about remaining domain to serve_url for the reasons outlined?

Copy link
Collaborator

Choose a reason for hiding this comment

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

@bernhardreiter We could use https:// as a default, sure.
Concerning domain ... my bike shed opinion would more tend to something like canonical_url_prefix.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Okay, changed to canonical_url_prefix.

bernhardreiter and others added 3 commits March 23, 2022 18:55
Co-authored-by: tschmidtb51 <65305130+tschmidtb51@users.noreply.github.com>
 * Moving from `domain` to `canonical_prefix_url`. Using `https` as
   default.
@bernhardreiter bernhardreiter merged commit 5e1f209 into main Mar 23, 2022
@bernhardreiter bernhardreiter deleted the document_provider_options branch March 23, 2022 18:48
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.

None yet

4 participants