sql-ledger-users

Receipting payments at the account level

[Tony G. <to...@go...>]

We have what seems to be a unique requirement not handled by the common
entry-level business accounting software, so we thought we'd check the
response from the major  open source packages.

We have no trouble CREATING invoices with amounts against multiple
receivable accounts.  However, the payment receipt process ends at the
invoice level, not the account level.  So, for example, we know that
Customer X has an outstanding balances on invoices 109 and 234, but we don't
know their balance on the "Hardware sales" and "Billable services" accounts
which each of those invoices included.

Can SQL-Ledger do this?  If not, does anyone else see this as useful?

Advice on Apache

[Wayne <inf...@pi...>]

Hi All,
I'm getting ready to download Apache and
wasn't sure what I should download. Do
I download the httpd or the one in the perl
tree? I never installed Apache before.
Thanks.
Wayne

Re: Advice on Apache

[Rod R. <ro...@su...>]

What OS?  Most Linux distributions come with Apache included.
You might find it easier to upgrade to something like Red Hat
7.1 than try to figure out installation of Postgres, DBI, DBD,
Apache, etc.

Or if you like I'll sell you a Linux box with sql-ledger ready
to go.  :-)

-- Rod
    http://www.sunsetsystems.com/

Wayne wrote:

> Hi All,
> I'm getting ready to download Apache and
> wasn't sure what I should download. Do
> I download the httpd or the one in the perl
> tree? I never installed Apache before.
> Thanks.
> Wayne

Re: Advice on Apache

[John S. <js...@im...>]

>Hi All,
>I'm getting ready to download Apache and
>wasn't sure what I should download. Do
>I download the httpd or the one in the perl
>tree? I never installed Apache before.
>Thanks.
>Wayne

Hi there,

Downloading apache is no problem at all, no matter what os. It's not 
a really big download either. Just saunter over to 
http://httpd.apache.org/dist/httpd/ and download source for 1.3.19 or 
1.3.20 (latest).

Untar, check out the README files, ./configure, make and make 
install; that's all there is to it, your set to go!

Although I think its more fun to roll your own, there is a binaries 
directory too, where most oss are represented. Just name your poison.

However, if you're running a particular linux or bsd distribution, 
look for the apache package, deb, rpm on your os vendor's website. 
It's probably less painful that way.

Enjoy ...




John Stoddart
Caracas - Venezuela

Re: Advice on Apache

[German D. <g_d...@ya...>]

Download the apache server version 1.3.39 and then go
to the perl site and download the perl-dbi and DB.
Jerry
--- John Stoddart <js...@im...> wrote:
> >Hi All,
> >I'm getting ready to download Apache and
> >wasn't sure what I should download. Do
> >I download the httpd or the one in the perl
> >tree? I never installed Apache before.
> >Thanks.
> >Wayne
> 
> Hi there,
> 
> Downloading apache is no problem at all, no matter
> what os. It's not 
> a really big download either. Just saunter over to 
> http://httpd.apache.org/dist/httpd/ and download
> source for 1.3.19 or 
> 1.3.20 (latest).
> 
> Untar, check out the README files, ./configure, make
> and make 
> install; that's all there is to it, your set to go!
> 
> Although I think its more fun to roll your own,
> there is a binaries 
> directory too, where most oss are represented. Just
> name your poison.
> 
> However, if you're running a particular linux or bsd
> distribution, 
> look for the apache package, deb, rpm on your os
> vendor's website. 
> It's probably less painful that way.
> 
> Enjoy ...
> 
> 
> 
> 
> John Stoddart
> Caracas - Venezuela
> 


__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail
http://personal.mail.yahoo.com/

Re: Advice on Apache

[Wayne <inf...@pi...>]

Thanks for the input John. I download Apache 1.3.20 and
after reading the INSTALL instruction I'm not sure
whether I should install mod_perl first or if I can do it
after installing Apache.
Wayne

John Stoddart wrote:

