![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
PHP Geek? Bored?
Sep. 20th, 2004 01:40 amAmong my several headaches responsibilities is a MySQL database and its JSP interface that are in extreme need of a rewrite. The pair of them belong to a 501c3 non-profit corporation, which means that I'm keenly interested in someone willing to work pro bono, and failing that to consider their time spent a tax-deductible donation.
The current JSP interface is fragile, very buggy, and the combination of the two is completely non-portable. Moreover, I don't want to install Apache Tomcat on my production server. Therefore, I would like it rewritten in PHP.
The database is in need of minor reconfiguration, although I have a DBA onboard to assist with this.
The database and its interface already have a primitive understanding of users and groups. This needs to be extended. Ideally, it needs to be able to provide password protection on a user and/or group basis for hierarch(ies) of static HTML files. Writing a page that's really PHP or JSP that consists of a big old include statment is not really okay. I am told that this rights management can be done exactly how I want it if we use Perl for this part, but really, I don't care as long as it talks to the database above, speaks unix-like users and groups, and can protect hierarchies of static data.
There's more, but that's the basics. If you're interested, or think you know of someone who is interested, please reply here or e-mail my username at LiveJournal.
Thanks!
-- Lorrie
The current JSP interface is fragile, very buggy, and the combination of the two is completely non-portable. Moreover, I don't want to install Apache Tomcat on my production server. Therefore, I would like it rewritten in PHP.
The database is in need of minor reconfiguration, although I have a DBA onboard to assist with this.
The database and its interface already have a primitive understanding of users and groups. This needs to be extended. Ideally, it needs to be able to provide password protection on a user and/or group basis for hierarch(ies) of static HTML files. Writing a page that's really PHP or JSP that consists of a big old include statment is not really okay. I am told that this rights management can be done exactly how I want it if we use Perl for this part, but really, I don't care as long as it talks to the database above, speaks unix-like users and groups, and can protect hierarchies of static data.
There's more, but that's the basics. If you're interested, or think you know of someone who is interested, please reply here or e-mail my username at LiveJournal.
Thanks!
-- Lorrie
