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

Make the apache log monitor binary configurable in starter.ini #54

Closed
apolopena opened this issue Mar 7, 2021 · 0 comments
Closed

Make the apache log monitor binary configurable in starter.ini #54

apolopena opened this issue Mar 7, 2021 · 0 comments
Labels
enhancement New feature or request passed-dev-qa Optional state. Use this when QAing other peoples fixes in another branch.ready to be merged to main

Comments

@apolopena
Copy link
Owner

Problem this feature will solve

multitail can crash silently when run in a terminal window that is way too small. Aditionally in most situations the user is prompted to hit a key in the terminal to continue in order to lauch multitail because multitail is so finiky about the size of terminal it is run in.

Background

This feature stems from #53

Proposed Solution

Add the ability to configure your apache log monitor in starter.ini to something like grc tail /var/log/apache2/error.log /var/log/apache2/access.log
add a variable in the development section of starter 'starter.ini' named apache_log_monitor that accepts the values tail and multitail

Constraints and Assumptions

the tail call will depend on grc
Use a custom color configuration for grc

Alternatives or Workarounds

Do it manually on every creation of a workspace every time multitail fails

Additional context

tail is too ugly without something like grc to brighten the day ;) but it does now support multiple files.
Users may still want to use multitail however since it is prone to crashing silently and was never designed to run in a Docker container, offer a colorized tail.

@apolopena apolopena added the enhancement New feature or request label Mar 7, 2021
@apolopena apolopena added in-dev-qa passed-dev-qa Optional state. Use this when QAing other peoples fixes in another branch.ready to be merged to main and removed in-dev-qa labels Mar 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request passed-dev-qa Optional state. Use this when QAing other peoples fixes in another branch.ready to be merged to main
Projects
None yet
Development

No branches or pull requests

1 participant