> >Hi All,
> >I'm getting ready to download Apache and
> >wasn't sure what I should download. Do
> >I download the httpd or the one in the perl
> >tree? I never installed Apache before.
> >Thanks.
> >Wayne
>
> Hi there,
>
> Downloading apache is no problem at all, no matter what os. It's not
> a really big download either. Just saunter over to
> http://httpd.apache.org/dist/httpd/ and download source for 1.3.19 or
> 1.3.20 (latest).
>
> Untar, check out the README files, ./configure, make and make
> install; that's all there is to it, your set to go!
>
> Although I think its more fun to roll your own, there is a binaries
> directory too, where most oss are represented. Just name your poison.
>
> However, if you're running a particular linux or bsd distribution,
> look for the apache package, deb, rpm on your os vendor's website.
> It's probably less painful that way.
>
> Enjoy ...
>
> John Stoddart
> Caracas - Venezuela

Re: Advice on Apache

[John S. <js...@im...>]

>I download Apache 1.3.20 and after reading the INSTALL instruction 
>I'm not sure whether I should install mod_perl first or if I can do 
>it after installing Apache.

If my memory serves me rightly, you should have apache installed 
first. You can find latest mod_perl at 
http://perl.apache.org/dist/mod_perl-1.26.tar.gz

When you untar, locate the INSTALL.simple file, which will give you 
an overview of the whole process. The INSTALL file goes through the 
process thoroughly.

Good luck


John

Re: Advice on Apache

[Jose R. A. <jos...@ho...>]

Hi guys.

I've been following this thread and i think noone has told you about
www.apachetoolbox.com, it might be the best approach for your needs, take a
look at the site and smile for a while as you see all your troubles vanish away.

Have a nce day.

-- 

Jose Rodriguez Alarcon
http://hostinglabs.com
jos...@ho...

On Thu, 12 Jul 2001, you wrote:
> >I download Apache 1.3.20 and after reading the INSTALL instruction 
> >I'm not sure whether I should install mod_perl first or if I can do 
> >it after installing Apache.
> 
> If my memory serves me rightly, you should have apache installed 
> first. You can find latest mod_perl at 
> http://perl.apache.org/dist/mod_perl-1.26.tar.gz
> 
> When you untar, locate the INSTALL.simple file, which will give you 
> an overview of the whole process. The INSTALL file goes through the 
> process thoroughly.
> 
> Good luck
> 
> 
> John

Re: Advice on Apache

[Jonas S. <dr...@jo...>]

On Thu, 12 Jul 2001, Wayne wrote:

 > Thanks for the input John. I download Apache 1.3.20 and after reading
 > the INSTALL instruction I'm not sure whether I should install mod_perl
 > first or if I can do it after installing Apache.

Forget about mod_perl. For SQL-Ledger you need Apache and perl, not
apache+perl.

mod_perl is for embedding perl commands in html - like server side
includes or php. SQL-Ledger is perl CGI-scripts, not embedded perl.

Hope that clears up the confusion a bit :-)

  - Jonas

--
Jonas Smedegaard <jo...@jo...> http://dr.jones.dk/~jonas/ +45 40843136
Spiff ApS (aka. IT-guide dr. Jones ApS) <dr...@jo...> http://dr.jones.dk/
Debian GNU/Linux <js...@de...> http://www.debian.org/ fngrprn: C02440B8

GNU GPL: "The source will be with you... always."

Re: Advice on Apache

[Roderick A. A. <raa...@ti...>]

On Thu, 12 Jul 2001, Jonas Smedegaard wrote:

> On Thu, 12 Jul 2001, Wayne wrote:
> 
>  > Thanks for the input John. I download Apache 1.3.20 and after reading
>  > the INSTALL instruction I'm not sure whether I should install mod_perl
>  > first or if I can do it after installing Apache.

You might look for the apache-heavy package - statically linked in
mod_perl (and other modules if you want). There are RPMs (which is what
I use) but I'm not sure about a tarball or other package managers.

> Forget about mod_perl. For SQL-Ledger you need Apache and perl, not
> apache+perl.
> 
> mod_perl is for embedding perl commands in html - like server side
> includes or php. SQL-Ledger is perl CGI-scripts, not embedded perl.

