Learn about longtime user Rowby Goren and his great contributions to the site. We explore his method for posing questions that are likely to yield a solution, and take a look at how his career transformed from a Hollywood writer to a website entrepreneur.
Can I have multiple sites sharing the same codebase?
I have multiple sites using Coldfusion 11 and each site uses a MySQL database. Since each of my sites each use a copy of the same codebase I am wondering if there is a way to configure things so that I can have multiple websites share the same codebase. For example, www.sample.com, www.anothersite.com, test.sample.com and mysite.anothersite.com would all use the same codebase but use their own database and the URL is preserved when viewing the site.
Is there a way to configure this?
Thank you
Is there a way to configure this?
Thank you
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Where are you deploying your website?
The best option is probably to deploy it separately by domain.
What you describe is not a simple configuration/infrastructu
The best option is probably to deploy it separately by domain.
What you describe is not a simple configuration/infrastructu
I was looking at this post: how to run multiple sites on same codebase in ColdFusion base on domain or subdomain
and see that they suggest the following:
Can I have multiple domains and subdomains all point to the same IP address and still preserve the URL that is displayed when someone is viewing the site?
and see that they suggest the following:
<CFIF not CGI.HTTP_HOST EQ "www.example.com" AND not CGI.HTTP_HOST EQ "example.com">
<CFSET Application.Environment = "Dev">
...
<CFELSE>
<CFSET Application.Environment = "Prod">
...
</CFIF>
Can I have multiple domains and subdomains all point to the same IP address and still preserve the URL that is displayed when someone is viewing the site?
But which is the application server?
Apache? NginX?...
What is the current configuration? Multiple applications per website?
Does you website support multiple tenants?
Apache? NginX?...
What is the current configuration? Multiple applications per website?
Does you website support multiple tenants?
The problem is that you don't want to share the same DB.
Because of that, your application must have a way to know which DB to pick based on the logged in user.
Does you app implement this logic?
Because of that, your application must have a way to know which DB to pick based on the logged in user.
Does you app implement this logic?
If your sites are already running, you can spend a lot of non-productive time making this work. Because of the support requirements, you may spend more time making the "common code base" work than actually supporting the sites.
I have worked on one site that was set up to be viewed as a dozen different domains. But every single page was written to support that and it used a single database. I currently work on a set of four sites that have an 'almost' common code base except that each one has different CSS and javascript files that are customized to that site. Although much of the PHP code is identical, it would be difficult to make them all work off the same code on one of the sites.
I have worked on one site that was set up to be viewed as a dozen different domains. But every single page was written to support that and it used a single database. I currently work on a set of four sites that have an 'almost' common code base except that each one has different CSS and javascript files that are customized to that site. Although much of the PHP code is identical, it would be difficult to make them all work off the same code on one of the sites.
@Alex... I agree with your perspectives here.
Because of that, your application must have a way to know which DB to pick based on the logged in user.
I have a ASP.NET application where using the same database was simply not an option (databases are in a hosted environment and some of our clients need to replicate the database to their remote sites as well - construction in the middle of nowhere and need offline access to system - so we cannot replicate every other client's data along with that).
In our case, a username actually has a DOMAIN part (domain\username) were the domain is used to determine the database which we use (even to authenticate that user). We have a separate globally accessible configuration database/file which stores additional domain configuration information, such as database names, and a few custom domain settings.
The only requirement for this to work is that any places in the code where we need to do any database communication, the connection information should be parameterized so that the front end can inform which database to use. When a user logs on, it can be easily established which database they must use and this can be kept in a configuration variable of sorts (either in session or other mechanism).
In ColdFusion, this setup can be implemented using the CF Administrator and data sources. In the ColdFusion Administrator, you configure your data sources to communicate with ColdFusion. After you add a data source to the Administrator, you access it by name in any CFML tag that establishes database connections; for example, in the <cfquery datasource="#current_datas
Because of that, your application must have a way to know which DB to pick based on the logged in user.
I have a ASP.NET application where using the same database was simply not an option (databases are in a hosted environment and some of our clients need to replicate the database to their remote sites as well - construction in the middle of nowhere and need offline access to system - so we cannot replicate every other client's data along with that).
In our case, a username actually has a DOMAIN part (domain\username) were the domain is used to determine the database which we use (even to authenticate that user). We have a separate globally accessible configuration database/file which stores additional domain configuration information, such as database names, and a few custom domain settings.
The only requirement for this to work is that any places in the code where we need to do any database communication, the connection information should be parameterized so that the front end can inform which database to use. When a user logs on, it can be easily established which database they must use and this can be kept in a configuration variable of sorts (either in session or other mechanism).
In ColdFusion, this setup can be implemented using the CF Administrator and data sources. In the ColdFusion Administrator, you configure your data sources to communicate with ColdFusion. After you add a data source to the Administrator, you access it by name in any CFML tag that establishes database connections; for example, in the <cfquery datasource="#current_datas
Can I have multiple domains and subdomains all point to the same IP address and still preserve the URL that is displayed when someone is viewing the site?
Yes, have all domains and subdomains point to the same websites. Then in your application.cfc file you can check for which website is in the URL using cgi.server_name. Using a cfswitch statement, you can then assign variables for data source and layout file and website ID or whatever you need to distinguish your different websites even though they are all pointing to exactly the same folder.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial