Age | Commit message (Collapse) | Author | Files | Lines |
|
Stating we accept donations without mentioning how to initiate them
doesn't make much sense.
|
|
Apply a few fixes and improvements throughout the text.
|
|
Clarify the purpose of the staging area, and (try to) improve the "Basic
Concepts" section in another few ways.
|
|
This text was written a few years ago, when we switched from SVN to Git.
These days, it makes less sense to assume the reader is accustomed to
SVN but not to Git.
|
|
While we provide and document our source tarball, we should clarify that
we recommend using distribution-provided binary packages whenever
possible.
|
|
The Nagios Plugin Development Guidelines are referenced on the main
Documentation page (and elsewhere), so there's no need to also mention
them on the Development page.
|
|
Import most of the FAQ entries from our old web site. A few outdated
questions have been omitted, many of the imported ones were updated in
one way or another, and the order of the development-related questions
has been changed. Also, the phrasing of some questions has been
modified (just to make the headings shorter).
For the record, this is the original list of questions from the old web
site:
General
-------
* Who controls the Nagios Plugins project?
* What license is Nagios Plugins distributed under?
* Who owns the copyright for the Nagios Plugin code?
* Can I submit a patch to this project?
* Do you accept donations?
Compiling
---------
* ./configure appears to hang
* check_ldap, check_radius or check_pgsql don't compile even though
configure output says the required libraries are present
* How come check_http/check_tcp doesn't work with --ssl?
* How do I compile the Nagios::Plugin perl module?
* I can't compile check_mysql on solaris
* I get '":types" is not exported by the Params::Validate module' when
running tests
* Why does Solaris use pst3 for check_procs?
Installing
----------
* Some of the root plugins (check_dhcp and check_icmp) haven't been
installed. What's happening?
* Why aren't my plugins installed as the nagios user? And what about
root plugins?
Development
-----------
* How do I use Git?
* Can I add extra tests to the C routines?
* Can I use the Nagios Plugins in my own project?
* How can I find out more about writing a plugin?
* How do I make changes on nagiosmib?
* How do I prove the C routines work?
* How do I use and update Gnulib?
* How do I use the Nagios::Plugin perl module?
* How do the test parameters in NPTest.pm work?
* Private C APIs
|
|
Don't start a new paragraph for the list of mirrors.
|
|
Add an FTP server from Portugal and one from the United States to our
list of mirrors.
|
|
Add the FTP mirrors from Argentina, Belgium, Greece, New Zealand, and
Korea.
|
|
Don't repeat "check"/"checking" that often.
|
|
Add ftp://mirror.bytemark.co.uk/nagios-plugins/ to our list of mirrors.
|
|
Add ftp://mirror.mephi.ru/nagios-plugins/ to our list of mirrors.
|
|
Mention the new FTP mirrors on download.md, and reference that from
doc/presentation.md.
|
|
|
|
... to improve readability a little bit.
|
|
|
|
|
|
Add a link to the /download/mib directory.
|
|
Compared to the Plugins tarballs, the NagiosMIB tarballs aren't all that
popular, so let's hide them away in a subdirectory.
|
|
|
|
|
|
|
|
Some of the contents were imported from our old web site, and that was
launched in 2008.
|
|
|
|
Fix a few small typos and apply various cosmetic changes.
|
|
On narrow displays, replace the menu bar with a simple list of items,
and omit the GitHub ribbon.
|
|
Add appropriate attributes to the RSS and Twitter links on our News
page(s).
|
|
Add a <link> tag that mentions our RSS feed.
|
|
Version 1.4.16 was released in 2012, not in 2013.
|
|
Mention the names of news articles authors, as we did on the old web
site.
|
|
Many sites have links to our New Threshold Syntax proposal, so lets put
it back online. However, as we decided not to implement the New
Threshold Syntax anytime soon, we currently don't add a link to the
proposal on our own web site.
|
|
The hyphenation support in current browser versions isn't all that good.
As the text lines on our web site are long (actually too long), there's
no need for hyphenation anyway.
|
|
When setting "padding: 0.6em" for the menu elements, certain versions of
Chrome and WebKitGTK+ render the light blue menu item a tad larger than
the rest of the menu bar. (This only happened when the site was
accessed for the first time. Reloading the current page or following a
link to another document on the Nagios Plugins site fixed the issue.)
Using 0.625em works around this problem.
Note that the issue is not related to using the "em" unit: It also shows
up when specifying 9.6px (and is fixed by specifying 10px).
|
|
Seperate the documents that cover "advanced" topics more clearly from
the basic documentation.
|
|
None of the Nagios Plugins developers are currently in #Icinga, and I'm
not sure the Icinga guys are keen on providing support for the Plugins.
|
|
Add links to the Nagios Plugin Develepment Guidelines and to the
Extra-Opts documentation.
|
|
Testing the current snapshot is purely optional, searching the issue
tracker less so.
|
|
Not sure whether we'll actually send announcements to all lists in the
future.
|
|
The mailing lists were moved from SourceForge to the project server.
|
|
|
|
The text between <object> and </object> is not interpreted as Markdown.
|
|
The foreground color is black by default.
|
|
We don't have the "RSS and Twitter box" (which had a gray background)
anymore.
|
|
|
|
The <guid> and <pubDate> contents were swapped again. (The same bug had
been fixed in an earlier commit and was then reintroduced by accident.)
|
|
Strip trailing whitespace from news teasers to make sure the "Read more"
link doesn't go onto a new paragraph.
|
|
|
|
Use RSS and Twitter icons from <http://www.designdeck.co.uk/a/1239>.
|
|
Move the RSS and Twitter buttons into the (right edge of the) menu bar.
|