Actually I think you're thinking of embperl.  Mod_perl loads a perl
interpreter into Apache.  The main benefit being quicker startup of perl
scripts.  Instead of Apache making a system call to the script which
starts perl which reads the rest of the script file to execute; mod_perl
gets reads the script to execute (or it will already be there from a
previous call).  Things happen faster.

   For a lightly loaded server (hardware and software wise) it isn't
really needed but on a system running multiple companies which may have
multiple users connected at the same time the response times would be
much better.

I'm not sure if the SQL-Ledger code supports Apache::DBI but it is my
understanding that this in conjunction with mod_perl will make a
significant response time difference.

The short of it is mod_perl isn't needed for light/normal usage.


Rod
-- 
                 Remove the word 'try' from your vocabulary ... 
                     Don't try.  Do it or don't do it ...
                                Steers try!

                                                            Don Aslett

Re: Advice on Apache

[Wayne <inf...@pi...>]

Thanks for all the replys. After doing further reading
I came to the conculsion that I didn't need mod_perl.
I have Apache now installed. now for DBI.
Wayne

"Roderick A. Anderson" wrote:

> On Thu, 12 Jul 2001, Jonas Smedegaard wrote:
>
> > On Thu, 12 Jul 2001, Wayne wrote:
> >
> >  > Thanks for the input John. I download Apache 1.3.20 and after reading
> >  > the INSTALL instruction I'm not sure whether I should install mod_perl
> >  > first or if I can do it after installing Apache.
>
> You might look for the apache-heavy package - statically linked in
> mod_perl (and other modules if you want). There are RPMs (which is what
> I use) but I'm not sure about a tarball or other package managers.
>
> > Forget about mod_perl. For SQL-Ledger you need Apache and perl, not
> > apache+perl.
> >
> > mod_perl is for embedding perl commands in html - like server side
> > includes or php. SQL-Ledger is perl CGI-scripts, not embedded perl.
>
> Actually I think you're thinking of embperl.  Mod_perl loads a perl
> interpreter into Apache.  The main benefit being quicker startup of perl
> scripts.  Instead of Apache making a system call to the script which
> starts perl which reads the rest of the script file to execute; mod_perl
> gets reads the script to execute (or it will already be there from a
> previous call).  Things happen faster.
>
>    For a lightly loaded server (hardware and software wise) it isn't
> really needed but on a system running multiple companies which may have
> multiple users connected at the same time the response times would be
> much better.
>
> I'm not sure if the SQL-Ledger code supports Apache::DBI but it is my
> understanding that this in conjunction with mod_perl will make a
> significant response time difference.
>
> The short of it is mod_perl isn't needed for light/normal usage.
>
> Rod
> --
>                  Remove the word 'try' from your vocabulary ...
>                      Don't try.  Do it or don't do it ...
>                                 Steers try!
>
>                                                             Don Aslett

Re: Advice on Apache

[John S. <js...@im...>]

>Thanks for all the replys. After doing further reading
>I came to the conculsion that I didn't need mod_perl.
>I have Apache now installed. now for DBI.
>Wayne
>
>"Roderick A. Anderson" wrote:
>
>>  On Thu, 12 Jul 2001, Jonas Smedegaard wrote:
>>
>>  > On Thu, 12 Jul 2001, Wayne wrote:
>>  >
>>  >  > Thanks for the input John. I download Apache 1.3.20 and after reading
>>  >  > the INSTALL instruction I'm not sure whether I should install mod_perl
>>  >  > first or if I can do it after installing Apache.
>>
>>  You might look for the apache-heavy package - statically linked in
>>  mod_perl (and other modules if you want). There are RPMs (which is what
>>  I use) but I'm not sure about a tarball or other package managers.
>>
>>  > Forget about mod_perl. For SQL-Ledger you need Apache and perl, not
>>  > apache+perl.
>>  >
>>  > mod_perl is for embedding perl commands in html - like server side
>>  > includes or php. SQL-Ledger is perl CGI-scripts, not embedded perl.
>>
>>  Actually I think you're thinking of embperl.  Mod_perl loads a perl
>>  interpreter into Apache.  The main benefit being quicker startup of perl
>>  scripts.  Instead of Apache making a system call to the script which
>>  starts perl which reads the rest of the script file to execute; mod_perl
>>  gets reads the script to execute (or it will already be there from a
>>  previous call).  Things happen faster.
>>
>>     For a lightly loaded server (hardware and software wise) it isn't
>>  really needed but on a system running multiple companies which may have
>>  multiple users connected at the same time the response times would be
>>  much better.
>>
>>  I'm not sure if the SQL-Ledger code supports Apache::DBI but it is my
>>  understanding that this in conjunction with mod_perl will make a
>>  significant response time difference.
>>
>  > The short of it is mod_perl isn't needed for light/normal usage.

