Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Is there any way to keep 2 sites pointing to same databaseIs there any way to keep 2 sites pointing to same database
Previous
 
Next
New Post
12/15/2009 3:23 AM
 

According to our company IT security policy we can't make CMS functionality public. Is there any way to keep 2 sites pointing to same database? Then we can make one site without CMS capability and one site with CMS capability.

Any suggestion to achieve this

Thanks

 
New Post
12/15/2009 3:30 AM
 

no, this is not a supported scenario.

there are a number of CMS modules on www.snowcovered.com, which provide additional CMS workflow capabilities and might be of help.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
12/15/2009 4:18 AM
 

Hi,

You may try our module Portal Keeper (http://www.aricie.com/en/products/simple-modules/portalkeeper.aspx), which allows to disable CMS features according to IP addresses or to domain aliases in use.

You can for instance prevent power users from connecting from an external URL, while allowing them to connect from the local intranet access.


Jesse
CTO - Aricie
 
New Post
12/24/2009 6:25 AM
 

But I achieved my objective by

1. Create 2 URL’s: one for live site which has public access, another one (portal alias) for CMS site which available only on intranet.

2.Point each URL to two different folders(same DNN content) : live site is pointed to a folder with login controls are visible false, CMS site is pointed to a folder with login controls are visible true

3.each web.config is pointed to same database

 it works fine for me. Any comments/suggestion on security or performance issues please

Thanks

 
New Post
12/24/2009 6:34 AM
 

you will need to implement a sync mechanism for files in /portals and cannot use file based caching.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Is there any way to keep 2 sites pointing to same databaseIs there any way to keep 2 sites pointing to same database


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out