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] Inclusion within crowdsec-docs #188

Open
LaurenceJJones opened this issue Sep 23, 2024 · 3 comments
Open

[Documentation] Inclusion within crowdsec-docs #188

LaurenceJJones opened this issue Sep 23, 2024 · 3 comments
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@LaurenceJJones
Copy link

LaurenceJJones commented Sep 23, 2024

Hey 👋🏻

Over the weeks at @crowdsecurity we have been discussing our current documentation and as it stands we only host first party supported documentation. However, since this remediation is very popular we stand to both benefit from an inclusion of material based on this remediation and how it can be used.

Would you be happy for us to do this? we always want to seek permission before doing something as what our intention:

  • Use the readme.md as a starting point
  • Refactor the current format to be more aligned with our first party:
    • Heading (add to your readme to get most up to date information)
    • Getting started (simply remediation)
    • Getting started (AppSec)
    • Configuration options (this might get little complicated as dynamic configuration and labels are two separate)

It will be on us to make sure the documentation stays up to date with your current options. However, I have seen this is mostly stable and not much breaking changing / new configuration options have been included.

Let me know your thoughts!

@mathieuHa
Copy link
Collaborator

Hi @LaurenceJJones,

Yes, I think It's a good Idea. Can you just clarify one point for us. We understood that we could help you write a first version of documentation with the structure you mentioned that would be published in Crowdsec doc website. Is that correct ? Like for instance adding a Traefik Remediation component documented like the https://docs.crowdsec.net/u/bouncers/haproxy HAProxy one

Please let us know if that what you meant

@mathieuHa mathieuHa self-assigned this Sep 24, 2024
@mathieuHa mathieuHa added the documentation Improvements or additions to documentation label Sep 24, 2024
@LaurenceJJones
Copy link
Author

Hi @LaurenceJJones,

Yes, I think It's a good Idea. Can you just clarify one point for us. We understood that we could help you write a first version of documentation with the structure you mentioned that would be published in Crowdsec doc website. Is that correct ? Like for instance adding a Traefik Remediation component documented like the https://docs.crowdsec.net/u/bouncers/haproxy HAProxy one

Please let us know if that what you meant

It up to you, we are happy to do it or if you wish to collaborate together on the PR then we invite you too also. It would be like the HAProxy format, provides context at the top then some "classical" examples and then goes into the configuration structure.

@mathieuHa
Copy link
Collaborator

Yes I would like that, I'll create in the next following days a PR for this when I got the time

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

No branches or pull requests

2 participants