This thread has raised an interesting point regarding Doug 
MacEachern's mod_perl, a truly powerful resource. Apparently, it's so 
popular that many CGI developers have switched to circumnavigate 
mod_cgi's shortcomings. Statistics at 
http://perl.apache.org/netcraft/ show it in use on over 2 million 
server installations.

Obviously there is an advantage to mod_perl's persistence, speeding 
up response processing significatively (I've seen claims of 
improvements in the order of 10 to 100 times!, depending on code) in 
exchange for a bit more RAM. This is clearly a usable benefit!

Where do you all think mod_perl can fit into sql-ledger's scheme of things?



John

Re: Advice on Apache

[Mark T. <ma...@fr...>]

> Obviously there is an advantage to mod_perl's persistence, speeding 
> up response processing significatively (I've seen claims of 
> improvements in the order of 10 to 100 times!, depending on code) in 
> exchange for a bit more RAM. This is clearly a usable benefit!
> 
> Where do you all think mod_perl can fit into sql-ledger's scheme of things?

It probably doesn't need to for the vast majority of SQL-Ledger users:

We do virtual-hosting and have offered mod_perl on our servers for several years now. Our own e-commerce stuff 
and anything else that will generate large numbers of hits is built in Perl/mod_perl. mod_perl is probably one of the 
single most powerful technologies available to web developers using Perl.

mod_perl integrates the Perl language interpreter into the Apache web server. This has two main advantages:

1. the developer gets access to the Apache API via Perl, allowing Apache modules (or handlers) to be written in Perl
2. Perl scripts can run as Apache::Registry scripts, meaning they are parsed, compiled and executed in the         
Apache process itself.

Once a script has been parsed and compiled into the Apache parent process (preferably at Apache start-up) the 
next request that calls the script is answered from the compiled version cached by Apache. This means the 
overhead of starting a Perl process, parsing and compiling the script for each request is avoided. The result is 
performance that comes close to that of compiled C-code in many cases.

So, mod_perl is used for speed and power by folks that use Perl. But, for applications like SQL-Ledger its benefits 
are likely to be minimal at best (unless the same system is being used by many users simultaneously).

There are a couple of caveats when using mod_perl. But they do help enforce good coding practices. Because the 
Perl scripts/handlers/Apache-modules are persistent name-spaces and variable-scoping become critical. A global 
variable will be shared by all Apache processes that handle requests for a particular script. mod_perl Apache 
processes can be pretty large. On modern systems this is usually not a problem. On a busy server it is generally 
preferable to have an Apache child process using 10MB-RAM (a lot is shared memory on OS's like Linux) than to 
fork and exec a new Perl process for every hit to a frequently requested resource.

There is no harm in using a mod_perl capable server to run SQL-Ledger since Perl scripts can always be run as 
standard CGI processes. The Apache configuration can control the use of mod_perl on a per-file/script basis.

For more info see:
http://perl.apache.org/guide/

Mark

Mark Tiramani
FREDO Internet Services
ma...@fr...

Re: Advice on Apache

[John S. <js...@im...>]

>On Thu, 12 Jul 2001, Wayne wrote:
>
>>  Thanks for the input John. I download Apache 1.3.20 and after reading
>>  the INSTALL instruction I'm not sure whether I should install mod_perl
>>  first or if I can do it after installing Apache.
>
>Forget about mod_perl. For SQL-Ledger you need Apache and perl, not
>apache+perl.

You're totally right of course, sql-ledger wants a web server and the 
perl language.

mod_perl is an apache loadable module that implements the perl 
language. I don't know how it fits into Wayne's general plan, which 
is why I didn't comment.

Thanks for clearing up that omission!




John