Can c5 be set up to work on only part of a site?

Permalink
Here's a question for you ...

Can c5 be set up to work on only part of a site?

Here are some examples of what I'm asking about. Could it be set up to work on examplesite.com/anything but not on examplesite.com nor on examplesite.com/everythingelse ?

If this can be done then how?

I've read through a good number of forums and support info without finding a clear answer.
Thanks.

 
PineCreativeLabs replied on at Permalink Reply
PineCreativeLabs
Yes, you can install and run Concrete in any folder on your server. It can be installed in the root (main) directory, or in a folder, or set up as subdomain.

If you installing Concrete via FTP, simply extract the version you plan to use to the folder where you plan to run Concrete (ex. yourmainsite.com/concrete)

Hope this helps.
searchring replied on at Permalink Reply
Thanks.

Follow up questions:

Can multiple c5 installs be set up on one site?
examples:
unique install at examplesite.com/gallery
unique install at examplesite.com/products/inventory
unique install at examplesite.com/media
etc.
PineCreativeLabs replied on at Permalink Reply
PineCreativeLabs
Sort of. In this case, you might want to install Concrete once, and use an addon. There are some addons that allow you to have a "multisite". Below are some to look at:

http://www.concrete5.org/marketplace/addons/multiple-domains/...
http://www.concrete5.org/marketplace/addons/domain_mapper/...
http://www.concrete5.org/marketplace/addons/multi-url-site/...

Also, you can apply unique themes to different pages, so it would feel like having multiple sites with just once instance of Concrete. It all depends on how you set up your site structure.
searchring replied on at Permalink Reply
Thanks.

Now here's a related question:

Once c5 is set up can some folders or pages on a site be "pulled out of" c5 or not used with c5?
examples:
c5 set up on examplesite.com
but don't want c5 on examplesite.com/products/
Can this be done?
exchangecore replied on at Permalink Reply
exchangecore
Basically, if the file / folder exists in the file system then it will get loaded first, if it does not exist, that's when it goes through the concrete5 routing. See your .htaccess file on your installation for more details.