You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Original Author: pedersen, Original Timestamp: 2011-03-10 03:33:27.875000
Original Body: Today it is a fairly common task to have one application be spread over multiple subdomain, and even though this isn't proper by domain standards. It's a common thing and we shall support it.
Is this something that can be done with apache configuration?
yes and no, you need to have apache tell your app the rewrite rules but your app needs to be aware of it too. Routes provides functions for this but they are not documented in TG.
Original Author: amolsf, Original Timestamp: 2011-03-11 01:00:54.718000
Original Body: If what is expected is to run the same application between multiple subdomains? That should be possible by using multiple WSGIScriptAlias from mod_wsgi.Have I misunderstood the ticket?
Original Author: godoy, Original Timestamp: 2011-10-02 11:54:27.226000
Original Body: What I would consider more interesting is on how to create isolated views (i.e. alternatives to the "master.html" template) based on the domain visited.
This would allow for providing customized services for different companies by using virtual hosts. Of course the database would need some change to include checks for which "customer" is using the data -- maybe using different databases? I would prefer using the same and filtering the information shown... -- and restricting or allowing their access to it based on that.
This would allow for TG to be used by companies selling customer management systems, employees management systems, etc. to hold their intelectual property by keeping their systems on their own servers while also freeing the customers to get their data through database dumps in case they want to change their service provider.
This issue existed in Trac. The original can be viewed at http://trac.turbogears.org/ticket/2181
This issue existed on SourceForge. The original can be viewed at https://sourceforge.net/p/turbogears2/tickets/12
The text was updated successfully, but these errors were encountered: