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

Support for bootstrap/hook scripts #15

Open
bernd opened this issue Apr 4, 2019 · 0 comments
Open

Support for bootstrap/hook scripts #15

bernd opened this issue Apr 4, 2019 · 0 comments

Comments

@bernd
Copy link
Member

bernd commented Apr 4, 2019

When developers use graylog-project bootstrap to clone all repositories the next step is to run yarn install and an initial mvn compile. These steps are required to run the web server and graylog server development processes from the IDE.

To avoid hardcoding these commands in the CLI, the CLI should check for hook scripts in a default location. (e.g. hooks/) A good default might be to check for a script that is named after the CLI command that is executed.

Examples:

  • graylog-project bootstrap: Check and execute hooks/bootstrap.sh if it exists
  • graylog-project checkout: Check and execute hooks/checkout.sh if it exists

In addition to that, the CLI could also check for <command-name>_custom.sh files where developers can add some custom commands. (these files should be in .gitignore)

@bernd bernd added the feature label Apr 4, 2019
bernd added a commit that referenced this issue Apr 8, 2019
bernd added a commit that referenced this issue Apr 8, 2019
@bernd bernd added the triaged label Apr 8, 2019
@bernd bernd removed their assignment Mar 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant