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

Opt-in to non-dataset modules #241

Closed
isaisabel opened this issue Sep 23, 2020 · 0 comments
Closed

Opt-in to non-dataset modules #241

isaisabel opened this issue Sep 23, 2020 · 0 comments
Assignees
Labels
timescale/imminent Ready to be assigned to developers

Comments

@isaisabel
Copy link
Contributor

As a user who is creating their own instance of the ATT&CK Website, I want my instance to be uncluttered by ATT&CK-centric functionalities. I mostly want to use my personal instance for exploring the contents of the knowledge base.

Modules that do not pertain to the ATT&CK dataset itself should not be built by default. They should only be added if the user explicitly specifies them with build arguments. This should also be stated clearly in the CLI documentation.

Modules that don't need to be built under the default arguments:

  • Resources
  • Versions (preserved current and previous)
  • Contribute
  • Blog

See also #240.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
timescale/imminent Ready to be assigned to developers
Projects
None yet
Development

No branches or pull requests

2 participants