here's a useful thread that explains how:

http://www.concrete5.org/community/forums/chat/uploading-a-website-...

mario

easiest way on localhost is to just simply have a ton of folders off of the server document root.


when i navigate to my localhost i have 23 folders there, and in the case of concrete5latest/ i have another 10 sites under that.

So you simply place each site in it's own folder and change the config settings when you upload as final.

I find trying to do anything non-trivial on a live site not worth it.

If you are working with a site with a ton of images in the filesystem and interacting with them matters, then maybe i'd debug on the actual server, but for 99% of cases I'd say just localhost it assuming you are working on something from scratch.

Even adding content I've found much faster locally, that's just the way it is.

Sorry must misunderstand you, how do I allow multiple sites to be developed on my local machine?

your document root in apache points to a folder, each of these folders contain an instance of concrete5 for each client/site.

I've had problems with developing locally with a local server then uploading to a remote server. Particularly, backing up a remote database, restoring it locally, developing, then uploading it back again is not exactly the most efficient way to work. I don't like working in a system (like Dreamweaver seems to like to work) where everything is uploaded to the server all the time ... the network lag seems to work slowly.

I start with a blank HTML file, and use a visual CSS editor like Dreamweaver to nail by standard theme. I then use a nice editor (I prefer FlashDevelop) for managing all my files and editing text. Once I wrap up the style, I turn it into a Concrete theme and upload it to the server.

In my "Export" folder of my project directory, I keep everything that goes on the server. I duplicate server directories to make it easier to manage, and also so that I can use directory-mirroring in my FTP program, so I might have a "themes" directory, "blocks" directory, etc.

If I need to make style changes, I might edit the CSS in my static version then copy them over to the Concrete theme, or I might use a debugger (I like Opera Dragonfly the most) to edit the CSS in the browser, then I apply my changes back to the text, then double-click the CSS file in my FTP program to upload it again.

Supposedly Dreamweaver CS5 works a lot better with third-party PHP frameworks like Concrete5. I haven't tried it yet, but it sounds like it would be awesome, assuming it doesn't try to create .notes directories all over the place :)

I use ubuntu, primarily because I had enough of windows, so its a linux file system. I have concrete5 loaded in the var/www folder.

How do I make several instances then of concrete5?

I do all of my work on my Debian web server, I have a number of web sites for my user account.

This is how I have it setup. Under the home folder of my user account on the web server.

I have two folders called domains and public_html.

within the domains folder I have my development site.

/home/jva/domains/dev.mydomain.com

accessible from the web ashttp://dev.mydomain.com

within the public_html folder will be the production site.

/home/jva/public_html

accessible from the web as
http://mydomain.com

I will also use my development site to test any new updates for Concrete5 core files before applying it to production.

And I use name-based virtual hosting to have as many sites I want pointed to one IP address.

Thanks very much everyone for their input.

What I'm after is a process in which I can develop on one machine (laptop at home or the office) and then upload to the net . . .simple and easy. Just the way we do traditional web development.

Maybe there is a step by step guide somewhere.

@kappi: I have had great success using VMWare to create virtual development apache/MySQL servers exactly matching my production servers. Then it is just a matter of picking up and moving the development database/files to production. I also like the ability to make minor tweeks to production and be able to move them back to development. This is great for making sure enhancements and large changes stay compatible with production. Plus, I can break the crap out of develoment and not worry, just load a new virtual machine with database/files and be good to go :)

I do not know of a "how-to" or "tutorial" describing my process. Sorry.

I don't know about Linux, but I develop on a Mac, and I use MAMP Pro to take care of managing multiple sites. I would be surprised if there wasn't a linux equivalent.

I develop the entire install locally, including the theme and custom templates, etc, and then kick it over to the actual server when the site is ready to launch. It's normal for me to have multiple sites, all with full installs, running at the same time—usually in various stages of construction.

I'm kind of like Proteus...

Photoshop/Dreamweaver locally to do the theme, then upload to server and work on the rest of the site from there.

Hi Guys, yeah I use Lamp ( linux apache mysql and php)

but it still doesn't state how we would use multiple sites using Lamp and c5.

Once I work that one out my next problem is uploading the complete site, but hey one step at a time.

Cheers