From: Justin F. <je...@ey...> - 2001-06-29 11:49:42
|
Alby: Exactly! From what you wrote, you seem to have the same kind of "problem" in anticipated administration. Now, we too have a dream that is similar, BC offers the potential. It is no secret that "shopping" carts are becoming a commodity item, say. So, for our modest environment here in eastern NC, we want to be able to sell shopping carts on the cheap for everything from mom and pops to SOHO to medium size stores. These sites will not differ too much from one another in decoration or layout. You stepped out and said your sites will differ by 10 percent. Now I think that BC is a genius concept. What I want to be able to do is write a humungous Makefile where I can sit down with a "parts list" given to me by Marketing, and type one command line that does something on the order of: 1. creates a database and tables 2. populates the database with control data 3. selects a few GIF's that are scattered around in the shopping cart for site differentiation 4. creates the php files I need that uses the modules that I have specified from pre-established sets 5. establishes a SITE_ROOT directory with a correct, prestablished convention 6. edits my httpd.conf file 7. moves things to where they should be 8. anything else necessary which would carry this list to maybe 25 items Now I _will_ restart Apache by hand to preserve my dignity. The point is, BC will, or certainly has the potential to allow this, to make a shopping cart in 5 minutes and have it running in five minutes if I have done my DNS work. BUT, for this, I need for BC to stabilize in its file layout, and, and, and... that is why it may seem like I have been nitpicking on a genius conception for something as mundane as those silly, bloody administration tasks. After your post, I don't feel as alone... Also, if you are going to write some upper-level abstract "administration tool" to do what my Makefile would do, I want to talk to you after September... Especially if you write it with gtk. Regards, _jef ====================================================================== Alby Lash wrote: > > Another boring yet real-life example of why someone wants to use BC: > > The current project I'm working on is in beta / conceptual / demo stage > right now - meaning it does all that it _needs_ to do but not very well or > reliably. > > When I rebuild it, I am planning on using BC2, and that will probably be > sometime in September. So here's the deal: > > The server will host anywhere from 3-100 sites that won't be used very often > individually, but the server itself will have a decent amount of traffic > overall allowing me to install so many different sites on a single machine. > In addition, each site will have its own db instance - I am curious to see > how this pans out. Each site will be almost identical in structure and > functionality, with maybe a 10% variation between each site instance. So, my > goal is to obviously re-use as much code as possible for each site, allowing > them to share different modules, but also have an easy way of administering > the differences between each site. > > Ok this site is using this set of interface components, ah - this site > doesn't use the common module for handling these objects, but the > specialized one I had to build for their unique situation, this db has this > extra table cell... OK I've got a new site to build let me click this button > and then change the preferences so that I can designate specialized modules > and db characteristics. > > I know this is way too specific to be of design use for BC in general, but I > thought it might help in considering some type of administration solution, > which I am going to start conceptualizing today and next week. Come > September BC2 will probably have all the kinks rolled out and I would be > psyched to contribute some administration stuff to the platform. Hopefully > by that time my php skills will be up to par. :?/ > [ Duh, what does $this->mean? ] > > Alby Lash > al...@th... > > _______________________________________________ > binarycloud-dev mailing list > bin...@li... > http://lists.sourceforge.net/lists/listinfo/binarycloud-dev -- Justin Farnsworth Eye Integrated Communications 321 South Evans - Suite 203 Greenville, NC 27858 | Tel: (252) 353-0722 |