[BlueOnyx:00193] Re: Third party software

[Lucas Peyatt]

The only foreseeable problem is when a backup (raqbackup) is re-imported. I 
have seen several problems (nuonce awstats & nuonce subdomains)

On Wed, 14 Jan 2009 10:15:03 -0500, Stephanie Sullivan wrote
> Michael,
> 
> Well put an a better solution along the same line. Naming a database
> sitexxx.randomtext would be just a good and have the added advantage 
> that renaming the site will NOT rename the sitexxx reference. Since 
> most folks
> (not server admins) will not know the relationship between a given 
> site and the fqdn, even better. Brilliant!
> 
> While I'm here may I also suggest we may want to change the group on 
> a site's database files (e.g. the container directory and all files 
> within) with ownership mysql (as it is now) and the group of sitexxx 
> to match the owning site. This means the disk usage of the database 
> will be included in the site quota. I do this manually (yuck) for 
> mysql users.
> 
> Also (just thought of it, so haven't looked yet) doesn't mySQL by default
> put databases in /var/mysql or similar? If so shouldn't this become a
> softlink to somewhere on the /home partition? Sorry if I'm wrong and 
> too lazy to powerup my test machine right now as I'm supposed to be 
> working on something a client is desperate for... sigh.
> 
> Again, Michael - great thinking.
> 
>      -Stephanie
> 
> > -----Original Message-----
> > From: blueonyx-bounces at blueonyx.it [mailto:blueonyx-
> > bounces at blueonyx.it] On Behalf Of Michael Stauber
> > Sent: Wednesday, January 14, 2009 7:10 AM
> > To: BlueOnyx General Mailing List
> > Subject: [BlueOnyx:00181] Re: Third party software
> > 
> > Hi Stephanie and Chris,
> > 
> > > > With respect to Brian's applications package. We discussed naming
> > the
> > > > databases it creates with the name of the site rather than a
> > random name.
> > > > For BO I think the better solution to use the site's built-in
> > database
> > > > creation functions so the database will show up with the site and
> > can be
> > > > removed when the site is removed. I still like the idea of naming
> > the
> > > > databases with the FQDN of the site then a local name. Makes
> > determining
> > > > ownership much easier.
> > >
> > > 100% agreed.   Very much a fan of this idea.  I meet this with
> > enthusiasm.
> > 
> > Good points, as usual.
> > 
> > /me turns to the coder and says: "Make it so!" :o)
> > 
> > Although for BlueOnyx we went away from using the FQDN of the site as
> > database
> > name. Instead we name it "siteXX_db".
> > 
> > We couldn't use the FQDN, as it may get too long and MySQL has a
> > limit of how
> > long a database name can be (24 characters). Another option would
> > have been
> > to "trim" any sitename that's too long.
> > 
> > However, then you really need to cover all your bases more carefully,
> > as ...
> > 
> > www.my-superfantastic-shop-selling-flowers.com
> > ... and ...
> > www.my-superfantastic-shop-selling-cookies.com
> > 
> > ... would both get the same default MySQL database name, being:
> > 
> > www_my-superfantastic_db
> > 
> > So using the group name of the site instead (which is really unique)
> > avoids
> > that conflict.
> > 
> > As for deleting a MySQL database when the site is deleted: That's
> > currently a
> > default and would carry over to an implementation of the Webapps.
> > 
> > --
> > With best regards
> > 
> > Michael Stauber
> > _______________________________________________
> > Blueonyx mailing list
> > Blueonyx at blueonyx.it
> > http://www.blueonyx.it/mailman/listinfo/blueonyx
> 
> _______________________________________________
> Blueonyx mailing list
> Blueonyx at blueonyx.it
> http://www.blueonyx.it/mailman/listinfo/blueonyx



Lucas C Peyatt
Ohio Web Hosting & Design
lucas at ohiowebhosting.net
www.ohiowebhosting.net
937.969.4476 dayton
614.441.8169 columbus
513.258.2376 cincinnati
206.350.1292 facsimile