[GH-ISSUE #44] ui-highlight not working - two scenarios #27

New issue

Closed

opened 2026-03-03 16:03:48 +03:00 by kerem · 2 comments

kerem commented

2026-03-03 16:03:48 +03:00

Owner

Originally created by @mv5492 on GitHub (Feb 23, 2015).
Original GitHub issue: https://github.com/mthenw/frontail/issues/44

I think the daemonize option creates a conflict with --ui-highlight

/local/bin/frontail --host development.web.com --port 8181 --pid-path '/pub/node/frontail.8181.pid' --key '/local/ssl/certs/new_dev_private.key' --certificate '/local/ssl/certs/upstartdev.crt' --log-path /pub/node/frontail.log --daemonize --ui-highlight /local/lib/node_modules/frontail/preset/default.json /tmp/front1

The server starts but --ui-highlight does not work. If I remove --daemonize or -d the --ui-highlight works fine as specified above with full path to json file

If I leave off the [path] to --ui-highlights (as shown) I get the error below

/local/bin/frontail --host development.web.com --port 8181 --pid-path '/pub/node/frontail.8181.pid' --key '/local/ssl/certs/dev_private.key' --certificate '/local/ssl/certs/dev.crt' --log-path /pub/node/frontail.log --ui-highlight /tmp/front1

Arguments needed, use --help

If I leave off --ui-highlight all together there is no highlighting - not picking up defaults. The daemonize option is not specified.

My --ui-highlight input file works:
{
"words": {
"err": "color: red;"
},
"lines": {
"err": "font-weight: bold; background-color: yellow;"
}
}

I modified index.js and specified the full path to the default json file and started the server as follows - moved the --ui-highlight switch to the middle of the command. This works (but still does not work with --daemonize). This make --ui-highlight positional, at least it can't be the last switch:

/local/bin/frontail --host development.web.com --ui-highlight --port 8181 --pid-path '/pub/node/frontail.8181.pid' --key '/local/ssl/certs/dev_private.key' --certificate '/local/ssl/certs/dev.crt' --log-path /pub/node/frontail.log /tmp/front1

Thank you for looking. Mike

Originally created by @mv5492 on GitHub (Feb 23, 2015). Original GitHub issue: https://github.com/mthenw/frontail/issues/44 1. I think the daemonize option creates a conflict with --ui-highlight <path>/local/bin/frontail --host development.web.com --port 8181 --pid-path '<path>/pub/node/frontail.8181.pid' --key '<path>/local/ssl/certs/new_dev_private.key' --certificate '<path>/local/ssl/certs/upstartdev.crt' --log-path <path>/pub/node/frontail.log --daemonize --ui-highlight <path>/local/lib/node_modules/frontail/preset/default.json /tmp/front1 The server starts but --ui-highlight does not work. If I remove --daemonize or -d the --ui-highlight works fine as specified above with full path to json file 1. If I leave off the [path] to --ui-highlights (as shown) I get the error below <path>/local/bin/frontail --host development.web.com --port 8181 --pid-path '<path>/pub/node/frontail.8181.pid' --key '<path>/local/ssl/certs/dev_private.key' --certificate '<path>/local/ssl/certs/dev.crt' --log-path <path>/pub/node/frontail.log --ui-highlight /tmp/front1 Arguments needed, use --help If I leave off --ui-highlight all together there is no highlighting - not picking up defaults. The daemonize option is not specified. My --ui-highlight input file works: { "words": { "err": "color: red;" }, "lines": { "err": "font-weight: bold; background-color: yellow;" } } 1. I modified index.js and specified the full path to the default json file and started the server as follows - moved the --ui-highlight switch to the middle of the command. This works (but still does not work with --daemonize). This make --ui-highlight positional, at least it can't be the last switch: <path>/local/bin/frontail --host development.web.com --ui-highlight --port 8181 --pid-path '<path>/pub/node/frontail.8181.pid' --key '<path>/local/ssl/certs/dev_private.key' --certificate '<path>/local/ssl/certs/dev.crt' --log-path <path>/pub/node/frontail.log /tmp/front1 Thank you for looking. Mike

kerem closed this issue

2026-03-03 16:03:48 +03:00

kerem commented

2026-03-03 16:03:49 +03:00

Author

Owner

@mthenw commented on GitHub (Mar 3, 2015):

Hi,

thanks for reporting. Both cases were fixed in 2.0.0. I've also introduced new option --ui-highlight-preset for providing highlight preset path.

@mthenw commented on GitHub (Mar 3, 2015): Hi, thanks for reporting. Both cases were fixed in 2.0.0. I've also introduced new option `--ui-highlight-preset` for providing highlight preset path.

kerem commented

2026-03-03 16:03:49 +03:00

Author

Owner

@mv5492 commented on GitHub (Mar 3, 2015):

My pleasure. I really like your approach to tail -f to a browser. I'm looking forward to issue#38

@mv5492 commented on GitHub (Mar 3, 2015): My pleasure. I really like your approach to tail -f to a browser. I'm looking forward to issue#38

kerem referenced this issue

2026-03-03 16:05:52 +03:00

[PR #27] [CLOSED] listen on 9002 to accept and merge netcat input #178