I was wondering if it is possible and how hard it would be to remote deploy the starter kit without having to install the MSI... I want to use it on my webhost but I do not know if they would install it just for me...
I have been testing it on my local server first to see if I can do it.
I installed the MSI first to copy the files and configure the web.config file, then I copied the files somewhere else to try to set it up without using the MSI package, then uninstalled it.
Installs all files -
Copied from files created by MSI package
Creates virtual directory -
Created a new IIS site at the directory where the community files are stored with appropriate host header
Adds script mappings -
Done by web.config file
Creates database -
Using existing database
Installs database objects -
Ran the provided SQL setup script
Loads sample data -
Not needed
Creates application database connection -
Done by web.config file
Creates ISP Admin account -
Done by web.config file
Creates Community Admin account -
Went to /ISPAdmin/ and created a new community and admin account
After doing all this, I went to / but it said that the application required a virtual directory or there was no community established for the domain (which there is)
So, I am wondering why it requires this and if there is any workaround to it
________________
Second question...
I installed the MSI package, trying to see if I could get the community working for / for a domain. I set the domain for the default community to localhost and a DNS pointer for the domain I was testing with to the same IP. However, when I visit / I still get the old site, and when I go to /CommunityStarterKit/ on the testing domain I get the default community...
How does community recognition work for multiple communities/domains?
Philip Heath
Philip@Heathtech.net