On Mon, Dec 20, 2004 at 11:31:07AM -0500, Bill Catlan wrote: > Well, its not ideal, and the config file is not as well documented as it > could be. However, the instructions do say where to put stuff, and its > mostly a matter of picking 2 "top level directories" and untarring the 2 > directory trees into them (one for system libs and the other for host (or > rather, virtual host) local files).
You are right. Indeed, the biggest hassle for me was learning how to setup mysql. Even with the scripts you provided, I was still having permission problems until I performed 'grant all on fmdemo.* to [EMAIL PROTECTED]'. Dunno why it wasn't working with the sql dump you sent. After being away from MySQL for the past year, I find the grant system to be archaic and hardly intuitive. Support for SQLLite would eliminate this frustration. > Yes. SQLLite would be perfect. The config files and class structure allow > for this implementation in the future. In fact, I may make this a higher > priority to encourage support for both engines by others as well. If you could document what you had to change, it would help in the case that someone wants to add support for other databases such as PostgreSQL. > > - You do not have any automated tests to confirm the installation or > > the logic of your code. This concerns me and would prevent me from > > going further with this codebase. I'd be willing to help you get the > > Apache::Test framework working and writing some basic tests to get > > you started. > > I am not familiar with this framework or the benefits it would provide. I > am sure that I would enjoy gaining a better understanding of what you had > in mind. Examples or a further description would be a great start. I hope to be building an availability calendar for one of my clients in the next couple of weeks. If I do so, I will send you the code so that you can see the framework I'm using which includes Apache::Test and Module::Build integration. I knew there had to be a reason for multiple sets of config files and templates. To play devil's advocate, you've made installation of a simple e-commerce site twice as difficult because now I have to scrounge around in two different sets of directories which have files that contain different settings and are sometimes in different places (e.g., fmdemo/tmpl vs. flexmart/pgman/tmpl). To folks like myself wanting to quickly test the package, the extra power of being able to configure multiple sites does not overcome the hassle factor. Would it be possible for all the settings to be in one or the other config file and then add support for a master config file as an extra step? My thinking is that if someone needs that capability, they would be willing to make more effort. Regards, William -- Knowmad Services Inc. http://www.knowmad.com --------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/[email protected]/ http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
