1 $Id: TODO,v 1.32 1999-07-08 01:02:24 ivan Exp $
3 If you are interested in helping with any of these, please join the mailing
4 list (send a blank message to ivan-freeside-subscribe@sisd.com) to avoid
9 Multiple tax rates by geographic region (county, state, and county) are
10 supported; just choose View/Edit tax rates from the main menu.
12 Multiple tax rates by package are not (yet) supported.
14 On Wed, Jul 07, 1999 at 12:13:36PM -0400, Shaun Batterton wrote:
15 > How would you handle something like multiple tax rates and multiple
16 > states? For example in Connecticut, they just changed computer and/or
17 > data processing services to 3% (whatever that is), and everything else
21 > Second, when trying to add a new user I get two types of errors; first one
22 > is when I place an e-mail address and select the "submit," Freeside
23 > complains with "Error: Unknown local account (specified literally)"
25 You probably put a (local) email address in for email invoices. Freeside
26 stores these as references to the database records, so (for example) they
27 follow username changes.
29 I'm guessing you put in the email address that you were creating, and got
30 that error because it didn't exist yet. Sounds like a buglet to me. I'll
31 try to fix that soon; in the meantime you can add the invoicing email
34 Postgres `money' time sucks rocks anyway. I'll probably just require 6.5
35 and use the numeric types, which *finally* work right.
36 On Sat, Apr 24, 1999 at 12:52:00PM -0700, Mr. Poet wrote:
38 > Error creating cust_bill record: ERROR: parser:
39 > attribute 'charged' is of type 'money' but expression
40 > is of type 'float8' You will need to rewrite or cast
41 > the expression ! Check updated but unbilled packages
44 Postgres `money' time sucks rocks anyway. I'll probably just require 6.5
45 and use the numeric types, which *finally* work right (well, according to
46 the web site, anyway).
48 In the mean-time, this could probably be fixed with the reverse of
49 the kludge in FS::Record::new. This removes `$' and `,' from money fields
50 coming out of the database. Something which fixed up the data so Postgres
51 was happy with it could go in FS::Record::_quote, for data going into the
54 our data display problem might be a Freeside problem wrt not using
55 Oracle-compatible DBI syntax (uses the return value from $sth->execute as
56 a number of rows). Fixing this is on the TODO.
58 hooks for arbitrary commands out of configuration files
59 svc_acct.pm svc_acct_sm.pm etc.
61 Add this to a FAQ, along with doing it for middle names:
64 > What I'm finding difficult is how to easily
65 > customize fields. For example, I am trying to add a "middle name" field
66 > to the Customer Edit, view, etc. If I'm going about it right, it appears
67 > I have to edit the cust_main.cgi under edit and edit/process and the
68 > site_perl/cust_main.pm, as well as other things. Perhaps you could shed
69 > some light on the best way of doing this.
71 You have the basic idea. To implement that completely, I would:
72 - Add the new field to bin/fs-setup for new users
73 - Document the field in htdocs/docs/schema.html
74 - Document the change in a new file, htdocs/docs/upgrade4.html
75 * Run bin/dbdef-create
76 * Add the new field to edit/cust_main.cgi and edit/process/cust_main.cgi
78 For bonus points, I'd grep around for the various bits which use "$first
79 $last" or "$last, $first" and replace them with a method call in cust_main.pm,
80 , like search/cust_main.cgi
82 document security model:
83 Don't forget about Apache usernames - since, via the mapsecrets file, each
84 user can login to the SQL database with a different username and
85 password, you can utitilize the security model of the SQL database as
86 well. Also, each username here can point to a different configuration
87 directory where you could store user-specific configuration info. Then
88 you could link each username to one-to-many agents.
89 (The web demo works using a trivial version of this.)
91 Yes, queue processing or the equivalent via checkpoint fields on various
92 talbes (which you pick up via a pretty simple SELECT) would be really
95 default (and ordering) state/county/country config file
97 cust_main_county table to provide a preferred ordering, so the most common
98 entries would be at the top of the selection box. automatically, based on
101 hmm... maybe svc_acct__shell should check off the legal shells list if
102 applicable? yeah... cool.
104 payinfo field should me much larger than 16
107 [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.
109 javascript (yuck!) "are you sure?" confirmation on cancelations, etc.
110 (view/cust_pkg and view/svc_*)
112 get rid of time2str("%D") which formats dates in a non-y2k-safe looking fashion
113 (all the actual date handling uses UNIX timestamps and is fine)
115 uncomment expire in view/cust_pkg.cgi and find the expire cron from fsold
118 one-time/per-customer/? changes in rates and descriptions ('remembered
119 invoices'): implement by creating a new package on the fly... but it isn't
120 associated with any agent types so it won't show up for other customers to buy.
121 (but also... make sure they go away when the customer does! - need this? :
122 one-off package edits! : need a cust_pkgs or cust_part_pkgs or something table,
123 with custnum and partpkg (like type_pkgs)
124 (what happens if you hit "custom pricing" but the pricing is already custom?)
126 Lay out any remaining ugly forms better.
128 remove "records identical" warning? gets in the way of more important stuff.
129 or fix logic which tries to update identical records??
130 1.2 should be quiet enough that the error log is useful, hopefully.
132 Postgres has a maximum column length of 31 characters (but see NAMEDATALEN in
133 postgres_ext.h). part_svc has columns like: svc_acct__radius_Attribute_flag
134 (22 characters!) It seems that stuff over the limit is silently ignored,
135 so we get 4 characters back. So, Radius_Attributes are max 13 characters with
136 stock Postgres. see rfc2138 for what's affected
137 What's a good fix? (besides recompiling postgres with NAMEDATALEN 64)
138 (mysql has a 64 character max column length. others?)
140 [Mon Mar 29 06:57:56 1999] -e: Use of uninitialized value at /usr/lib/perl5/Date/Format.pm line 333.
141 (when sending mail in cust_main.pm::bill or svc_domain.pm)
143 look at DBIx::Recordset! (and Tie::DBI, and...)
145 undefined conf/lpr gives this uninfomative error:
146 [Fri Feb 26 16:42:36 1999] bill.cgi: Can't do bidirectional pipe at
148 l5/site_perl/FS/cust_main.pm line 629.
149 [Fri Feb 26 16:42:38 1999] bill.cgi: Error closing : Broken pipe at
151 l5/site_perl/FS/cust_main.pm line 631.
152 So give a meaningful error!
154 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
156 i10n: Apache::Language
158 Apache::Session? Other useful Apache::* ?
160 email invoices are only sent for the BILL payby. If setup, should statements
161 (since they're not invoices) be sent for COMP and CARD as well?
163 $cgi->keywords is causing the (hard to trace) error:
164 Use of uninitialized value at (eval 5) line 5
166 edit/cust_main.cgi gives an uninformative error message:
167 > Can't call method "agentnum" without a package or object reference at
168 > /usr/local/apache-ssl/htdocs/freeside/edit/cust_main.cgi line 116.
169 if there are no agents.
171 (is this missing on any web screens? (easy with $cust_svc->label)
172 Add the ability for services to filter information up to the package level
173 for web screens, so you can select a particlar package based
174 on username or domain name, etc.
176 Allow a cancelled/suspended/active status from packages to bubble up to
177 the customer lists. Put active, then suspended, then cancelled accounts.
178 Similar ordering on the package listing inside a single customer.
180 false laziness: edit/cust_main.cgi got some parts copied from edit/svc_acct.cgi
181 the web interface in general needs to be redone in a more abstract way.
183 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.
185 Portability: in FS::Record, $sth->execute does not return a number of rows for all DBD's. see man DBI
187 subroutine the where clause (eventually all SQL) as OO perhaps (has anyone done this?)
189 add a select method to FS::Record?
191 one-time/per-customer/? changes in rates and descriptions ('remembered
192 invoices'): implement by creating a new package on the fly... but it isn't
193 associated with any agent types so it won't show up for other customers to buy.
194 (but also... make sure they go away when the customer does! - need this? :
195 one-off package edits! : need a cust_pkgs or cust_part_pkgs or something table,
196 with custnum and partpkg (like type_pkgs)
197 (what happens if you hit "custom pricing" but the pricing is already custom?)
199 You can't delete the stuff under administration yet. Add this,
200 _including_ making sure the thing you are deleting is not in use!
202 add links on view/cust_main.cgi to setup services, like view/cust_pkg.cgi
204 FS::cust_pkg _require_'s FS::$svc, but this won't work with %FS::UID::callback
205 loading of configuration. (pry need same idea, but will run immediately if
206 context allows). Looks like error is masked by 'use FS::cust_svc' which in
207 turn 'use's FS::{svc_acct, svc_acct_sm, svc_domain}' which is now explicit
210 Allow a cancelled/suspended/active status from packages to bubble up to
211 the customer lists. Put active, then suspended, then cancelled accounts.
212 Similar ordering on the package listing inside a single customer.
214 svc_domain.pm mail sending uses Date::Format which doesn't seem to pick up
217 view/svc_domain.cgi needs to know the domain might be unaudited (cosmetic)
219 remove whois_hack set to 1 for svc_domain.pm? add all known registries and
221 .us domains and others!
222 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...
224 turn on the depriciation warnings for [e]idiot in FS::CGI. Stop using [e]idiot
225 the last places it is (htdocs/search/ htdocs/misc/ htdocs/misc/process)
227 (test cust_main.pm with cybercash v2 and v3, especially with the callback
228 stuff AND with mod_perl w/cybercash v2 kludge in package main)
229 (callback stuff should be eliminated by now)
231 bah, table/itable/*table in FS::CGI is silly.
233 doc Apache::AuthDBI as well
235 Provide sample httpd.conf files.
237 hey look: Tie::DBI! Check that out. Override its commit with something that
238 does perl-side caching for ? a performance improvement and as an emulation
239 layer to plug in f.ex mysql's atomic transactions
241 Record.pm uses does some non-portable DBI things. MySQL and Pg seem fine.
242 Fix it anyway unless we migrate to Tie::DBI.
246 cust_bill.pm uses '==' comparison on dates because they're currently ints
248 config file for allowed card types
250 write instructions for adding new services w/svc_Common.pm. Get rid of all
251 places where svc_* tables are hardcoded (rename svc_acct_pop to part_pop so
254 test and document libapache-dbi-logger (woo!)
256 radius logfile parsing and perl expression check.
258 Fix in cust_bill BUGS:
259 There is an off-by-one error in print_text which causes a visual error (Page 1
260 of 2 printed on some single-page invoices).
262 fields should be a method against a FS::Record or derived object, as well as
263 being something you can call as FS::Record::fields('tablename'). Might
264 even be able to handle both in the same routine (that would be neato).
266 Immediate removal of incorrectly entered check payments (can't take too
267 long to do this, or accounting is fubared).
269 Add code to move from one service to another (POP to SLIP/PPP, etc.).
270 This _should_ be possible by working off the rules in part_svc rather than
271 hardcoding anything in. The rules in part_svc may need some elaboration,
274 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.)
276 (bring back from fsold, ) Generalize config-sending stuff and make more configurable.
277 Expand the HylaFAX interface (also possibly generalize for other fax
278 softwar ie .comfaxe); allow things like arbitrary faxes of sales
279 literature, specific troubleshooting documents and so on. Maybe even
280 allow users to do this (though that might not belong in Freeside).
282 misc/process/sendconfig.cgi
283 Configure fax recipients via a separate box rather than using the finger
284 name or first+last from cust_main.
286 move all phone number logic out of Freeside - let HylaFAX or whatever
289 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?!
291 should be able to link on some field in email alias (right now you can link
292 on username or domain with a fallback to svcnum)
294 generalize and make configurable new invoice printing scheme in FS::cust_main::collect (past due)
296 deleting an svc_domain should delete all associated svc_acct_sm records.
297 same with a svc_acct.
299 periodic password encrypter
301 Automated, configurable notification, suspension and cancellation of
306 Allow for a future setup date on accounts.
308 sub AUTOLOAD in FS::Record should warn? die? if used with a non-existant column
311 edit (not just import, export and allow default/fixed) arbitrary radius stuff
313 edit/svc_acct.cgi and edit/process/svc_acct.cgi should deal with arbitrary radius stuff
315 radius import should take DEFAULT entry and put it in /var/spool/freeside/conf/radius-default ; svc_acct.export should use it (and doc)
317 in UI, s/State/State\/Provence/go and s/County/County\/Locality/go
319 what else (besides l10n) for i18n? (money!)
321 audit htdocs/* for things that should be libraried and things that should be
322 new methods on the objects (need to do this before implementing a new UI)
323 all the big things are done
325 some places we die() where we should &FS::CGI::idiot (and perhaps vice-versa).
326 Decide based on whether or not the "error" should show up in logs.
328 all .cgi's should use standard header/footer and idiot() subroutines. maybe HTML:: perl modules
329 for HTML creation. Maybe Embperl or something along those lines. ?
331 When running bin/bill, Fix this (Annoying but harmless):
332 Use of uninitialized value at /usr/local/lib/site_perl/FS/cust_pkg.pm line 99, <ADDRESS> chunk 4.
333 Use of uninitialized value at /usr/local/lib/site_perl/FS/cust_pkg.pm line 102, <ADDRESS> chunk 4.
334 Use of uninitialized value at /usr/local/lib/site_perl/FS/cust_pkg.pm line 105, <ADDRESS> chunk 4.
336 all cgi (but internal to the isp) places where package names are listed should also have
337 comment (like agent_type)
339 clean up $recref and other silliness and use -> calls where possible, or
340 one other alternative. clean up everything else.
341 should FS::Record use Tie::Hash? That would be very clean, but where do we
342 store the other information? Maybe you could ask any FS::Record object for a
345 change all file access from regular open(FILE,) stuff to OO, because of
346 problems scoping and passing filehandles like that.
348 the web interface should create a new object and use it instead of a blank
349 form for new records. the create method of svc_ objects should set defaults
352 sub check in man FS::table_name should be rewriteen. Get rid of $recref
353 stuff. Make sure all fields that refer to other database are checked.
355 Integration with signup disks (are there any free ones? Netscape?).
357 One-button cancel (+refund) for lusers who can't get online.
359 Keep information on virtual web servers (hostname, IP, host machine,
360 directory, etc.) and export this information for importation into the ISPs
363 Remove requirement that the first mail alias be the catchall? Still make
364 sure only one catchall per domain is defined in any case, of course.
366 Ability to move cust_pkg records from one customer to another? (proably
367 will need to cancel the old and create a new like when we move services
370 Auto-increment expired cards one year, and try again?
372 More non-US stuff - zip codes, country codes, foreign currencies, etc.
374 cust_refund.{cgi.pm} need to do cards xaxtions. (now we only have cust_credit)
376 Nicer set of integrated reporting possibilities, like weekly sales totals
377 by customer, package, agent, referral, etc., aging reports sorted by lots
378 of different things, and so on.
380 Client/server setup for users to modify their own passwords, shells, etc,
381 via passwd or secure web interface (prelminary passwd/chfn/chsh
382 replacement done). Complicated by the fact that we don't want to allow
383 incoming connections to the machine running Freeside, so we probably need
384 to have a daemon on each external shell or web machine that is contacted
385 by the Freeside machine. Be very very careful for both traditional
386 security issues and DoS problems.
388 An extension of the above to allow users to modify selected parts of their
389 own information, order and cancel services. A web interface for new
392 Expand domain name stuff to house all domain information. Export
393 named.boot/named.conf (primary and secondary) and named.{domain} files.
394 Add more registries (not just InterNIC's com org net edu)
396 Nice postscript paper invoices, rather than current ASCII invoices.
398 think about race-condititions in FS::Record and derived ->check ->insert
399 and so on, uid and username checks in svc_acct, etc.
401 Move to rsync over ssh file exportation rather than scp.
403 check 'n fix the proactive password checker. (cracklib?)
405 refunds of "BILL" payments: generate pseudo-check.
407 write batch senders and batch parsers for the different credit card processors
409 More CC processors/methods.
411 you should be able to fiddle the setup date in cust_pkg. (at least initially)
413 delete options in administration section
415 write a generic batch senders and batch parsers.
417 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
418 type stuff from cerkit)
420 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)
422 you should be able to get column types as a method against an FS::Record object
423 as well as dbdef->table($table)->column($column)->type
425 move to perl module for fuzzy and soundex searching.
427 package view needs to list extraneous services; we need to prevent the
428 creation of them so this never happens (and mark it as such in the source)
429 (the creation problem should be fixed - though they will still happen if people
430 fsck around in the data manually, so list them anyway)
432 add attribute dictionary to fs-setup as a menu, plus analyze users file to
435 Check for and report on duplicate billing accounts (cust_main, though many
436 will have a need for these so probably don't disable them outright.)
438 create a ->warn as well as a ->check method for all FS::table classes?
441 something to automate making a release and updating the web demo
443 export a debian-style (also redhat and?) /etc/group file aswell!
445 svc_acct_sm.import qmail import should pull in recipientmap people too.
447 .pm's like svc_acct.pm which need to do time-consuming things like ssh remotely
448 should fork and do them in a child.
450 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.
452 get some of { city, county, state, zip } from the missing bits if
453 possible (where can i get the data to do this? usps.gov?)
455 additional interfaces (perltk? java?)
457 Put the GPL notice in all files.
459 integrate w/IDEA's signup server
461 $cust_bill->owed database field to be eliminated, replaced by a method call
462 that calculates on the fly. make sure to grep for ->(get|set)field('owed')
463 same for cust_credit->credited
465 Export quota information.
467 move all configuration to a central place. maybe in blob's in the
468 database. maybe even things like the code to execute when a username is
469 changed can be in there, so less of the distributed scripts change between
472 Implement setup and recurring fees as Safe perl expressions rather than
473 numbers, to allow for variable-rate services. Backwards compatibility is
474 obtained because { 43 } in perl is still 43. :) Define API to pass
475 starting and ending dates and any other necessary data to expression
476 (fees are currently evaluated as Safe expressions but more work needs to
477 be done to define an opmask for various needs, write examples
478 (usage-based billing, etc.) and so on).
480 Add the ability to modify the next billing date in cust_pkg, and take
481 appropriate action. This will allow the implementation of pro-rate/1st of
482 the month billing as well as the ability to manually fiddle with
483 anniversary dates in cust_pkg, so you can sync a customer's anniversary
484 date even if you're using anniversary billing (manually or automatically).
485 (now with above, we need to have a way to automatically pro-rate /^(\d+)$/
486 charges - anything more complicated should figure it out itself given
487 starting and ending dates [document that!])
489 Daily Radius log parsing into database; other logfile formats?
491 Callbacks to enforce hourly limits on accounts (suspend until the end of
492 the billing period?), for those who limit customers rather than tack on
495 Flag packages (part_pkg) as taxable or non/taxable as some ISPs (for
496 example) need to charge tax on equipment but not service (separate flags
497 for setup and recurring fee... or perhaps a setup_tax, setup_notax,
498 recur_tax and recur_notax fees, and possibly something more flexible if
501 Allow for a variable number of invoices for customers who need multiple
504 Add a mail alias service with table svc_acct (not domain mail aliasing
505 which is domain with svc_acct_sm)
507 (bring back from fsold) Change customer comment field from its current kludge to something more
510 Better work orders with more information. Should eventually open a ticket
511 when we have such a thing.
513 edit/process/svc_wo.cgi
514 Call tracking and trouble tickets.
516 More accoutability for complimentary accounts: approval, expiration, term
517 (no more than x months in advance) and notification.
518 Flag particular users (or all users, for that matter) as having their
519 passwords hidden and/or locked from users of Freeside (maybe need Freeside
520 security levels first?).
522 Better Freeside-level configurable access, for those ISP's who have
523 employees they can't trust. Right now you're "stuck" with setting up
524 .htaccess stuff yourself. This should really just be integrated.
526 configuration/setup should get web interface
528 /usr/local/etc/freeside should be configurable
530 (probably as part of some automated installation process?)
532 This requires some serious magic in FS::Record:
533 ok, if date_type in fs-setup is to be something besides int,
534 now we need to create wrappers
535 for them so they behave identically across RDBMS's, ie date pops out as as
536 UNIX timestamp (or an object of some sort? maybe even a blessed $obj which
537 is a string not a hashref for backwards compatibility?) and so on. (remember
538 to treat '0' as Not a Date instead of 1/1/70.
540 Add Freeside-level transactions for RDBMS's which don't support
541 transcations? (Currently we assume a minimal RDBMS which has no rollback,
542 transactions or atomic updates). Or just require a RDBMS that supports
543 rollback and/or atomic updates and get rid of the work-arounds? The /rdb
544 interface had this kludge on top of it but is a technical dead-end in most
545 other ways, unless it can gain an SQL parser and DBD interface.
547 if i'm really bored, find the /rdb interface in fsold and port it to NoSQL,
548 and while I'm add it add interfaces for AnyDBM_File tied hash.. hmm. Shouldn't
549 an FS::Record have something to do with a tied hash? But we don't want
550 performance to go gaga... maybe something with commit to help out here?
552 Ok: FS::Record gives you a tied hash, and you get methods for commit, etc.
554 Better automated comparison of our CC records with processors (CyberCash,
555 at least, has not always had 100% accuracy, though recent versions are
558 Expect or other pty based login check, where we actually connect to a
559 terminal server or shell machine and test logging in as the user (if we
560 are keeping a cleartext password for that user) (This is something tech
561 support often needs for new customers)
563 Use cust_main table for pre-sales tracking as well?
565 Automatic commision report and check generation via freq and prog (to
566 become a Safe perl expression) fields in agent table, and possibly others.
568 Database and add a mailed-out date and method for disk/CD mailing, so a
569 customer can call and you can say, "sent on xx/xx/xx via {US Mail, Fedex,
572 Inventory tracking for physical items such as routers (for sale or
573 lease... probably doesn't make a difference in the ordering... but if you
574 cancel a router lease the inventory should come back. hmm.)
576 -- Matt's wishlist ---
578 From matt@michweb.net Fri Feb 20 16:39:53 1998
579 Date: Thu, 19 Feb 1998 23:20:11 -0500
580 From: Matt Simerson <matt@michweb.net>
581 Reply-To: quadran-developer@netgoth.com
582 To: quadran-developer@netgoth.com
583 Subject: Re: Welcome to quadran-developer
585 >Whats it based on and what is it supposed to do? I'm interested, but
586 >unfortunatly, I don't have that much time to help on the project (I'm busily
587 >working on one of my own based around MySQL and Qt right now -- don't know
588 >if it will be GPL'ed or not yet -- we'll probably just use it in house since
589 >it is designed around our system)...
591 That's what I set out to find, but didn't find anything on the web site.
592 I'm looking for something that will do the following:
594 Single point of entry for users on a secure system:
595 Creates account on user (public) systems
596 update /etc/passwd/master.passwd file
597 update radius database (if necessary)
598 Set up up disk quotas (although I hacked adduser to do this)
599 Option for adding user to a mailing list(s)
600 Export of new user info to customizable report (for automated entry
602 accounting software, etc...)
605 Export credit card info for batch processing and have hooks built
606 in for other forms of electronic processing.
607 Batch-Payment (apply payments from formatted text file).
608 Customizable reports for manual entry/importing into Accounting
610 Email or laser print invoices
611 Sanity checks credit card numbers before processing (code available)
613 Simple method for disabling an account.
614 Arbitrary Expiration Dates (on a given day, in x days)
616 Changing password to '*'
617 Virtual customers disabling dns, http server, log processing, etc..
619 Billing for different account types:
620 Dialup monthly flat rate. Prorates for partial months.
621 Dialup monthly flat rate for x hours + hourly usage.
624 Virtual Web accounts - w/multiple mailboxes
626 Disk space used over quota.
627 Tech support minimum + hourly charges
628 Other for misc stuff (modem, RAM, etc...)
630 Per user definable RADIUS attributes (ties in with above)
633 IP filters (for dialup email only)
635 Keep logs of modem usage generated daily from radius accounting logs stored
636 on multiple radius servers.
638 Keep logs of disk usage generated from quota.
640 Method of adding virtual domains to your system:
641 Automatically grabs an IP address from a preassigned pool.
642 Creates a domain.com database file from database fields
643 Updates /etc/named.conf or /etc/named.boot and reloads named.
644 Add's virtual.com to /etc/sendmail.cw or qmail control files.
645 Edits your web servers httpd.conf file and restarts http server.
646 An optional section for adding vif's can be added if the users OS
647 supports adding them on the fly. Otherwise it's up to the end
648 user. Make a hook that can run a custom script that the user
649 tweaks for his system.
650 Update or create the config file your web stats analyzer needs. I've
651 done this for analog (free) and http-analyze. Probably
652 should only officially support analog and let users hack
653 it to their hearts desire.
654 I've already written scripts that do most of the virtual web stuff on my
655 system...in bash. Shouldn't be hard for a perlmeister to convert. In fact,
656 as long as all the info was stored in the database (username, domain name,
657 and ip pool) this could easily just be run as an external script that the
658 user tweaks to match his system.
660 We use a great accounting software (M.Y.O.B) that does all the AP, AR,
661 Payroll, Tax stuff, and most everything else we could need. It's already
662 set up for the type of checks we have, etc, etc... I just need something to
663 do the billing part. I can import/export sales and payments directly once
664 the billing part is done. You can't write accounting software as good as