Index: [Article Count Order] [Thread]

Date:  Tue, 30 Sep 2008 01:06:52 -0400
From:  "Stephanie Sullivan" <bq (at mark) aviaweb.com>
Subject:  [coba-e:14123] Re: MySQL Database Setup Interface
To:  <coba-e (at mark) bluequartz.org>
Message-Id:  <02ec01c922ba$5a90a4a0$0fb1ede0$@com>
In-Reply-To:  <48E14A34.2020500 (at mark) virtbiz.com>
References:  <C506812F.33820%webmaster (at mark) muntada.com> <48E12483.1080000 (at mark) probass.com> <7B51314796AE45BAADE5E056EB11E182 (at mark) OfficeKen> <200809292327.08385.bq (at mark) solarspeed.net> <48E14A34.2020500 (at mark) virtbiz.com>
X-Mail-Count: 14123

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I've chirped on this before - I'll do so again. Warning- this might come
across as a bit of a rant, sorry in advance if it does. Here is what I think
will make mySQL database management truly useful in the BQ environment:

1) Have site quota's for how many databases a site admin may setup. This
facilitates different hosting plans allowing differing numbers of databases.
2) name the databases with a base name derived from the web site name. This
is something I've exchanged email with Brian about and he agreed this would
make associating databases with sites much easier than with the random names
the webapps currently generate.
3) set the group ownership of the database files to be that of the site
(make the directory containing the files be chmod g+s and the same group as
the site - after that files created there should have the same group. This
facilitates quota enforcement and (again) tracking down databases belonging
to defunct sites.
4) phpMyAdmin is great for more advanced things, but integrated into the BQ
interface should be the following:
	a: create a database/delete a database
	b: create/modify/delete users and their privs
	   plus what databases the users may map to
	   (could be 1-to-1 to be simplier)
	c: backup/restore database (could be a ripoff
	   of code from phpMyAdmin) to a client's PC
	d: list databases and note how many more can
	   be created (i.e. 3 of 5 mySQL databases
	   are in use)

I think the above would make a nice smooth integration into BQ and integrate
into the system. Maybe I'm being a bit of a B***H about it, but a half-done
integration does not inspire client confidence and can create management
problems. A well implemented interface will enhance the client experience
AND make server management easier for the hosting provider.

A note a CPANEL - It looks kind of hacky to me (and others who have
commented on that to me). BQ looks integrated and professional by
comparison. That makes a difference. It's a feature we should promote as I
feel it's an under-appreciated differentiator.

I guess I should say "flames off" and I really really do appreciate the
great work done by Hisao, Michael, Brian, and all the other big
contributors. I try to give back, but I'm just not in that league. Which
means I'm a client for packages (like many I get from Brian) and happy to
pay for good work well done.

	Thanks,
		-Stephanie

Stephanie Sullivan, President
AVIA web development and hosting
a division of AVIA Consulting, Inc.
GSEC Certified IT Security Consultant
Phone: 508-393-0750
Mobile: 508-954-2842
FAX: 508-975-0118



> -----Original Message-----
> From: Chris Gebhardt - VIRTBIZ Internet
> [mailto:cobaltfacts (at mark) virtbiz.com]
> Sent: Monday, September 29, 2008 5:36 PM
> To: coba-e (at mark) bluequartz.org
> Subject: [coba-e:14120] Re: MySQL Database Setup Interface
> 
> Michael Stauber wrote:
> > Hi Ken,
> >
> >> To be clear; it is possible to enable the Web Apps for siteadmins,
> but it's
> >> not a good idea unless you trust them to set up better passwords
> after they
> >> install it.
> >
> > One of the updates that's currently in SVN for BlueQuartz adds
> strong password
> > checks to all password fields in the GUI. With visible confirmation
> if an
> > entered password is safe or not - while the password is being
> entered.
> >
> > That could help a little in that regards.
> 
> If I understand correctly, I think the issue with the password
> strength
> insofar as the Web Apps go is that there are very weak default
> passwords
> for the applications themselves.   For instance, if you set up a
> WordPress install it will config with default admin credentials.
> 
> Then it's up to the user to change the password to something
> different
> (whether or not it's any stronger could be questioned much of the
> time,
> but at least it wouldn't be default!)
> 
> Anyhow, that's not the fault of the installer or the app.  Just a
> matter
> of many times the customer is not very security minded and that can
> lead
> to trouble.
> 
> As far as the MySQL setup goes in the BQ GUI (in order to shift a
> little
> closer to topic) Michael's suggestion for the MySQL config sounds
> pretty
> good.  Cannot wait to give it a look!
> 
> --
> Chris Gebhardt
> VIRTBIZ Internet Services
> Access, Web Hosting, Colocation, Dedicated
> www.virtbiz.com | toll-free (866) 4 VIRTBIZ



-----BEGIN PGP SIGNATURE-----
Version: PGP Desktop 9.8.3 (Build 4028)
Charset: us-ascii

wj8DBQFI4bPtRmFh0h8+YHsRAmNgAKCidB/YJY3ZbRrUTDDvty3G8hAWhACg4fCB
1ronpGbvGfYFjSvHu6Ioph8=
=Vo+z
-----END PGP SIGNATURE-----