mirror of
https://github.com/mthenw/frontail.git
synced 2026-04-26 02:05:57 +03:00
[GH-ISSUE #132] Starting tail process after recieving http request #94
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/frontail#94
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mikossheev on GitHub (Jul 16, 2018).
Original GitHub issue: https://github.com/mthenw/frontail/issues/132
Here is my case:
Frontail is used to monitor a bunch of folders with log files (one process per file, to view them separately).
There is a script that searches for the log files in directory, launches frontail and adds an nginx location for it.
Sometimes the quantity of processes getting to big, and recources are not used efficently.
Here is a question:
Is there a way to modify frontail for it to launch its own process, but the tail process to be launched only when there is a request to frontail?
@ssbarnea commented on GitHub (Aug 10, 2018):
If I am not wrong what you are are looking is more of what I described in https://medium.com/@sbarnea/how-to-share-terminal-output-on-the-web-83bf73c05c4c article, where the closes solution I found was seashells.
I came to frontail while trying to find other alternatives but apparently frontail lack few critical feature like web server mode that could be used to serve "recordings" even after client disconnected, ability to auto-generate sharable urls and so on.
I am curious if @mthenw is looking to implement features like these in the future.
@mthenw commented on GitHub (Aug 13, 2018):
@ssbarnea TBH I don't think it's a goal of frontail. I think it should stay small.