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