为多个客户端运行Magento-单个Installaton与多个安装 [英] Running Magento for multiple clients - single Installaton vs. multiple installations

查看:75
本文介绍了为多个客户端运行Magento-单个Installaton与多个安装的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我希望为多个客户设置Magento(社区版)安装,并且已经进行了几天的研究.

I am looking to set-up a Magento (Community Edition) installation for multiple clients and have researched the matter for a few days now.

我可以看到企业版具有我所需的功能,但令人惊讶的是,我不愿意支付每年$ 12,000的单价订阅费.

I can see that the Enterprise Edition has what I need in it, but surprisingly I am not willing to shell out the $12,000 odd yearly subscription.

似乎有一些可用的选择,但我担心我会从各种选择中脱颖而出.

It seems there are a few options available to be but I am worried about the performance I will get out of the various options.

选项1)使用AITOC高级权限模块进行单次安装 所以这就是我所追求的;一次安装,这样我可以同时更新所有核心文件,还可以从一个位置管理所有商店用户.这里的问题是,我对这种额外产品的可靠性一无所知,我必须多付一些钱.我还担心,如果我有10家商店在这一装置上运行,那么它可能会减慢很多速度并产生扭曲,因为我听说过有关Magento的速度缓慢的情况.

Option 1) Single install using AITOC advanced permissions module So this is really what I am after; one installation so that I can update my core files all at the same time and also manage all my store users from one place. The problems here are that I don't know anything about the reliability of this extra product and that I have to pay a bit extra. I am also worried that if I have 10 stores running off this one installation it might all slow down so much and keel over as I have heard allot about Magento's slowness.

模块链接: http://www.aitoc.com/en/magentomods_advanced_permissions.html

选项2)每个商店在一台服务器上安装了多个Magento 因此,在这里,我在一台服务器上安装了10个Magento安装,所有安装都愉快地运行着,没有花费任何额外的资金,但是我现在有10个独立的商店来更新和维护,这可能很烦人.另外,我还无法找到使用此方法的其他人,而当我收到这些信息时,他们通常会问如何阻止其服务器死亡.因此,这条路线似乎在我的服务器上可能会变得更糟,因为我将在服务器上进行更多操作,但是如果我的服务器可以使用它,则每个Magento安装将更简单,并且由于每个人都必须运行10个而减慢运行的可能性自己开店吗?

Option 2) Multiple installations of Magento on one server for each shop So here I have 10 Magento installations on one server all running happily away not using any extra money, but I now have 10 separate stores to update and maintain which could be annoying. Also I haven't been able to find a whole lot of other people using this method and when I have they are usually asking how to stop their servers from dying. So this route seems like it could be even worse on my server as I will have more going on on my server but if my server could take it each Magento installation would be simpler and less likely to slow down due to each one having to run 10 shops on its own?

选项3)使用大量服务器和大量Magento安装 我只是不想这样做.

Option 3) Use lots of servers and lots of Magento installations I just so do not want to do this.

选项4)购买Magento Enterprise 我没有钱去做.

那么哪条路由不太可能使我的服务器崩溃?有人对模块的这一圣杯有经验吗?

So which route is less likely to blow up my server? And does anyone have experience with this holy grail of a module?

感谢您的阅读,并在此先感谢您的帮助-克里斯·霍普金斯(Chris Hopkins)

Thanks for reading and thanks in advance for any help - Chris Hopkins

推荐答案

让我们立即删除非选项.您不想做#3,而#4是非解决方案. Magento企业版未添加任何可让您从一家商店经营多个客户的功能.

Let's get the non-options out of the way right away. You don't want to do #3 and #4 is a non-solution. Magento Enterprise Edition doesn't add any features that will let you run multiple customers from one store.

现在,进入可能的选项.如您所言,#1将允许您更新代码的一个版本,但是当然这会带来一些风险.据我了解,您的客户需要进入商店吗?如果您有多个客户同时运行在一个数据库和一个代码库上,则您总是会遇到问题,因为它们相互影响.例如,谁将控制产品属性,这些属性本质上是全球性的?如果一个商店删除了产品属性,则其他商店可能会因此丢失数据.如果您解决了这个问题,那么如何进行目录促销和产品类别等.Magento的构建是为了处理多个网站,而不是将它们彼此隔离,因此您将会遇到问题.至于性能,大型产品目录或客户群会降低站点速度,但是您可以使用固定产品目录并充分利用缓存来缓解这种情况.

Now, onto possible options. As you state, #1 will allow you to update one version of the code, but of course this comes with some risks. As I understand it, your customers will need to access the stores? If you have multiple customers running on one database and one codebase, you will always run into issues with them affecting each other. For instance, who will control product attributes, which are by nature global? If one store deletes a product attribute, other stores may lose data as a result. If you solve this issue, what about catalog promotions and product categories, etc. Magento was built to handle multiple websites, but not to insulate them from each other, and you will experience problems because of this. As for performance, a large product catalog or customer base will tend to slow down the site, but you can mitigate this using the flat product catalog and making good use of caching.

对于选项2,您可以运行多个Magento商店,这带来了两个主要问题.首先,正如您所说的,正在更新站点.如果您使用的是Magento的原始安装,而不是修改核心文件,那么这应该不是问题. Magento的更新程序对于这些安装非常简单,随着您执行更多的mod以及必须使用更多的手动过程进行更新,难度会随之增加.

For option #2, you can run multiple Magento stores, which brings up two main problems. First, as you state, is updating the sites. If you are using a vanilla installation of Magento and not modifying core files, this should be a nonissue. Magento's updater is pretty simple for those installations, with difficulty increasing as you do more mods and have to use more manual processes for upating.

就性能而言,运行多个magento网站可能速度较慢,但​​这取决于您如何构造它们.无论有一个或多个站点,您都必须为每个站点加载数据,因此数据库大小不会有很大的不同.服务器上的文件大小几乎没有问题.无论哪种情况,当客户请求页面时,Magento都必须旋转整个框架来满足请求,而这正是性能问题开始显现出来的地方.最大的缓解措施之一是使用Xcode之类的操作码缓存,但是对于多台计算机,您需要为Xcache提供更多的内存来容纳所有安装程序的代码.正当问题.

As far as performance, running multiple magento sites might be slower, but it depends on how you structure them. Regardless of having one or multiple sites, you'll have to load data for each site, so database size won't be terribly different. File size on a server is pretty much a nonissue. In either case, when a customer requests a page, Magento has to spin up the entire framework to serve the request, which is where performance issues start to show themselves. One of the big mitigations for this is to use an opcode cache like Xcache, but with multiple machines you need to give Xcache much more memory to hold all the installations' code. Legitimate problem.

我的推荐?从一台计算机上启动,多次安装.逐步增加安装次数,然后在服务器不再支持时继续前进.将您的代码更改保持在核心范围之外,并使用可以轻松更新的扩展名,因此更新很容易.那应该减轻尽可能多的担忧.

My recommendation? Start on one machine, multiple installs. Work your way up on number of installs, and when the server doesn't support any more, move on. Keep your code changes out of the core and use extensions that can be easily updated, so updates are easy. That should mitigate as many of the concerns as possible.

希望有帮助!

谢谢, 乔

这篇关于为多个客户端运行Magento-单个Installaton与多个安装的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