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: IPTraffic porting
Date: Fri, 11 Dec 2020 10:14:46 +0100	[thread overview]
Message-ID: <929D0183-4594-4AEE-A5D1-BBEEA90EA22F@ipfire.org> (raw)
In-Reply-To: <b0d603fa47694c137af7500b3ca2c56ba274b8b1.camel@cybermainzel.de>

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

Hello Frank,

> On 6 Dec 2020, at 14:57, Frank Mainz <frank(a)cybermainzel.de> wrote:
> 
> Hi folks,
> 
> as already written in the forum, I have ported my IPTraffic addon for
> IPFire.

You have come to the right place here. The forum is mainly a support forum.

> A few questions are still open. I hope you will help me.

Yes, absolutely.

But first from me: What is the IPTraffic add-on?

> The cronjob is okay. 
> Now I wonder if I should create the bash-installer as perl-script.

Why? I would prefer shell because we have a small library that we load for common functionality like starting a service, etc.

> I can't figure out the git-links. I see the code, but don't understand
> how it can help me.

Please explain the problem you are trying to solve and I hope I can help to come up with a solution.

> How to insert the code for the menu where?

There are files in config/menu. Have a look at the files beginning with EX-. Those are add-ons.

> How the language file should look like is clear, but how do I get it
> inserted in the system?

Have a look at lfs/squid-accounting. That script installs files from src/squid-accounting to /var/ipfire/addon-lang.

You can do the same and run /usr/local/bin/update-lang-cache in the install.sh script.

> Thanks in advance for your help.
> Frank

Let me know if this has helped.

Best,
-Michael

      reply	other threads:[~2020-12-11  9:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-06 13:57 Frank Mainz
2020-12-11  9:14 ` Michael Tremer [this message]

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=929D0183-4594-4AEE-A5D1-BBEEA90EA22F@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