DNN Forums

Ask questions about your website to get help learning DNN and help resolve issues.
Prev
Next

DNN 9.13.x in Azure WebApp multi-tenanted with isloated DBs and shared / single codebase

Forums > Installing DNN Platform
Sort:
You are not authorized to post a reply.





Alon

New Around Here



Posts:5
New Around Here




1/2/2024 3:15 AM

    Hi,

    I've been playing with and using DNN since the very early days when it ran in ASP with an Access database!
    I've used it for intranets and company web sites and I really love it.
    I'm now busy developing some custom modules and needing to run things in Azure WebApps (as per customer requirements).

    I've read that DNN can be installed in Azure WebApp as a multi-tenanted system such that each tenant has its own database and DNS entry (subdomain).

    Basically, I'd like to install DNN once, install some customer modules I'm developing once, and have multiple tenants access the software,but keeping each tenant's data completely isolated from each other. Each tenant will have their own sub-domain (tenant1.mydomain.com and tenant2.mydomain.com) thus accessing their own portal.

    I'd like to know:

    1. Is this type of installation possible?
    2. How do I go about performing this type of install / configuration for multiple tenants?
    3. Is there any way to simulate this on a local PC running under IIS on my DEV PC?
    4. Is there anything else I need to know about this?

    Thanx,

    Alon

     






    Sebastian Leupold

    Veteran Member



    Posts:539
    Veteran Member




    1/2/2024 8:44 AM
      in one DNN instance, a single SQL Server database is used.
      Even with mutiple sites within it, you cannot use multiple databases, sorry.
      You wou need to use individual DNN instances per site for your requierement.
      Each may have different DNN versions and extensions (modules. skins etc) installed.





      Michael Tobisch

      Veteran Member



      Posts:1124
      Veteran Member




      1/2/2024 8:49 AM

        Alon,

        1. Afaik (but maybe someone knows better): No. It is possible to have different portals in one installation, but they all are using the same database (separated by the PortalID). It is also possible to use the same database for different installations (using the concept of the "object qualifier"), but as nowadays there is no real need for that anymore it is a bit tricky to install (the installation routine does not give you the option) - and it is one of the most misunderstood features in DNN, so it is not actively promoted anymore.
        2. The answer above should say it...
        3. As it is not a feature of DNN: no. (btw: to set up a testing environment on your local PC you can use the dnndev.me domain with any server name. It always points to 127.0.0.1)
        4. No.

        I would go to the option to have different portals within one installation. The contents are separated by the portal ID, but you can also share content (and also users) over the portals if you want. And afair you can restrict the use of a module to one (or more, but not all, or to all) portals. 

        I know that there was MS Access support (up to version 2.1.2), but I never heard that DNN was running on (classic) ASP. The first DNN Version (and all it's predecessors, IBuSpy Workshop and IBuySpy Portal) were running on ASP.Net. Therefore excuse my question: Are you real?

        Happy DNNing!
        Michael

        Michael Tobisch
        DNN★MVP

        dnnWerk Austria
        DNN Connect
        You are not authorized to post a reply.

        These Forums are dedicated to the discussion of DNN Platform.

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

        1. If you have (suspected) security issues, please DO NOT post them in the forums but instead follow the official DNN security policy. 
        2. No Advertising. This includes the promotion of commercial and non-commercial products or services which are not directly related to DNN.
        3. 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.
        4. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
        5. No Flaming or Trolling.
        6. No Profanity, Racism, or Prejudice.
        7. Site Moderators have the final word on approving / removing a thread or post or comment.
        8. English language posting only, please.

        Would you like to help us?

        Awesome! Simply post in the forums using the link below and we'll get you started.

        Get Involved