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