It is a completely and utterly false statement that we attempt to make the software difficult to install on purpose. The documentation is resonably straightforward for any competant sysadmin, and all prerequisites ARE listed. The documentation is in a Wiki if folks from the community would like to help improve it for a more novice-oriented audience.
We even provide a completely installed and functional VMware appliance with each release, for folks who have difficulty installing from source code but who would still like to evaluate or use the software.
May I respectfully ask that you consider saving the vitrol for companies that ACTUALLY falsely represent themselves as "open source" while having pro versions, proprietary plugins and other such nonsense? It seems a bit unfair to pick on a small company doing the best we can to employ people full-time writing 100% free software, just because a free installation tutorial wasn't handed to you on a silver platter.
GPL'd, web-based, double entry accounting system
for businesses. Full internationalization support
for several languages, currencies and chart of
accounts, written in Perl. Good stuff.
Webpage here
GNUCash is *not* a business accounting system.
It is a *personal* accounting system.
Hi, I'm the primary author of Freeside, so I
figured I'd give a try at responding here.
Security: "alot of suid scripts and suEXEC in
Apache" is incorrect. More properly, it's
suid *OR* suEXEC in Apache, *OR* one of the other
methods outlined in the installation instructions
for running Freeside as its own user - a security
precaution, something I wish more packages which
handle sensitive data did. I've been securing Internet servers for almost seven years now. Freeside
is extrememly carefully written, and has never
had a privledge-escallating security problem. *EVER*. (You may consider that a challenge)
On the topic of neatly packaging the "3rd party" modules: it's been done, it's called CPAN, the
Comprehensive Perl Archive Network, and it's really very slick: http://search.cpan.org/ Also, I'm just finishing up the Debian new maintainer process, and all of the modules that aren't currently.deb packaged are about to make their
way into Debian unstable, followed shortly by Freeside itself.
MySQL vs. PostgreSQL: The posters who pointed
out that transaction support is essential for financial transactions are
correct. Freeside has a Pg backend, and all
future development is focused on Pg, not MySQL.
Your other option for open-source ISP billing software, as the original poster asked: ISPD at
.
The irony of open-source _billing_ software:
I'm a vegetarian, too.
Real-time billing: One poster claimed that
"Telephony billing really needs to be real-time
rather than ISP billing which is just parse a load of scripts". The current CVS of Freeside
contains an SQL-based "session monitor" which
tracks user sessions in real-time.
The best resource for outage information is to subscribe to the inet-access mailing list [1] and read the reports from Sean Donelan, resident outage guru.
[1] You can subscribe to the (_very_ high volume) inet-access mailing list by sending 'subscribe' n the body of a message to 'list-request@inet-access.net'. Sorry, but this list is (deliberately) not archived online.
> Actually, I can think of some instances in which sound card drivers could be vital for a > web server. How about streaming audio over the 'net from a live sound source?
When you do live streaming audio, you use don't use your web server to encode the audio - you use a separate, dedicated machine for that. This is true for Real Audio as well as Shoutcast and the open-source Icecast.
(I'm not talking out my ass here - I geek for Technostate, an internet radio station that broadcasts live events.)
About two dozen small ISPs (including sonic.net) have signed the ISP Privacy Pledge
Does one of them serve your area? Perhaps you should consider giving them your business.
Reply to This
In the US, you can find a small ISP servicing your address at http://isp.ninja/
Hi,
I am the person interviewed in this video.
It is a completely and utterly false statement that we attempt to make the software difficult to install on purpose. The documentation is resonably straightforward for any competant sysadmin, and all prerequisites ARE listed. The documentation is in a Wiki if folks from the community would like to help improve it for a more novice-oriented audience.
We even provide a completely installed and functional VMware appliance with each release, for folks who have difficulty installing from source code but who would still like to evaluate or use the software.
May I respectfully ask that you consider saving the vitrol for companies that ACTUALLY falsely represent themselves as "open source" while having pro versions, proprietary plugins and other such nonsense? It seems a bit unfair to pick on a small company doing the best we can to employ people full-time writing 100% free software, just because a free installation tutorial wasn't handed to you on a silver platter.
Thanks.
Freeside (http://www.sisd.com/freeside) includes an integrated ticketing system based on RT, as well as invoicing, customer tracking and so on. HTH.
HTH
GPL'd, web-based, double entry accounting system
for businesses. Full internationalization support
for several languages, currencies and chart of
accounts, written in Perl. Good stuff.
Webpage here
GNUCash is *not* a business accounting system.
It is a *personal* accounting system.
Hi, I'm the primary author of Freeside, so I
.deb packaged are about to make their
figured I'd give a try at responding here.
Security: "alot of suid scripts and suEXEC in
Apache" is incorrect. More properly, it's
suid *OR* suEXEC in Apache, *OR* one of the other
methods outlined in the installation instructions
for running Freeside as its own user - a security
precaution, something I wish more packages which
handle sensitive data did. I've been securing Internet servers for almost seven years now. Freeside
is extrememly carefully written, and has never
had a privledge-escallating security problem. *EVER*. (You may consider that a challenge)
On the topic of neatly packaging the "3rd party" modules: it's been done, it's called CPAN, the
Comprehensive Perl Archive Network, and it's really very slick: http://search.cpan.org/ Also, I'm just finishing up the Debian new maintainer process, and all of the modules that aren't currently
way into Debian unstable, followed shortly by Freeside itself.
MySQL vs. PostgreSQL: The posters who pointed
out that transaction support is essential for financial transactions are
correct. Freeside has a Pg backend, and all
future development is focused on Pg, not MySQL.
Your other option for open-source ISP billing software, as the original poster asked: ISPD at
.
The irony of open-source _billing_ software:
I'm a vegetarian, too.
Real-time billing: One poster claimed that
"Telephony billing really needs to be real-time
rather than ISP billing which is just parse a load of scripts". The current CVS of Freeside
contains an SQL-based "session monitor" which
tracks user sessions in real-time.
The best resource for outage information is to
subscribe to the inet-access mailing list [1] and
read the reports from Sean Donelan, resident
outage guru.
[1] You can subscribe to the (_very_ high volume)
inet-access mailing list by sending 'subscribe'
n the body of a message to
'list-request@inet-access.net'. Sorry, but this
list is (deliberately) not archived online.
ivan
> Actually, I can think of some instances in which sound card drivers could be vital for a
> web server. How about streaming audio over the 'net from a live sound source?
When you do live streaming audio, you use don't use your web server to encode the audio - you use a separate, dedicated machine for that. This is true for Real Audio as well as Shoutcast and the open-source Icecast.
(I'm not talking out my ass here - I geek for Technostate, an internet radio station that broadcasts live events.)