Handling Multiple Tenants/Instances

Legacy Uncategorised
1

Finally have some time to play with Octopus this coming weekend (yay) and thought I’d check something first.

I have an ASP.NET web application where:

  • all core libraries/dlls are versioned and centralized in the GAC
  • each tenant (client) gets its own virtual directory
  • each tenant has its own physical directory
  • physical directory contents are the same for all tenants (per version), with the exception of web.config

So what I need to take into consideration what version a given client is on when deploying., I also need to take into consideration whether the core libraries for that version have been deployed or not.

So before i get going I guess my question is – do you think Octopus is suitable for this type of setup or am i swimming against the current here?

Cheers,
-Sean

2

Hi Sean,

I think the GAC issue can be solved by checking to see if the component is already registered using a PowerShell script, so that part shouldn’t be a problem.

The virtual directory part is a problem however. It seems a lot of people would find virtual directories useful, so I’m thinking hard about a nice way to support them. I’ll keep you up to date on that.

Paul