Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

Customising the CMS /

running another software as addon


Reply


3 Posts   517 Views

Avatar
vonone

Community Member, 4 Posts

3 May 2012 at 10:12am

Edited: 03/05/2012 10:17am

Hi, I am new to this. Cheers
I have been playing with silverstripe. Pretty neat stuff.
I havn't contributed anything yet because I am still learning.

I wanted to run an additional custom made php software. It is a simple chat interface.
It gets its own upgrades from the developer. To pop the chat up it is a simple link.
Could be placed like a dataobject but I will integrate it into the custom modified theme I am making.

I don't need to integrate it into the CMS as it has its own back and that is ok.
what is the preferred directory to install it to.

I found a few suggestions like best to install under
/home/public_html/assets/livechat/
execute under www.example.com/livechat/
or under
/home/public_html/theme/livechat/
execute under www.example.com/theme/livechat/

I could use another URL but for consistency I want to use the same base URL and SSL cert as the CMS

The reason for my question is I don't want the file to get included in a DEV/BUILD.
Or is there a way to install it in /chat and have silverstripe skip the folder.

Thanks for your help.

Scott

Avatar
swaiba

Forum Moderator, 1799 Posts

3 May 2012 at 11:00am

Hi Scott,

Welcome to the forums!

There are two ways to make sure silverstripe doesn't include the files...

1) do not put them in "known" silverstripe folder - this is one that is there in a default install or one with a _config.php in it
2) put a file named "_manifest_exclude" in the folder

Avatar
vonone

Community Member, 4 Posts

3 May 2012 at 1:32pm

i figured a non critical folder would be ok,
but the manifest exclude is really what i wanted to know.

Thank you so much for responding so quickly. Your solution worked.

I almost everything worked ok from the start or wasn't hard to get going with some small tweaking :)