similar to: Documentation inside git

Roger Price <roger at rogerprice.org> writes: > On Sun, 2 Jun 2024, Jim Klimov wrote: > >> Trying to remember the context: is your book only rendered as a PDF >> (a "release" of which on GitHub the NUT site currently points to), >> or are there also HTML renditions to point to this way (to see in a >> typical browser)? > > Sorry, I did not

The pieces should all be there, I think. NUT source iterations cooperate with the sister nut-website repo on github, as well as nut-ddl and some more, to produce an horde of static HTML pages, and PDF versions of some docs, tarballs, etc. which are pushed to a repo for "github pages" and with their magic (I guess GH spins up a container with a web server and many data files for each new

Now back to computers - so re-checked some bits. The existing https://networkupstools.org/documentation.html page offers currently the https://github.com/networkupstools/ConfigExamples/releases/latest/ URL as "NUT Configuration Examples <https://github.com/networkupstools/ConfigExamples/releases/latest> book maintained by Roger Price" This in turn redirects to a particular newest

Hello Jim, I would like to be able to refer to the configuration examples without having to point to my own site. But the link at https://networkupstools.org/documentation.html points to a github.com site which offers the documentation as a download rather than an immediate screen display. I do not understand git, and I would be much more comfortable pointing to an HTML display directly from

Make your customers and visitors always have the link to your site on their Explorer toolbar. Custom Toolbars increase your ability to market your site anywhere within millions of Internet browsers and takes only seconds to install. Custom IE Toolbar with unlimited menu items - 200$US! Advanced IE Toolbar with custom design logo - 250$US! Unlimited IE Toolbar features with the plain rate of

Also for i2c specifically, you can look at examples in asem and recently pijuice drivers. Hope this helps, Jim Klimov On Wed, Nov 18, 2020, 11:25 Roger Price <roger at rogerprice.org> wrote: > On Thu, 5 Nov 2020, Nick Ellson wrote: > > > I searched the forum from the website and didn’t get any hits, so I > thought I’d ask here. > > I have an RPi 4B running Home

Errata coming up for NUT v2.8.2: * it was discovered that the nut-driver-enumerator (NDE) script had a regression which caused it to not reload nut-driver instances (systemd, SMF) when `ups.conf` edits happened. * on a related note, it may be possible that "live" driver reloading (at least on master branch) does not reduce debug verbosity to zero when `debug_min 0` is active in its

Errata coming up for NUT v2.8.2: * it was discovered that the nut-driver-enumerator (NDE) script had a regression which caused it to not reload nut-driver instances (systemd, SMF) when `ups.conf` edits happened. * on a related note, it may be possible that "live" driver reloading (at least on master branch) does not reduce debug verbosity to zero when `debug_min 0` is active in its

The trip to FOSDEM 2025 was great fun, with many interactions, useful lectures and fruitful conversations. It was insightful to randomly meet at least one person using the project, a few eager to use and asking question, and sadly quite a few who did not recognize not only "NUT" but also "UPS" key words. Face-to-face talks to maintainers of Debian, OpenIndiana, Tribblix and

The trip to FOSDEM 2025 was great fun, with many interactions, useful lectures and fruitful conversations. It was insightful to randomly meet at least one person using the project, a few eager to use and asking question, and sadly quite a few who did not recognize not only "NUT" but also "UPS" key words. Face-to-face talks to maintainers of Debian, OpenIndiana, Tribblix and

On Tue, 13 Jun 2017, Charles Lepple wrote: > On Jun 9, 2017, at 10:16 AM, Roger Price wrote: >> To address this, I propose a "NUT configuration for Noobs" which is >> called "Configuration Examples". > I am also curious whether you tried to edit any of the existing NUT > documentation before creating a new document. We chose AsciiDoc in part >

On Tue, 11 Jul 2017, Jim Klimov wrote: > On July 5, 2017 9:55:13 AM GMT+02:00, Roger Price <roger at rogerprice.org> wrote: >> I propose adding the sentence >> >> "If more than one AT matches the notifytype and upsname, the AT >> declarations are executed in the order in which they appear in >> upssched.conf. > > Your proposal and reasoning make

Many years ago, my sister asked me to look at the Google <a href="http://images.google.com/">Images search</a> . When I first saw the page, I thought Google was offering a place for freebie photos before I realized that it was probably searching for and finding the "alt tag" text written in the HTML for website images. "Alt tags" or "alt text"

On Fri, 16 Sep 2022, Jim Klimov via Nut-upsuser wrote: > Hello all, > ? Here's a PR I want to ask community about: should NUT clients like upsc report (log!) or hide the infamous 'Init SSL without certificate > database' message? How should upsc be used in order to get SSL/TLS protection? There is no configuration file with a CERTFILE declaration. Is there some other way

On Fri, 16 Sep 2022, Jim Klimov via Nut-upsuser wrote: > Hello all, > ? Here's a PR I want to ask community about: should NUT clients like upsc report (log!) or hide the infamous 'Init SSL without certificate > database' message? How should upsc be used in order to get SSL/TLS protection? There is no configuration file with a CERTFILE declaration. Is there some other way

So... April 1st came and went, busy with last-minute warnings from a newly set-up NetBSD build agent for the NUT CI farm, as Greg-inspired warnings exposed by the stricter platform kept popping up and biting. Led to some discoveries in toolkits and standards I thought I knew for decades, too. So it was a tad bit annoying, but good overall :) But now we are a day over the hopeful "not more

So... April 1st came and went, busy with last-minute warnings from a newly set-up NetBSD build agent for the NUT CI farm, as Greg-inspired warnings exposed by the stricter platform kept popping up and biting. Led to some discoveries in toolkits and standards I thought I knew for decades, too. So it was a tad bit annoying, but good overall :) But now we are a day over the hopeful "not more

On Fri, 28 May 2021, Jim Klimov via Nut-upsdev wrote: > ? Looking at NUT pull request (PR) history on GitHub, I see that we have > had a non-trivial number of stalled driver contributions sharing a prominent > similarity: proposed names for some of the variables did not fit into the list > defined at https://github.com/networkupstools/nut/blob/master/docs/nut-names.txt > ? I

On Fri, 28 May 2021, Jim Klimov via Nut-upsdev wrote: > ? Looking at NUT pull request (PR) history on GitHub, I see that we have > had a non-trivial number of stalled driver contributions sharing a prominent > similarity: proposed names for some of the variables did not fit into the list > defined at https://github.com/networkupstools/nut/blob/master/docs/nut-names.txt > ? I

My thought of #2 require none of that . . . I have a server with two supplies, and two UPS units. One supply is on each UPS, and clients are distributed otherwise to balance. The main thing is to ensure that it is documented accurately how to config so that the server only shuts down when the *second* unit hits low battery . . . I found the info on this topic almost nonexistent at present . . .