From: Michael Tremer <michael.tremer@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Re: haproxy, miniupnpd, nginx
Date: Sat, 04 Apr 2015 14:50:51 +0200 [thread overview]
Message-ID: <1428151851.3063.74.camel@ipfire.org> (raw)
In-Reply-To: <550FD83F.6040702@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2675 bytes --]
HAProxy is done: http://wiki.ipfire.org/en/addons/haproxy
On Mon, 2015-03-23 at 10:09 +0100, Daniel Weismüller wrote:
> Hi
>
> It was not my opinion that we need a complete documentation for each
> addon.
> Just as you said we need only a documentation which discribes the most
> important parts.
>
> What do this addon? How to install? Where can I find further
> informations or documentations?
>
> miniupnpd: You worked on it. ;-)
> http://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=a898e4cba75ad166863f928a30f7af454670579a
>
> - Daniel
>
> Am 22.03.2015 um 22:25 schrieb Michael Tremer:
>
> > Hi,
> >
> > indeed I guess we should have some documentation about these add-ons.
> > However I think that it does not make that much sense to copy stuff that
> > is documented somewhere else. That means that this documentation is more
> > of a stub than something proper.
> >
> > I recently added haproxy which is not in the stable tree, yet. I will
> > add some basic configuration examples but still link to other sources
> > which explain it more in depth. There is nothing IPFire-specific to it
> > at all. However it is good to have a starting point.
> >
> > I think I remember that Ben added nginx and I have no clue who added
> > miniupnpd. Could have been me. I also do not really know in which state
> > this package is right now and if it should not better be removed.
> >
> > It would help if you could find out who worked on these add-ons and add
> > CC them to ask if they would like to complete the documentation.
> >
> > -Michael
> >
> > On Sun, 2015-03-22 at 10:44 +0100, Daniel Weismüller wrote:
> > > All these addons were recently updated but there are no informations
> > > about it in our wiki.
> > >
> > > It would be very fine if someone could write a few words about it.
> > >
> > > What is it?
> > > What my a user do with it?
> > > How to use it?
> > >
> > > -
> > > Daniel
> > >
> > > ---
> > > Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
> > > http://www.avast.com
> > >
> > > _______________________________________________
> > > Development mailing list
> > > Development(a)lists.ipfire.org
> > > http://lists.ipfire.org/mailman/listinfo/development
> > >
> > >
> > > _______________________________________________
> > > Documentation mailing list
> > > Documentation(a)lists.ipfire.org
> > > http://lists.ipfire.org/mailman/listinfo/documentation
>
> _______________________________________________
> Documentation mailing list
> Documentation(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/documentation
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next parent reply other threads:[~2015-04-04 12:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <550FD83F.6040702@ipfire.org>
2015-04-04 12:50 ` Michael Tremer [this message]
2015-04-04 20:07 ` Daniel Weismüller
[not found] <FB9D4E4C-B2BE-405A-B56B-3BB781234F37@beert.de>
2015-03-22 21:46 ` Michael Tremer
[not found] <550E8F19.4060505@ipfire.org>
2015-03-22 21:25 ` Michael Tremer
2015-03-22 10:10 Daniel Weismüller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1428151851.3063.74.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=documentation@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox