----- Original Message -----
From: "Abdul-Rashid Abdullah" <webmaster (at mark) muntada.com>
To: "coba-e (at mark) bluequartz. org" <coba-e (at mark) bluequartz.org>
Sent: Monday, September 29, 2008 9:57 AM
Subject: [coba-e:14113] Re: MySQL Database Setup Interface
> I'm second!
>
> The webapp deal actually randomly generates a username/password and
> database
> name. So it is hard to tell what is what.
>
> Also, an idea I had too is putting the actual MySQL database under the
> site
> directory and drawing a symbolic link to it in the MySQL directory. This
> way the disk space used will be part of the quota, a site migration would
> catch the database as well, and it would also be easy to know what
> databases
> belong to what sites.
>
> -Regards,
>
> Rashid
>
>
> On 9/29/08 12:51 PM, "Chris Gebhardt - VIRTBIZ Internet"
> <cobaltfacts (at mark) virtbiz.com> wrote:
>
>> Michael Stauber wrote:
>>> Hi Chris,
>>> I'll pull that functionality into a separate module and will cobble
>>> something
>>> together that allows to automatically create/remove MySQL databases and
>>> users
>>> through the BlueQuartz GUI when a site is created, removed or modified.
>>
>> Sounds great. Please let us know when that's ready for release.
>>
>> *the line starts here* ;)
>
The MySQL addition is a good idea.
On the WebApp topic: One problem with the Web Apps is that you can't rellay
enable them for your customer's to be able to install themselves. The reason
is that they are sll set up with the default username and password to log
into the web app itself. So while the database login is good, the actual
login from the admin area for that app is very guessable. I had a customer
testing them all out in the default directories with the default logins.
The web apps do add lines to the apache config for the site; one thing that
would be a nice addition is to add a php_admin_value open_basedir
restriction to restrict the app to its own directory.
----
Ken Marcus
Ecommerce Web Hosting by
Precision Web Hosting, Inc.
http://www.precisionweb.net