1 $Id: TODO,v 1.61 2001-04-15 12:56:30 ivan Exp $
3 If you are interested in helping with any of these, please join the
4 *development* mailing list (send a blank message to
5 ivan-freeside-devel-subscribe@sisd.com) to avoid duplication of effort.
13 finish transactions (svc_*.pm, fs_register/)
15 Pg-style or universal-style locking in fs_sessmon FS/FS/nas.pm, or rewrite it
16 to use a database expression that won't need it, or just dump the locking
17 entirely as nas_heartbeat stuff doesn't need to be accurate; it's just informational.
21 test with MySQL+Sleepycat?
24 unclassified, probably either done already or post-1.3.0
27 anything doing transactions in the web interface should likely move into *.pm.
28 (transactions are here woo!)
30 write some sample billing expressions with libcflow-perl :)
34 (at least) These questions need to be answered for Mason, Apache::ASP and
35 eperl. If eperl becomes too much of a pain, I'm okay with forgetting
36 about it - it's not well-maintained. The answers below are for Mason.
38 How do you interpolate a value? <% $value %>
40 How do you interpolate a value without escaping HTML? <% $value |n %>
42 How do you interpolate a (possibly non-stand-alone, non-interpolated)
43 control structure? With an inital % - for example:
45 % for each $value ( @values ) {
46 <OPTION><% $value %></OPTION>
49 This is one of the things I worry that the webmonkey HTML editors will not
50 like about Mason. That and the <%INIT> and <%PERL> tags.
53 in the context of a state machine (& MySQL and Pg locking) for LDAP export:
55 Also note that Pg locks are for the duration of the transaction, so
56 Freeside needs to start using transactions for this to happen.
57 FS::UID::adminsuidsetup should explicitly set AutoCommit false and export
58 some functions to begin and end transactions on $FS::UID::dbh. (Well,
59 eventually FS::UID should be an overloaded subclass of a DBI handle, but
60 we don't have to worry about that until perl threads + mod_perl + threaded
61 Apache 2.0 is stable, i.e. quite some time).
64 also supports virtual domains in a way that's somewhat similar (but not
65 compatible with) the way sendmail does. In the postfix world, all virtual
66 domain info is contained in one file (similar to the virtusertable), but
69 foo@bar.com some@other.net
70 quux@bar.com localuser1
72 and so on. After the file is generated, it gets compiled into a hash db
73 using, "postmap /etc/postfix/virtual".
76 steal all the play-nice-with-cache stuff back from RT
78 Use this for email checking:
79 libemail-valid-perl - Check validity of Internet email addresses
81 This module determines whether an email address is well-formed, and
82 optionally, whether a mail host exists for the domain.
85 wishlist from drenalin@ultimanet.com:
86 * delete button for customers
87 - 15th of the month billing
88 - field for customer referrals (naming who it is) and automatically crediting
90 - ability to edit referrals
91 - catch expired credit cards and notify via email when they are expiring
93 - set default shell to /bin/false when adding ppp account
94 - import list of POPs from Megapop (see www.ultimanet.com and click on locations
95 +from text in index page)
98 wishlist wrt projects/consulting from jivko@ijs.com:
99 >The other thing, which is the serious part, is the following: We do not
100 >offer dial-up services and that part of the system does not have to work,
101 >but we have many customer, for which we do both hosting and consulting work.
103 >The hosting can be handled by freeside fine, but in the little time I spent
104 >on it I could not see how exactly to solve the consulting problem. What I
105 >would love to see there is a way to create 'projects' for each customer and
106 >ability to follow up on those (I mean to be able to add new comments,
107 >descriptions, progress updates etc.). You already have the feature, which
108 >allows multiple people to access the system with different access rights so
109 >it should be possible to make it keep track of who and when updated given
110 >'project' so we could have the developers access the database and update
111 >the projects they are working on.
113 Hmm. Is this accurate: Each project is related to a single customer, and
114 zero or more packages (billing items). Each project has a name, due date,
115 and zero or more log entries consisting of date, user, and a text field
116 (for "new comments, descriptions, progress updates etc." - would you like
117 anything more specific?)
119 In conjunction with that it looks like you need the ability to create
120 "one-off" packages on the fly for arbitrary charges.
122 > Additionally it would be nice to have a page, where all open projects can
123 > be listed and not only that but be able list them by date too. (Say I want
124 > to find out which projects are due today or two days from today, or which
125 > projects are running late)
127 Browse/search project by date and customer.
129 > Finally it would be real nice if the billing script could add the cost for
130 > all completed projects (or work done by the hour) to the monthly bill along
131 > with the hosting information and using the description of the work from the
134 Can you be more specific about your needs here?
136 > This is a lot of work, unless you disagree :-), and I would not expect you
137 > to do all of it - we can work on it too - but I would hope for you to lead
140 I'm trying to get a handle on specifically what you need.
142 > Oh, and there is one more thing, but that should be simple to do. I would
143 > like to be able to give the customers access to selected information from
144 > their account. I want them to be able to monitor the progress of their
145 > projects and the status of their accounts.
149 > Does all this make sense? It must be close to what you need at your office
150 > though or at least I think so.
152 Yes, but we're small and have been tracking projects manually.
155 >You may have this already .. what I have in mind is the following. Say you
156 >have a customer for which you do hosting and some consulting (CGI, JAVA
157 >etc) At the end of the month you need to bill the customer for the hosting,
158 >35hours of Java programming and 10 hours of HTML authoring. The last two
159 >are not because the project is over but because the work was done during
162 >So the way I see it, and it could be wrong, is that during the month the
163 >people who work on particular project enter their comments and time spent
164 >on the project. At the end of the month the billing script generates
165 >invoices in which besides the hosting charges there are also charges for
166 >work done during the period.
168 >Currently we do this in a very stupid way by maintaining a customer file,
169 >in which a script saves things to be invoiced. At the end of the month a
170 >script goes through these files and generates invoices with all items from
171 >the files, which have not been flagged as 'paid'. The convenience of this
172 >is that no one needs to worry about the invoices containing the items they
177 first package select field in edit/cust_main.cgi isn't sticky on errors, yuck
178 (also referral isn't sticky either? yuck)
180 > 1. A Web Form to the user get his account added automatically . The
181 > /etc/raddb/users and /etc/passwd would be updated automatically (these
182 > file are on the same machine Freeside is). I guess the the Add
184 > page with some customization could be the work.
185 > 2. A Canceling Account Web Form available to user cancel his account
188 > 3. A Password Changing Web Form where the user could change your
189 > password by sending your username, old and new password.
190 > 4. Additional POP Accounts Creation where the user supply only his
192 > username/password (probably provided from a PPP Account already
194 > and his POP username/password for this specific account.
195 (actually need something more general i guess - probably need some way to say
196 which accounts (svc_acct) can log in and make changes per customer (cust_main) )
198 this is awfully vauge, perhaps email for more info? don't want to alientate
199 someone with accounting experience, but i just don't have time right now.
203 Thanks for the information. It took me a little while to figure it out, but I
205 able to create an invoice. As a lamer and an accountant, may I make a few
208 On the Customer view page:
209 1) Layout the information in the manner the invoicing process is conducted.
210 a) Customer information
212 c) Add a "Create & Edit Invoice" section - this allows auditing of the
213 invoice before it is processed.
214 d) then put the billing section to actually process the invoice
215 e) then put payment history information
218 Mark Roberts <mroberts@iopenenterprises.com>
221 new overdue code might be overzealous. test carefully.
223 Port Freeside to use the modules that were abstracted from it:
224 Net::SSH, Net::SCP, DBIx::DataSource and DBIx::DBSchema, at least.
226 "first package" and email invoice (?) not sticky on errors in new/edit customer
229 http://www.ipmeter.com/ integration would be useful
231 http://tangram.sourceforge.net/
234 mmm, http://pootpoot.com/~dlowe/DBIx-Table/
236 The cybercash links in htdocs/docs/config.html are b0rken.
238 Yes. Which is what I've been trying to tell you. (destination user,
239 destination domainname) would be represented by the svcnum of a record in
240 svc_acct. (In retrospect, using the uid instead of the svcnum was a bad
241 choice). (domuser, domain name) would be part of the svc_acct_sm record,
242 as domuser and domsvc.
244 Upon further consideration, I'll probably eliminate the svc_acct_sm table
245 completely, and just add a field for the svcnum of a domain and the svcnum
246 of a destination mailbox to svc_acct (or perhaps a one-to-many
247 relationship - multiple svcnum(s) for multiple destination mailboxes.
250 > > > > Longer-term, I need to do something about the length of the
251 > > > > column names -
252 > > > > The SQL1992 standard defines 18 character column names,
253 > > > > which would be a
254 > > > > reasonable goal.
256 > > > Maybe the thing to do would be to separate these out to separate
258 > > > then we could simply use something like id, attrib_name,
261 > > > store all of the radius values.
263 > > Hmm, no, that's not quite right. You don't want to store the actual
264 > > strings in the records for each account. Probably need a table that
265 > > corresponds to the RADIUS dictionary file, with a list of
267 > > attribute id's, then reference the attribute by id and not name.
269 > > The more difficult bit is handling the service definitions
271 > > part_svc and it's effects.
273 > Yes that could be a bit tricky. Perhaps just one "radius" field in
274 > part_svc that held a list of id's from the radius table that applied
275 > that particular service?
277 No, that wouldn't let you set defaults or fixed values for each attribute,
278 like part_svc currently does.
282 hmm - if you delete an account in svc_acct somehow that a mail alias points to,
283 svc_acct_sm.export will fail. make sure this can't be done using
286 Bug: during the linking process apparantly you can link too many services to
289 zip code i18n is not very good :( but at least US, CA, HU, ?
291 ut_phonen doesn't check data length. several
292 orthogonal cleanup projects here. *sigh*
294 update the cybercash links in config.html and in the homepage. add more explicit support for other payment types. etc.
296 From "Tim Jung" <tjung@igateway.net>
298 Automatic CC Decline Notices via email
299 Block Time billing for prepaid internet cards (400 hours or whatever block
301 Trouble Ticket System with simple search function for Knowledge Base feature
303 Credit Card System support for Red Hat's CCVS, and other Linux credit card
305 Contact Manager/Lead Tracking
307 Cisco NetFlow Account for IP traffic billing
308 VoIP and FoIP billing
309 Roaming per minute billing based on Radius Proxy support or number they
310 dialed into from Radius logs (800# etc)
311 Support for OpenSRS Domain Registration
312 Support for TUCOWS signup CDs
315 dbdef-create for postgres
317 pro-rating, fiddling dates
319 It looks like svc_acct.import doesn't deal well with comments and
320 multi-attribute lines.
322 ivan@rootwood:~/freeside_current$ rgrep -r domuid * | cut -d: -f1 | sort |
327 bin/svc_acct_sm.export
328 bin/svc_acct_sm.import
329 htdocs/docs/man/svc_acct_sm.txt
330 htdocs/docs/schema.html
331 htdocs/edit/CVS/Base/part_svc.cgi
332 htdocs/edit/part_svc.cgi
333 htdocs/edit/process/svc_acct_sm.cgi
334 htdocs/edit/svc_acct_sm.cgi
335 htdocs/search/svc_acct_sm.cgi
336 htdocs/view/svc_acct_sm.cgi
337 site_perl/svc_acct_sm.pm
339 rootwood:COMPLETEHOST/TODO
341 Currently, you set a value in the %FS::UID::callback hash with a coderef
342 of the code you want to execute, but this was bad design and will shortly
343 be changed to a subroutine to which you pass your coderef to register it.
345 This is not a bug, it is how the system is currently designed. After
346 defining a new package, you need to specifically allow agent types to
347 purchase packages. You can do this from the edit screen of the new agent
350 It wouldn't be a bad idea to add a configuration value that makes new
351 packages available for all currently existing agent types automatically.
353 On Fri, Apr 07, 2000 at 10:50:35AM -0500, David Morton wrote:
354 > For some reason, the type_pkgs table didn't get updated when I tried to
355 > create a domain service and package... insert into type_pkgs values
356 > (4,1); fixed it up so that I could actually order the package.
359 From: Chuck Cochems <zaphod@tdl.com>
361 1) automated generating of late notices. So far the only way I know to
362 generate one is to re-invoice manually.
364 2) smart credit card rejection handling. It should e-mail a note at
365 least, explainig that it did't go through, and why.
367 3)coment field in the main customer record.
369 4) streamlined payment entry feature. the current scheme has it fairly
372 5) queries to show al customers who owe money,and such stuff as that.
375 credits aren't counted against past invoices? hmm. something needs to be
376 done to "apply payment" genericly. and zero out invoices etc.
378 more email which should make it into a more organized TODO list:
380 I would also love to see Freeside support bandwidth billing by reading the
381 Cisco NetFlow Accounting data so we and other ISP's could automatically bill
382 co-located servers and even potentially other virtually hosted sites like
383 MUD, Palace Chat, IRC Chat, etc based on the bandwidth they use or average
384 sustained rates or whatever. I'm not much of a programmer so I don't know
385 what all this entails but I did download a NetFlow client agent/whatever for
388 It would also be nice to see Freeside be able to read Apache log files and
389 bill customers for web traffic that way as an option also. Plus an option to
390 bill for excessive disk usage without having to use quotas if you didn't
391 want to, would be a nice feature as well. So you could monitor with a script
392 or something to see how much disk space a user was using then get some
393 average and charge a certain amount for anything above some preset limit for
394 that account type. I might be able to hack something like this up, but I'm
395 not 100% sure where to start or if there is something out there that could
398 Do you think that you will ever support the HKS CCVS (Hell's Kitchen
399 Software Credit Card Verification Software) since Red Hat bought them out
400 and is going to be including that for credit card processing when you buy
401 the professional version? What about possibly supporting the OpenCCVS which
402 is a GNU/GPL version of a credit card program? I haven't had time to comb
403 through the Freeside code to see how hard it would be to add support for
404 these as externally called programs.
406 Also any thoughts on help desk, and knowledge base stuff? Any thoughts on
407 this stuff, and how possible and what kinds of work or time frame would be
412 Internet Gateway Inc.
417 CVS via SSH (Score:1)
418 by platinum (jedgar at fxp dot org) on Thursday September 30, @07:13PM EDT (#4)
419 (User Info) http://www.fxp.org/~jedgar
420 The links above are your best bet for basic cvs server configuration. Once you have a pserver set up, you
421 may consider using cvs via ssh. All you need to do is the following:
423 1) Have ssh and sshd set up on the client and server machines
424 2) Set CVSROOT="joe@example.com:/home/ncvs"
425 3) Set CVS_RSH="/usr/local/bin/ssh"
427 (Obviously, insert the proper host/paths above)
429 You can also set up cvs/ssh to not need a password every time (similiar to an initial 'cvs login'):
431 1) run ssh-keygen on client machine using no passphrase.
432 2) copy/add ~/.ssh/identity.pub on the client to ~/.ssh/authorized_keys on the server
433 (man ssh for more details)
435 The main reason I mentio
436 CVS via SSH (Score:1)
437 by platinum (jedgar at fxp dot org) on Thursday September 30, @07:13PM EDT (#4)
438 (User Info) http://www.fxp.org/~jedgar
441 There's no way to do this currently, though it would be pretty
442 straightforward to modify the source - specifically, the _collect_
443 subroutine in FS::cust_main.
445 On Mon, Dec 13, 1999 at 04:05:32PM -0700, Jeff Garner wrote:
446 > Freeside will e-mail my users when they are billed if they are setup as
449 > When setup by credit card it does not e-mail them. Is there a way to
450 > turn on e-mail invoices for those who are billed via credit card? Kind
451 > of like a recipt of billing....
454 doc: http://www.softagency.co.jp/mysql/qmail.en.html
456 sql1992.txt standard is 18 character column names. shoot for that, not just
457 32 (postgresql default)
459 Also note that (AFAIK) Freeside won't display any package that has more
460 than one service on the "Add Customer" page. The reason for this is
461 because there's no way to dynamically alter the displayed html form
462 based on which package is selected. One possible solution would be to
463 make an additional page that's used in the signup process that would
464 display the form for each package, like a MS-style "Wizard". The first
465 page lets you select the package, then the second page has the custom
466 form with fields for each service in that package and a save button. Of
467 course, that would require a little perl work.
470 Scott Cruzen <sic@boernenet.com>
473 Your suggested script with back up /usr/local/etc/freeside, but will miss
474 any database not named `freeside'. Both of our scripts are specific to
475 MySQL. If you're interested in contributing to Freeside, maybe you could
476 work on a script which: reads the mapsecrets configuration file and then
477 each secrets file to find out what specific database engine(s) (MySQL,
478 PostgreSQL, etc.) and database(s) need to be backed up, then does so,
479 serializing backups of the same engine, i.e. stop mysql, do all the mysql
480 backups, start mysql, stop postgresql, do all the postgresql backups,
481 start postgresql, etc.
484 > mysqldump -t freeside > fs-backup.sql
486 > tar -Pzcvf fs-backup-`date +%y%m%d%H%M%S`.tgz fs-backup.sql /usr/local/etc/freeside/
489 I chose to use counters in the filesystem because there is no standard way
490 to get the value of an auto-incrementing keyfield which is common across
491 all databases (as seen through DBI/DBD).
493 It certainly wouldn't be a bad idea to use the database-specific methods,
496 htdocs/edit/svc_acct.cgi:
497 (Does the `*HIDDEN*' show up when you are adding a new account, and
498 specify the password, then receive an error and are returned to the form?)
501 Thought some of you might be interested in this:
503 <ftp://ftp.minivend.com/pub> has CyberCash compatibility modules for
504 Paymentnet <http://www.paymentnet.com> and Authorizenet
505 <http://www.authorizenet.com> which should allow you process transactions
506 using those services as well as CyberCash.
508 The files are named CCLib.pm.paymentnet and CCLib.pm_authorizenet,
509 respectively, and are installed by renaming to CCLib.pm and moving to your
510 site_perl directory. Otherwise, follow the directions for Cybercash v2 in
511 htdocs/docs/config.html
514 fs_passwd/ is a client-server replacement for the `passwd', `chfn' and
515 `chsh' commands that updates the Freeside database. (so for that to be
516 useful, you'd have to be exporting that data periodically)
518 fs_radlog/ is a client-server RADIUS log parser that stuffs the data into
519 SQL. It isn't finished, and probably won't be unless someone who I can't
520 convince to use one of the RADIUS daemons that logs to SQL directly pays
521 me money or something.
523 fs_signup/ is a client-server signup server. i'm just finishing it up
524 now; probably isn't on your machine yet.
527 http://www.sisd.com/freeside/list-archive/msg00812.html
529 package definitions should be implicit allow wrt agent types, not implicit deny
530 (with the old behavior possible via a config file)
532 > So is there anyway it could be setup to allow you to select a "primary
533 > service" from each package? This service would be the one you were prompted
534 > for. Could the signup server then be expanded to allow users to go into
535 > their package and "turn-on" the remaining non-primary services(using the
538 take the GPL'ed whois proxy stuff at www.geektools.com and turn it into
539 intelligence for Net::Whois.
541 A web version of the fs_passwd stuff would be nifty.
543 If you have Cistron authenticating directly from MySQL, you can replicate
544 in real-time instead of exporting periodically. See
545 <http://www.mysql.com/Manual_chapter/manual_Common_problems.html#Replication>.
548 <http://www.sisd.com/freeside/list-archive/msg00541.html> (was 546), and
550 and http://www.sisd.com/freeside/list-archive/msg00421.html (was 423)
552 > > 5: Is there anyway to get freeside to send a sysadmin a warning when a
553 > > credit card has expired?
554 No, but there should be.
556 Put this in the doc (quoting Mark Wells <mark@pc-intouch.com>):
557 >Of course, thanks to the sheer coolness of SQL and MyODBC, you can do
558 >whatever reports you want in basically whatever application you want.
559 >There's no need for Freeside itself to do any reports at all.
561 middle names and titles
563 On Wed, Jul 07, 1999 at 01:11:40PM -0400, Frank Nazario wrote:
564 > Playing and entering information to Freeside i encountered the following
567 > View Customers by Agent
569 > View Pending Invoices
572 grep 'uncomment this to encrypt password immediately' site_perl/svc_acct.pm
573 Not to say that it shouldn't be a configurable option.
575 in site_perl/cust_main_invoice.pm (elsewhere?), error out if mydomain config file is gone
576 (at least until the idea of a default domain goes away)
578 FS::Record::qsearch does an eval every loop iteration (which is itself not
579 guaranteed to work across all DBD's and should be fixed). This has got to be
580 slow. Fix it. (I think recent Perls might have a way to accept a variable
581 there, no eval needed?)
583 Could you have added /bin/sync, /sbin/shutdown, and /bin/halt to the
584 `shells' configuration file before importing, and removed them afterwords?
585 (even better if svc_acct.import did that automatically - it could just
586 munge and restore @FS::svc_acct::shells... hmm.)
588 > BTW, Ivan, I am trying to verify in an additional database table that a
589 > particular user doesn't exist. This database is used to store email aliases a$
590 > additional POP boxes for our customers (kinda like AOL allows). I have toyed
591 > with the idea of just writing the aliases to an email only svc_acct that
592 > doesn't write to the password file, but that isn't really how I want to do it.
594 Actually, I think that's a pretty good way to do it. Cerkit contributed
595 support a little while back for svc_acct.pm and svc_acct.export for
596 multiple export targets. It needs to be cleaned up and documented, which
597 I'll try to get to soon. For this to work correctly, the svc_acct_sm
598 table should go away, along with the concept of a "default" domain.
600 default setting for new packages should allow all agents to purchase them...
601 with a config file for the old behaviour
603 fix or replace Term::Query (Quiz::Question doesn't do what i need)
605 Check config file reading stuff from CPAN
607 Authorizenet module from CPAN!
609 <http://www.math.fu-berlin.de/~leitner/mutt/faq.html> has a good y2k complience
612 I'm hoping Freeside can support arbitrailly complex pricing plans
613 because of a simple concept: all prices are perl expressions. So if
614 you use `19.95' for example, perl evalates that to be `19.95'. But if
615 you need to do a complex pricing scheme, you just need to write an
616 appropriate perl expression, which will most likely pull data from the
617 database to return pricing. Some things will already log to SQL; for
618 example most RADIUS servers can or have a patch available. Getting
619 Freeside to bill based on any sort of data then becomes a matter of
620 importing the data into the database.
622 There are some issues involved with pro-rating, partial month charges,
623 that sort of thing. Expressions will need a standard way to have the
624 applicable time/data ranges passed to them. Also the expressions are
625 currently running under the Safe perl module, and the opmask might not
626 be right in all situations. I'll try to spend some time working on
627 this if you are using it.
629 > 2. can customers view their bills on-line.
631 Not yet; it needs to be proxied from Freeside to a customer web server in
632 a secure way using something not completely unlike the fs_passwd,
633 fs_passwdd, fs_passwd_server trio.
636 > Lastly, if someone over pays on an invoice, the credit part does not flow
637 > over to other invoices..
639 The total balance flows over correctly, but individual payments don't.
640 The code you're looking for is in FS::cust_pay::insert
642 The question of what to do with overpayments that don't have another
643 invoice to flow into (yet.. or possibly not) is still an open one. The
644 legacy system Freeside replaced long ago had a separate place for this
645 (payments waiting for an invoice) for each customer, and it gave our
649 option to relax username uniqueness in favor of username+domain or mail/shell
650 vs. radius to ease import for isp's with namespace problems or who buy others.
652 do i have to store anything for radius realms besides regular radius attributes
653 (which are handled fine now)?
655 warn or complain or something when invoice_from is empty (and we use it)
657 Right now Freeside uses the `freq' field of a package definition as a
658 number of months. The specific section of code you're looking for is in
661 #change this bit to use Date::Manip?
662 #$sdate=$cust_pkg->bill || time;
663 #$sdate=$cust_pkg->bill || $time;
664 $sdate = $cust_pkg->bill || $cust_pkg->setup || $time;
665 my ($sec,$min,$hour,$mday,$mon,$year) =
666 (localtime($sdate) )[0,1,2,3,4,5];
667 $mon += $part_pkg->getfield('freq');
668 until ( $mon < 12 ) { $mon -= 12; $year++; }
669 $cust_pkg->setfield('bill',
670 timelocal($sec,$min,$hour,$mday,$mon,$year));
671 $cust_pkg_mod_flag = 1;
673 ..and when I went poking for this, looks like it tells us just what needs
674 to be done! Hehehe...
676 Date::Manip can handle cool things like "+ 1 month" (actually the current
677 case of /^(\d+)$/ would have to be added as a special case of "+ $1
678 month") and "+ 30 days" (what you need) and even "+ 5 business days" !
681 On Wed, Apr 28, 1999 at 08:38:16PM +0000, Kristian Hoffmann wrote:
682 > I can't quite seem to figure out how this exporting works. From what I
683 > understand, when you run svc_acct.export, it rewrites the /etc/passwd,
684 > /etc/shadow, etc. files. Is this only for initial setups with the
685 > export hooks being in the pm's?
687 You can use both, or just one method. The configuration files control
688 this. One of the things in the TODO is to take out the last few things
689 that aren't customizable wrt this and put them in config files.
691 http://www.daemonnews.org/199905/user-mgmt.html
693 Term::Query doesn't install out of the box from CPAN. Fix it (and get it
694 submitted upstream!), or remove requirement from bin/svc_acct.import and
695 bin/svc_acct_sm.import and take it out of the install instructions.
697 use this cool link to explain the Freeside API
698 ftp://cpan.nas.nasa.gov/pub/perl/CPAN/doc/FMTEYEWTK/easy_objects.html
700 Multiple tax rates by geographic region (county, state, and county) are
701 supported; just choose View/Edit tax rates from the main menu.
703 Multiple tax rates by package are not (yet) supported.
705 On Wed, Jul 07, 1999 at 12:13:36PM -0400, Shaun Batterton wrote:
706 > How would you handle something like multiple tax rates and multiple
707 > states? For example in Connecticut, they just changed computer and/or
708 > data processing services to 3% (whatever that is), and everything else
712 > Second, when trying to add a new user I get two types of errors; first one
713 > is when I place an e-mail address and select the "submit," Freeside
714 > complains with "Error: Unknown local account (specified literally)"
716 You probably put a (local) email address in for email invoices. Freeside
717 stores these as references to the database records, so (for example) they
718 follow username changes.
720 I'm guessing you put in the email address that you were creating, and got
721 that error because it didn't exist yet. Sounds like a buglet to me. I'll
722 try to fix that soon; in the meantime you can add the invoicing email
725 (workaround for postgres before 6.5) (unlikely to ever be implemented)
726 In the mean-time, this could probably be fixed with the reverse of
727 the kludge in FS::Record::new. This removes `$' and `,' from money fields
728 coming out of the database. Something which fixed up the data so Postgres
729 was happy with it could go in FS::Record::_quote, for data going into the
732 our data display problem might be a Freeside problem wrt not using
733 Oracle-compatible DBI syntax (fixed using the return value from $sth->execute
734 as a number of rows - something else?).
736 hooks for arbitrary commands out of configuration files
737 svc_acct.pm svc_acct_sm.pm etc.
739 Add this to a FAQ, along with doing it for middle names:
742 > What I'm finding difficult is how to easily
743 > customize fields. For example, I am trying to add a "middle name" field
744 > to the Customer Edit, view, etc. If I'm going about it right, it appears
745 > I have to edit the cust_main.cgi under edit and edit/process and the
746 > site_perl/cust_main.pm, as well as other things. Perhaps you could shed
747 > some light on the best way of doing this.
749 You have the basic idea. To implement that completely, I would:
750 - Add the new field to bin/fs-setup for new users
751 - Document the field in htdocs/docs/schema.html
752 - Document the change in a new file, htdocs/docs/upgrade4.html
753 * Run bin/dbdef-create
754 * Add the new field to edit/cust_main.cgi and edit/process/cust_main.cgi
756 For bonus points, I'd grep around for the various bits which use "$first
757 $last" or "$last, $first" and replace them with a method call in cust_main.pm,
758 , like search/cust_main.cgi
760 document security model:
761 Don't forget about Apache usernames - since, via the mapsecrets file, each
762 user can login to the SQL database with a different username and
763 password, you can utitilize the security model of the SQL database as
764 well. Also, each username here can point to a different configuration
765 directory where you could store user-specific configuration info. Then
766 you could link each username to one-to-many agents.
767 (The web demo works using a trivial version of this.)
769 Yes, queue processing or the equivalent via checkpoint fields on various
770 talbes (which you pick up via a pretty simple SELECT) would be really
773 default (and ordering) state/county/country config file
775 cust_main_county table to provide a preferred ordering, so the most common
776 entries would be at the top of the selection box. automatically, based on
779 hmm... maybe svc_acct__shell should check off the legal shells list if
780 applicable? yeah... cool.
782 payinfo field should me much larger than 16
785 [Mon Apr 12 20:31:21 1999] [error] [Mon Apr 12 20:31:21 1999] null: Error closing true: Broken pipe at /usr/local/lib/site_perl/FS/cust_main.pm line 615.
787 javascript (yuck!) "are you sure?" confirmation on cancelations, etc.
788 (view/cust_pkg and view/svc_*)
790 get rid of time2str("%D") which formats dates in a non-y2k-safe looking fashion
791 (all the actual date handling uses UNIX timestamps and is fine)
793 uncomment expire in view/cust_pkg.cgi and find the expire cron from fsold
796 one-time/per-customer/? changes in rates and descriptions ('remembered
797 invoices'): implement by creating a new package on the fly... but it isn't
798 associated with any agent types so it won't show up for other customers to buy.
799 (but also... make sure they go away when the customer does! - need this? :
800 one-off package edits! : need a cust_pkgs or cust_part_pkgs or something table,
801 with custnum and partpkg (like type_pkgs)
802 (what happens if you hit "custom pricing" but the pricing is already custom?)
804 Lay out any remaining ugly forms better.
806 remove "records identical" warning? gets in the way of more important stuff.
807 or fix logic which tries to update identical records??
808 1.2 should be quiet enough that the error log is useful, hopefully.
810 Postgres has a maximum column length of 31 characters (but see NAMEDATALEN in
811 postgres_ext.h). part_svc has columns like: svc_acct__radius_Attribute_flag
812 (22 characters!) It seems that stuff over the limit is silently ignored,
813 so we get 4 characters back. So, Radius_Attributes are max 13 characters with
814 stock Postgres. see rfc2138 for what's affected
815 What's a good fix? (besides recompiling postgres with NAMEDATALEN 64)
816 (mysql has a 64 character max column length. others?)
818 [Mon Mar 29 06:57:56 1999] -e: Use of uninitialized value at /usr/lib/perl5/Date/Format.pm line 333.
819 (when sending mail in cust_main.pm::bill or svc_domain.pm)
821 look at DBIx::Recordset! (and Tie::DBI, and...)
823 undefined conf/lpr gives this uninfomative error:
824 [Fri Feb 26 16:42:36 1999] bill.cgi: Can't do bidirectional pipe at
826 l5/site_perl/FS/cust_main.pm line 629.
827 [Fri Feb 26 16:42:38 1999] bill.cgi: Error closing : Broken pipe at
829 l5/site_perl/FS/cust_main.pm line 631.
830 So give a meaningful error!
832 password and slipip stuff in svc_acct.pm store need to be split into two fields or something, so the silliness in svc_acct.pm and svc_acct.export with looking at the data to decide what to do with it can be fixed
834 i10n: Apache::Language
836 Apache::Session? Other useful Apache::* ?
838 email invoices are only sent for the BILL payby. If setup, should statements
839 (since they're not invoices) be sent for COMP and CARD as well?
841 $cgi->keywords is causing the (hard to trace) error:
842 Use of uninitialized value at (eval 5) line 5
844 edit/cust_main.cgi gives an uninformative error message:
845 > Can't call method "agentnum" without a package or object reference at
846 > /usr/local/apache-ssl/htdocs/freeside/edit/cust_main.cgi line 116.
847 if there are no agents.
849 (is this missing on any web screens? (easy with $cust_svc->label)
850 Add the ability for services to filter information up to the package level
851 for web screens, so you can select a particlar package based
852 on username or domain name, etc.
854 Allow a cancelled/suspended/active status from packages to bubble up to
855 the customer lists. Put active, then suspended, then cancelled accounts.
856 Similar ordering on the package listing inside a single customer.
858 false laziness: edit/cust_main.cgi got some parts copied from edit/svc_acct.cgi
859 the web interface in general needs to be redone in a more abstract way.
861 false laziness: some of search/svc_acct_sm.cgi was copied to search/svc_domain.cgi. but web interface in general needs to be rewritten in a mucho cleaner way.
863 subroutine the where clause (eventually all SQL) as OO perhaps (has anyone done this?)
865 add a select method to FS::Record?
867 one-time/per-customer/? changes in rates and descriptions ('remembered
868 invoices'): implement by creating a new package on the fly... but it isn't
869 associated with any agent types so it won't show up for other customers to buy.
870 (but also... make sure they go away when the customer does! - need this? :
871 one-off package edits! : need a cust_pkgs or cust_part_pkgs or something table,
872 with custnum and partpkg (like type_pkgs)
873 (what happens if you hit "custom pricing" but the pricing is already custom?)
875 You can't delete the stuff under administration yet. Add this,
876 _including_ making sure the thing you are deleting is not in use!
878 add links on view/cust_main.cgi to setup services, like view/cust_pkg.cgi
880 FS::cust_pkg _require_'s FS::$svc, but this won't work with %FS::UID::callback
881 loading of configuration. (pry need same idea, but will run immediately if
882 context allows). Looks like error is masked by 'use FS::cust_svc' which in
883 turn 'use's FS::{svc_acct, svc_acct_sm, svc_domain}' which is now explicit
886 Allow a cancelled/suspended/active status from packages to bubble up to
887 the customer lists. Put active, then suspended, then cancelled accounts.
888 Similar ordering on the package listing inside a single customer.
890 svc_domain.pm mail sending uses Date::Format which doesn't seem to pick up
893 view/svc_domain.cgi needs to know the domain might be unaudited (cosmetic)
895 remove whois_hack set to 1 for svc_domain.pm? add all known registries and
897 .us domains and others!
898 site_perl/svc_domain.cgi (hmm... or maybe should have a button? or maybe svc_domain.pm should handle this) should set $whois_hack for non-internic domains, so you can add them...
900 turn on the depriciation warnings for [e]idiot in FS::CGI. Stop using [e]idiot
901 the last places it is (htdocs/search/ htdocs/misc/ htdocs/misc/process)
903 (test cust_main.pm with cybercash v2 and v3, especially with the callback
904 stuff AND with mod_perl w/cybercash v2 kludge in package main)
905 (callback stuff should be eliminated by now)
907 bah, table/itable/*table in FS::CGI is silly.
909 doc Apache::AuthDBI as well
911 Provide sample httpd.conf files.
913 hey look: Tie::DBI! Check that out. Override its commit with something that
914 does perl-side caching for ? a performance improvement and as an emulation
915 layer to plug in f.ex mysql's atomic transactions
917 Record.pm uses does some non-portable DBI things. MySQL and Pg seem fine.
918 Fix it anyway unless we migrate to Tie::DBI.
922 cust_bill.pm uses '==' comparison on dates because they're currently ints
924 config file for allowed card types
926 write instructions for adding new services w/svc_Common.pm. Get rid of all
927 places where svc_* tables are hardcoded (rename svc_acct_pop to part_pop so
930 test and document libapache-dbi-logger (woo!)
932 radius logfile parsing and perl expression check.
934 Fix in cust_bill BUGS:
935 There is an off-by-one error in print_text which causes a visual error (Page 1
936 of 2 printed on some single-page invoices).
938 fields should be a method against a FS::Record or derived object, as well as
939 being something you can call as FS::Record::fields('tablename'). Might
940 even be able to handle both in the same routine (that would be neato).
942 Immediate removal of incorrectly entered check payments (can't take too
943 long to do this, or accounting is fubared).
945 Add code to move from one service to another (POP to SLIP/PPP, etc.).
946 This _should_ be possible by working off the rules in part_svc rather than
947 hardcoding anything in. The rules in part_svc may need some elaboration,
950 Use ut_ FS::Record methods in all derived classes (possibly some from dbdef?... eventually all from dbdef??? - but then `dbdef-create' would be impossible as there would be metadata we couldn't ask the backend for. hmm.)
952 (bring back from fsold, ) Generalize config-sending stuff and make more configurable.
953 Expand the HylaFAX interface (also possibly generalize for other fax
954 softwar ie .comfaxe); allow things like arbitrary faxes of sales
955 literature, specific troubleshooting documents and so on. Maybe even
956 allow users to do this (though that might not belong in Freeside).
958 misc/process/sendconfig.cgi
959 Configure fax recipients via a separate box rather than using the finger
960 name or first+last from cust_main.
962 move all phone number logic out of Freeside - let HylaFAX or whatever
965 soundex searches for customer name and company? where are free soundex tools? (standard Text::Soundex duh) - I could have sworn I saw Text::Soundex on CPAN?!
967 should be able to link on some field in email alias (right now you can link
968 on username or domain with a fallback to svcnum)
970 generalize and make configurable new invoice printing scheme in FS::cust_main::collect (past due)
972 deleting an svc_domain should delete all associated svc_acct_sm records.
973 same with a svc_acct.
975 periodic password encrypter
977 Automated, configurable notification, suspension and cancellation of
982 Allow for a future setup date on accounts.
984 sub AUTOLOAD in FS::Record should warn? die? if used with a non-existant column
987 edit (not just import, export and allow default/fixed) arbitrary radius stuff
989 edit/svc_acct.cgi and edit/process/svc_acct.cgi should deal with arbitrary radius stuff
991 radius import should take DEFAULT entry and put it in /var/spool/freeside/conf/radius-default ; svc_acct.export should use it (and doc)
993 in UI, s/State/State\/Provence/go and s/County/County\/Locality/go
995 what else (besides l10n) for i18n? (money!)
997 audit htdocs/* for things that should be libraried and things that should be
998 new methods on the objects (need to do this before implementing a new UI)
999 all the big things are done
1001 some places we die() where we should &FS::CGI::idiot (and perhaps vice-versa).
1002 Decide based on whether or not the "error" should show up in logs.
1004 all .cgi's should use standard header/footer and idiot() subroutines. maybe HTML:: perl modules
1005 for HTML creation. Maybe Embperl or something along those lines. ?
1007 When running bin/bill, Fix this (Annoying but harmless):
1008 Use of uninitialized value at /usr/local/lib/site_perl/FS/cust_pkg.pm line 99, <ADDRESS> chunk 4.
1009 Use of uninitialized value at /usr/local/lib/site_perl/FS/cust_pkg.pm line 102, <ADDRESS> chunk 4.
1010 Use of uninitialized value at /usr/local/lib/site_perl/FS/cust_pkg.pm line 105, <ADDRESS> chunk 4.
1012 all cgi (but internal to the isp) places where package names are listed should also have
1013 comment (like agent_type)
1015 clean up $recref and other silliness and use -> calls where possible, or
1016 one other alternative. clean up everything else.
1017 should FS::Record use Tie::Hash? That would be very clean, but where do we
1018 store the other information? Maybe you could ask any FS::Record object for a
1021 change all file access from regular open(FILE,) stuff to OO, because of
1022 problems scoping and passing filehandles like that.
1024 the web interface should create a new object and use it instead of a blank
1025 form for new records. the create method of svc_ objects should set defaults
1028 sub check in man FS::table_name should be rewriteen. Get rid of $recref
1029 stuff. Make sure all fields that refer to other database are checked.
1031 Integration with signup disks (are there any free ones? Netscape?).
1033 One-button cancel (+refund) for lusers who can't get online.
1035 Keep information on virtual web servers (hostname, IP, host machine,
1036 directory, etc.) and export this information for importation into the ISPs
1039 Remove requirement that the first mail alias be the catchall? Still make
1040 sure only one catchall per domain is defined in any case, of course.
1042 Ability to move cust_pkg records from one customer to another? (proably
1043 will need to cancel the old and create a new like when we move services
1046 Auto-increment expired cards one year, and try again?
1048 More non-US stuff - zip codes, country codes, foreign currencies, etc.
1050 cust_refund.{cgi.pm} need to do cards xaxtions. (now we only have cust_credit)
1052 Nicer set of integrated reporting possibilities, like weekly sales totals
1053 by customer, package, agent, referral, etc., aging reports sorted by lots
1054 of different things, and so on.
1056 Client/server setup for users to modify their own passwords, shells, etc,
1057 via passwd or secure web interface (prelminary passwd/chfn/chsh
1058 replacement done). Complicated by the fact that we don't want to allow
1059 incoming connections to the machine running Freeside, so we probably need
1060 to have a daemon on each external shell or web machine that is contacted
1061 by the Freeside machine. Be very very careful for both traditional
1062 security issues and DoS problems.
1064 An extension of the above to allow users to modify selected parts of their
1065 own information, order and cancel services. A web interface for new
1068 Expand domain name stuff to house all domain information. Export
1069 named.boot/named.conf (primary and secondary) and named.{domain} files.
1070 Add more registries (not just InterNIC's com org net edu)
1072 Nice postscript paper invoices, rather than current ASCII invoices.
1074 think about race-condititions in FS::Record and derived ->check ->insert
1075 and so on, uid and username checks in svc_acct, etc.
1077 Move to rsync over ssh file exportation rather than scp.
1079 check 'n fix the proactive password checker. (cracklib?)
1081 refunds of "BILL" payments: generate pseudo-check.
1083 write batch senders and batch parsers for the different credit card processors
1085 More CC processors/methods.
1087 you should be able to fiddle the setup date in cust_pkg. (at least initially)
1089 delete options in administration section
1091 write a generic batch senders and batch parsers.
1093 need a way to override svc_acct export on a per-machine basis; just use config files based on machine name i suppose; document that. (no, import desync_hosts
1094 type stuff from cerkit)
1096 add a table with column of export services (passwd, shadow, master.passwd, .qmail file update, dns update, etc.) and rows machine groups and whether or not to export that (and any necessary parameters). wasn't matt (vunderkid, not matt@michweb) working on this? find him? each machine goes in a group of its own as well as a group based on function. add a table with only svcpart and machine group. now, when you import from each machine, it can get its own accounts with one svcpart and universal accounts with another svcpart. (though that does make the username duplicate checking more interesting)
1098 you should be able to get column types as a method against an FS::Record object
1099 as well as dbdef->table($table)->column($column)->type
1101 move to perl module for fuzzy and soundex searching.
1103 package view needs to list extraneous services; we need to prevent the
1104 creation of them so this never happens (and mark it as such in the source)
1105 (the creation problem should be fixed - though they will still happen if people
1106 fsck around in the data manually, so list them anyway)
1108 add attribute dictionary to fs-setup as a menu, plus analyze users file to
1109 decide automatically
1111 Check for and report on duplicate billing accounts (cust_main, though many
1112 will have a need for these so probably don't disable them outright.)
1114 create a ->warn as well as a ->check method for all FS::table classes?
1117 something to automate making a release and updating the web demo
1119 export a debian-style (also redhat and?) /etc/group file aswell!
1121 svc_acct_sm.import qmail import should pull in recipientmap people too.
1123 .pm's like svc_acct.pm which need to do time-consuming things like ssh remotely
1124 should fork and do them in a child.
1126 i18n/l10n: take ALL messages and catalog them in english.txt or in database or something, so we can eventually go int'l. int'l currency support would be a help aswell.
1128 get some of { city, county, state, zip } from the missing bits if
1129 possible (where can i get the data to do this? usps.gov?)
1131 additional interfaces (perltk? java?)
1133 Put the GPL notice in all files.
1135 integrate w/IDEA's signup server
1137 $cust_bill->owed database field to be eliminated, replaced by a method call
1138 that calculates on the fly. make sure to grep for ->(get|set)field('owed')
1139 same for cust_credit->credited
1141 Export quota information.
1143 move all configuration to a central place. maybe in blob's in the
1144 database. maybe even things like the code to execute when a username is
1145 changed can be in there, so less of the distributed scripts change between
1148 Implement setup and recurring fees as Safe perl expressions rather than
1149 numbers, to allow for variable-rate services. Backwards compatibility is
1150 obtained because { 43 } in perl is still 43. :) Define API to pass
1151 starting and ending dates and any other necessary data to expression
1152 (fees are currently evaluated as Safe expressions but more work needs to
1153 be done to define an opmask for various needs, write examples
1154 (usage-based billing, etc.) and so on).
1156 Add the ability to modify the next billing date in cust_pkg, and take
1157 appropriate action. This will allow the implementation of pro-rate/1st of
1158 the month billing as well as the ability to manually fiddle with
1159 anniversary dates in cust_pkg, so you can sync a customer's anniversary
1160 date even if you're using anniversary billing (manually or automatically).
1161 (now with above, we need to have a way to automatically pro-rate /^(\d+)$/
1162 charges - anything more complicated should figure it out itself given
1163 starting and ending dates [document that!])
1165 Daily Radius log parsing into database; other logfile formats?
1167 Callbacks to enforce hourly limits on accounts (suspend until the end of
1168 the billing period?), for those who limit customers rather than tack on
1171 Flag packages (part_pkg) as taxable or non/taxable as some ISPs (for
1172 example) need to charge tax on equipment but not service (separate flags
1173 for setup and recurring fee... or perhaps a setup_tax, setup_notax,
1174 recur_tax and recur_notax fees, and possibly something more flexible if
1177 Allow for a variable number of invoices for customers who need multiple
1180 Add a mail alias service with table svc_acct (not domain mail aliasing
1181 which is domain with svc_acct_sm)
1183 (bring back from fsold) Change customer comment field from its current kludge to something more
1186 Better work orders with more information. Should eventually open a ticket
1187 when we have such a thing.
1189 edit/process/svc_wo.cgi
1190 Call tracking and trouble tickets.
1192 More accoutability for complimentary accounts: approval, expiration, term
1193 (no more than x months in advance) and notification.
1194 Flag particular users (or all users, for that matter) as having their
1195 passwords hidden and/or locked from users of Freeside (maybe need Freeside
1196 security levels first?).
1198 Better Freeside-level configurable access, for those ISP's who have
1199 employees they can't trust. Right now you're "stuck" with setting up
1200 .htaccess stuff yourself. This should really just be integrated.
1202 configuration/setup should get web interface
1204 /usr/local/etc/freeside should be configurable
1206 (probably as part of some automated installation process?)
1208 This requires some serious magic in FS::Record:
1209 ok, if date_type in fs-setup is to be something besides int,
1210 now we need to create wrappers
1211 for them so they behave identically across RDBMS's, ie date pops out as as
1212 UNIX timestamp (or an object of some sort? maybe even a blessed $obj which
1213 is a string not a hashref for backwards compatibility?) and so on. (remember
1214 to treat '0' as Not a Date instead of 1/1/70.
1216 Add Freeside-level transactions for RDBMS's which don't support
1217 transcations? (Currently we assume a minimal RDBMS which has no rollback,
1218 transactions or atomic updates). Or just require a RDBMS that supports
1219 rollback and/or atomic updates and get rid of the work-arounds? The /rdb
1220 interface had this kludge on top of it but is a technical dead-end in most
1221 other ways, unless it can gain an SQL parser and DBD interface.
1223 if i'm really bored, find the /rdb interface in fsold and port it to NoSQL,
1224 and while I'm add it add interfaces for AnyDBM_File tied hash.. hmm. Shouldn't
1225 an FS::Record have something to do with a tied hash? But we don't want
1226 performance to go gaga... maybe something with commit to help out here?
1228 Ok: FS::Record gives you a tied hash, and you get methods for commit, etc.
1230 Better automated comparison of our CC records with processors (CyberCash,
1231 at least, has not always had 100% accuracy, though recent versions are
1234 Expect or other pty based login check, where we actually connect to a
1235 terminal server or shell machine and test logging in as the user (if we
1236 are keeping a cleartext password for that user) (This is something tech
1237 support often needs for new customers)
1239 Use cust_main table for pre-sales tracking as well?
1241 Automatic commision report and check generation via freq and prog (to
1242 become a Safe perl expression) fields in agent table, and possibly others.
1244 Database and add a mailed-out date and method for disk/CD mailing, so a
1245 customer can call and you can say, "sent on xx/xx/xx via {US Mail, Fedex,
1248 Inventory tracking for physical items such as routers (for sale or
1249 lease... probably doesn't make a difference in the ordering... but if you
1250 cancel a router lease the inventory should come back. hmm.)
1252 -- Matt's wishlist ---
1254 From matt@michweb.net Fri Feb 20 16:39:53 1998
1255 Date: Thu, 19 Feb 1998 23:20:11 -0500
1256 From: Matt Simerson <matt@michweb.net>
1257 Reply-To: quadran-developer@netgoth.com
1258 To: quadran-developer@netgoth.com
1259 Subject: Re: Welcome to quadran-developer
1261 >Whats it based on and what is it supposed to do? I'm interested, but
1262 >unfortunatly, I don't have that much time to help on the project (I'm busily
1263 >working on one of my own based around MySQL and Qt right now -- don't know
1264 >if it will be GPL'ed or not yet -- we'll probably just use it in house since
1265 >it is designed around our system)...
1267 That's what I set out to find, but didn't find anything on the web site.
1268 I'm looking for something that will do the following:
1270 Single point of entry for users on a secure system:
1271 Creates account on user (public) systems
1272 update /etc/passwd/master.passwd file
1273 update radius database (if necessary)
1274 Set up up disk quotas (although I hacked adduser to do this)
1275 Option for adding user to a mailing list(s)
1276 Export of new user info to customizable report (for automated entry
1278 accounting software, etc...)
1281 Export credit card info for batch processing and have hooks built
1282 in for other forms of electronic processing.
1283 Batch-Payment (apply payments from formatted text file).
1284 Customizable reports for manual entry/importing into Accounting
1286 Email or laser print invoices
1287 Sanity checks credit card numbers before processing (code available)
1289 Simple method for disabling an account.
1290 Arbitrary Expiration Dates (on a given day, in x days)
1292 Changing password to '*'
1293 Virtual customers disabling dns, http server, log processing, etc..
1295 Billing for different account types:
1296 Dialup monthly flat rate. Prorates for partial months.
1297 Dialup monthly flat rate for x hours + hourly usage.
1300 Virtual Web accounts - w/multiple mailboxes
1301 Leased line accounts
1302 Disk space used over quota.
1303 Tech support minimum + hourly charges
1304 Other for misc stuff (modem, RAM, etc...)
1306 Per user definable RADIUS attributes (ties in with above)
1309 IP filters (for dialup email only)
1311 Keep logs of modem usage generated daily from radius accounting logs stored
1312 on multiple radius servers.
1314 Keep logs of disk usage generated from quota.
1316 Method of adding virtual domains to your system:
1317 Automatically grabs an IP address from a preassigned pool.
1318 Creates a domain.com database file from database fields
1319 Updates /etc/named.conf or /etc/named.boot and reloads named.
1320 Add's virtual.com to /etc/sendmail.cw or qmail control files.
1321 Edits your web servers httpd.conf file and restarts http server.
1322 An optional section for adding vif's can be added if the users OS
1323 supports adding them on the fly. Otherwise it's up to the end
1324 user. Make a hook that can run a custom script that the user
1325 tweaks for his system.
1326 Update or create the config file your web stats analyzer needs. I've
1327 done this for analog (free) and http-analyze. Probably
1328 should only officially support analog and let users hack
1329 it to their hearts desire.
1330 I've already written scripts that do most of the virtual web stuff on my
1331 system...in bash. Shouldn't be hard for a perlmeister to convert. In fact,
1332 as long as all the info was stored in the database (username, domain name,
1333 and ip pool) this could easily just be run as an external script that the
1334 user tweaks to match his system.
1336 We use a great accounting software (M.Y.O.B) that does all the AP, AR,
1337 Payroll, Tax stuff, and most everything else we could need. It's already
1338 set up for the type of checks we have, etc, etc... I just need something to
1339 do the billing part. I can import/export sales and payments directly once
1340 the billing part is done. You can't write accounting software as good as