C
chanko
hi all!
ok i'll try and keep this clean and simple
i have a web app where users can log in and manage a mini site (ie
galleries, files, news....)
and i have a web app which is the site where all that info they can
manage is displayed to the public
the way i'm handling it right now, is that for each user, i make a
copy of said public web app, and change the site_id value within the
web.config so that when you enter their url, the app knows what info
to get from the database
lately, i've been getting requests from my employer to find a way so
as to not have to copy the application for each one of our clients,
and try to see if we can implement url rewriting, where if you pass a
url
www.anyurl.com
the application can map that specific url to a site_id and load the
pertinent information
that way we only have one copy of our web application (in case we make
changes and rolling out those changes isn't such a hassle); instead of
N folders with the same web application, depending on the number of
clients we have
i hope i made myself clear
if anybody can please help me out here, to at least be directed in the
correct way to handle this situation
much appreciated
-cesar
ok i'll try and keep this clean and simple
i have a web app where users can log in and manage a mini site (ie
galleries, files, news....)
and i have a web app which is the site where all that info they can
manage is displayed to the public
the way i'm handling it right now, is that for each user, i make a
copy of said public web app, and change the site_id value within the
web.config so that when you enter their url, the app knows what info
to get from the database
lately, i've been getting requests from my employer to find a way so
as to not have to copy the application for each one of our clients,
and try to see if we can implement url rewriting, where if you pass a
url
www.anyurl.com
the application can map that specific url to a site_id and load the
pertinent information
that way we only have one copy of our web application (in case we make
changes and rolling out those changes isn't such a hassle); instead of
N folders with the same web application, depending on the number of
clients we have
i hope i made myself clear
if anybody can please help me out here, to at least be directed in the
correct way to handle this situation
much appreciated
-cesar