public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Porting ipcop addons
Date: Fri, 12 Jan 2018 12:34:58 +0000	[thread overview]
Message-ID: <1515760498.3647.52.camel@ipfire.org> (raw)
In-Reply-To: <p32ndn$anv$1@tuscan3.grantura.co.uk>

[-- Attachment #1: Type: text/plain, Size: 2337 bytes --]

Hey Bob,

thanks for getting in touch.

I had no idea that too many people are still active around the IPCop community,
but welcome to IPFire.

I guess this would be a great addition to IPFire although I could not find out
which modems are supported. Is there any (bigger?) ISP handing out any
compatible ones?

I had a look at the code that you linked and that looks quite good. It's clean
and tidy and I think porting that over would not be too hard. However, we don't
run the perl scripts any more to collect stats. We use collectd in IPFire 2.

Since we should not run the cron job to collect data for every since even when
it doesn't have a compatible device, we should make this an add-on.

What you will need to do is check out the build system as described here:

  https://wiki.ipfire.org/devel/ipfire-2.x/build-howto

Then you would have to create a file called lfs/adslmonitor or something similar
and roughly follow these steps:

  https://wiki.ipfire.org/devel/ipfire-2.x/addon-howto

I guess a good example to follow would be guardian which is also an add-on
written in perl:

  https://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=lfs/guardian;h=f3001c82128f3ba08290eea295b87cf342f65590;hb=HEAD

To add a button to the navigation, you will have to add a file with some
information to /var/ipfire/menu.d. They are here in the source:

  https://git.ipfire.org/?p=ipfire-2.x.git;a=tree;f=config/menu;h=64cd8c17713574e84a7012803f3261b8a8e81801;hb=HEAD

Just dropping a file into that directory will do it.

I hope that this gives you some good guidance. If you have any further questions
please ask at any time.

Best,
-Michael

On Tue, 2018-01-09 at 15:34 +0000, Bob Brewer wrote:
> Hi
> 
> I am the author of the adslmonitor addon for ipcop 
> (https://sourceforge.net/projects/adslmonitor/) 
>  and looking at porting it to ipfire. 
> 
> I assume that I would need to use Pakfire to install the addon but I have so 
> far been unsuccessful in finding any documentation that would help me modify 
> the ipcop addon to be compatible with Ipfire (eg the Ipfire equivalent of 
> the Ipcop command  updatemenu.pl which adds the adslmonitor perl scripts to 
> the cgi menus).
> 
> Could someone could point me to the relevant documentation.
> 
> Kind Regards
> 
> Bob

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-01-12 12:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-09 15:34 Bob Brewer
2018-01-12 12:34 ` Michael Tremer [this message]
2018-01-12 18:53   ` Bob Brewer

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=1515760498.3647.52.camel@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@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