Just a suggestion about the chronyc use. There is the -n or -N option to prevent slow reverse DNS lookups and unnecessary DNS traffic. There is also the -c option to print the data in a CSV format, which should be much easier to parse, e.g. with awk -F , ‘{print $1}’. No need to handle the slow/fast keywords, etc.
Ah yeah, good point, I hadn’t thought of that !
I’ve added an option now so users can choose if they want a reverse DNS lookup or not, thanks for the suggestion !
As for the -c option, I’ll keep it in mind for a future version. Thanks, I didn’t know about it!
Would it be possible to have the web page auto resize it’s width to the actual web browser window width? I just realized I had resized the generated graphs width and height thinking it would change the display size in the web page/browser, only to realize that I had already resized the web page to 130%. The original size makes my old eyes strain too much.
Oh, maybe also when we click on one of the chart images, it would open the actual image at its normal size. That way if we wanted to create images at 1920x1080 size, the main webpage will display those images resized down to fit in the browser width in the same 2 columns it currently displays, but we could still easily view the full size image with a single click. Currently, I have to right-click on the image and choose to open the image in a new tab to view the original size.
@Mpegger Hey, I actually added a little feature so when you click on an image, it’ll pop up in full size now.
Thanks a lot for the suggestion! Really appreciate it
About the idea of auto-resizing the whole page to the browser width, that’s a bit trickier. If I just make everything bigger by default, it means less info fits on the screen for most people. But don’t worry, I’ll definitely keep your feedback in mind for future updates. I’ll try to find a good balance. And I’ll be thinking of you when I work on it, haha !
The page resizing works when the browser window is made smaller. It just stops to fill the page when you make the browser window larger, which on a 1920x1080 screen or larger, means that the page will stop filling the width of the browser. On a 2560 width desktop, thats almost 1/2 the page blank. 4k screen you get teeny tiny graph that is only about 1/8 the screen width.
I thought this may be a limit placed in the html code that is just preventing the page from expanding beyond a certain width. Looking at the page source, is that not what controls it?
.container { max-width: 1400px;
[edit] I checked the .sh file and found that exact line in the code. I changed it to a 4K screen width (3840) and the web page will now “resize” up to that screen width. However, the images don’t resize because of the default 300x200 limit, so I increased those to 1920x1080 and they display just fine, filling up the screen as expected. [/edit]
Ah! Sorry if I didn’t catch you quick enough, but maybe you can add an option for the container width after the image size.
WIDTH=800 ## Width of the generated graphs
HEIGHT=300 ## Height of the generated graphs
Container_width=1400 ##Maximum allowed display width of page
And add some information or recommended settings to use on your git page so that the user could change the values to work with thier setup. Since I run with a 4K and 1440p screen, I’m using
WIDTH=1920 ## Width of the generated graphs
HEIGHT=1080 ## Height of the generated graphs
Container_width=3840 ##Maximum allowed display width of page
This allows the images to fill the screen when clicked on, and also fill the width when the full page is viewed.
Hello,
I didn’t know that it as this look on other resolution.
So i just pushed an update where I added a new variable:
DISPLAY_PRESET="4k" # Preset for large screens. Options: default | 2k | 4k
Now the main container width and the graphs resize dynamically based on that preset, so you don’t have to manually edit WIDTH=800 / HEIGHT=300 anymore. Just pick the preset that matches your screen (default, 2k, or 4k) and it should scale everything properly (entire webpage + graph).
Big thank you for this suggestion ! @Mpegger (if you see anything else to improve I am here)