I want to set up Multiple Wordpress Installations on a Single Domain name. I need a wordpress installation for my webdeveloper website, and other installations for developing customer websites. After development I would have to move these new websites to client server. Technical staff of my web hosting company suggested two possibilities:
1)development.domainame.com (create a subdomain for additional wordpress installation)
2)domainame.com/development (use subfolder for additional wordpress installation
They recommended to use solution 1). May I know the pro and con of each solution ? And would be a best practise ? Thx in advance
PS: I cant use multisite, not suited for my case
Your web host's technical staff is correct. You have 2 options:
Use Subdomains. ex: sub1.mydomain.com vs sub2.mydomain.com
Use Subfolders. ex: mydomain.com/folder1 vs mydomain.com/folder2
The benefit of using subdomains is that the "environments" are separated. The two websites will act like they are entirely different websites, making it easier to migrate the clients site in the future.
The benefit of using subfolders is that it's easier to "switch in between the sites". You could access all the files using the same FTP login.
I would suggest the use of subdomains. It separates the sites into 2 clearly different sites, will make it easier to restrict client/user access by-subdomain, and will decrease the chances that making a change to one site would affect the other (for example, if you have 2 wordpress sites as subfolders, it would be much easier to accidentally edit or change the wrong mysql database table)
Related
In Laravel Forge there's an option called Website Isolation, which some people also seem to mention as user isolation as well. I am not quite sure what it does and possible benefit for such functionality. It would be great if someone can explain this!
It also means you can assign different users to different sites on your server. You can give them SSH and SFTP access to a specific site without allowing them access to other sites on the same server. It also can prevent malicious code in one site from affecting another site on the same server if these sites have different users.
See https://blog.laravel.com/forge-user-isolation
I found out that one of the biggest advantages for using Website / User Isolation is that Laravel Forge will be then able to offer unique and independent nginx environment compared to other sites exist in the same server. Thus, in situations where it requires restarting an nginx or overloading, other sites in the server should work perfectly fine.
Currently I have an informational site running on .net and would like to addon ecommerce functionality via shopify. Is it possible to have a site split between two hosted locations/languages but tied together under a single domain?
so it would be wwww.domain.com/store/ instead of store.domain.com
One approach would be to use something like nginx or varnish and set backends to the various routes on your site thus merging them together to give the impression that it is all one site.
The issue you may face however would that sessions would not be shared so you'd have problems to have a cart icon with a count of items etc across the entire site.
We are planning to convert our website which is running on single server to a web farm with two servers on Windows 2008 R2. I am afraid I haven't found lot of documentation on how to achieve this. Can any one please point me to the proper documentation for this. The one document I found is
http://www.datasprings.com/resources/articles-information/creating-a-webfarm-for-your-dotnetnuke-site
This one explains using single UNC share as file server but we are looking into to use every server in the web farm as file server (i.e. have dotnetnuke folder on all the server's local drive) since UNC share becomes single point of failure. So my questions are:
Can we do DNN web farm with multiple file servers, if so, how?
And also, how does the modules updates should be done? Does it need to be done on all the servers separately or does the DNN has any inbuilt mechanism for this or do we need to use DFS replication between the servers?
Also, we use heavy caching. Since we have to use file caching in the DNN CE web farms, how does the caching works with multiple file servers?
Also, please let me know any points or gotcha that I need be aware of. Any help is greatly appreciated.
The recommended way or doing a web farm for DNN is to use a single UNC share. Even with the paid editions of DNN that is the recommended approach.
Is it possible to do it any other way, yes, but there is nothing build into DNN to help you do so.
If you want to use multiple file servers you start running into issues with file based caching, module installations, etc.
Using UNC Share is best and easy to setup method to run DNN portal on webfarm. If you use single UNC share from all servers then possibly you do not get cache issue.
I had setup webfarm of DNN portal which was running on 4 web servers and 5th one was being used as file sever (UNC share) and DNN Database server and it was working quite well.
One more thing you should consider is that - Sessions.
DNN itself do not make use of Session and session variables. But if you are using your own modules or third party modules using session then it will be good to implement Session State Server.
I am not sure if my question is suitable here. If not, forgive me.
Magento supports multi-websites on a single installation. Let's say that I'd like to make e-commerce websites for fashion industry merchants. I would install an e-commerce solution for each merchant. However, since Magento supports multiple websites on a single installation, can I just install a single Magento to support all the merchants? Each merchant has a domain and they don't share any information each other.
Or should I install a Magento for each merchant?
Thanks.
Sam
Yes, it is possible to support multiple Magento stores on one hosting account. If your hosting account allows parked domains, then it is possible to use one IP address to secure all the sites using a Unified Communications (UC) or multi-domain SSL certificate available from most vendors. Some of these certificates may support up to 100 unique domain names.
There are still other issues regarding performance that you should consider.
Depending on what you want to do this is doable. I was actually searching for a similar thing and found this resource:
Magento KB: How Multiple Websites & Stores Work
It is thus possible to have different web sites (with different domains) or a single web site with different store fronts.
I also found this explanation from the point of view of a hosting service on how to add two domains to a single Magento installation. Please note that this is specific for this service but you get the idea and the steps inside Magento should be roughly the same:
How To Setup Multiple Magento Stores
A client of mine is running an ecommerce store on godaddy shared hosting.
They are trying to pass pci compliance and the only issue is the default apache icons folder by allowing it to be indexed.
This folder is NOT in my web root. So I don't have access to it.
I've tried htaccess rewrites, but it's not working.
Anyone know of any other solutions?
I am sorry but Go Daddy shared hosting is not PCI Complaint. You can review the last part of this page to verify that: http://support.godaddy.com/help/article/4265/quick-shopping-cart-pci-compliance-faq?locale=en
turns out the scan is not required at level 4 with the amount of annual sales this client processes. So, we opted to leave it as-is.