Apostrophe CMS:托管问题 + 在没有 Symfony 经验的情况下是否可行? [英] Apostrophe CMS: Hosting questions + feasible to get into without Symfony experience?

问题描述

我正在寻找一个干净、构建良好的 CMS.我想从我不会进一步开发的自建 CMS 迁移一些站点.

I am looking for a clean, well-built CMS. I want to migrate a number of sites away from a self-built CMS which I will not be developing further.

我遇到了 Apostrophe 并立即爱上了出色的集成用户界面.

I've come across Apostrophe and instantly fell in love with the great, integrated user interface.

它基于我几乎没有使用过的 Symfony 框架.

It is based on the Symfony framework, which I have practically no experience with.

我的问题:

• 我计划在不提供任何命令行访问的共享主机包上部署我使用此 CMS 构建的站点.我知道 Symfony 的许多开发和维护功能都依赖于对 symfony 脚本的命令行访问.将基于撇号的网站部署到这样的网络主机是否可行，或者是否可以定期访问实时产品所需的命令行工具?

• I am planning to deploy sites I build with this CMS on shared hosting packages which do not offer any command line access. I know that many of Symfony's development and maintenance functions rely on command line access to the symfony script. Is it feasible to deploy an Apostrophe-based web site to such a web host, or is access to the command line tools required for a live product on a regular basis?

老实说，我现在并不是很热衷于深入学习 Symfony:我确信这是一个很棒的框架，但我还有 吨 其他义务.我真的很喜欢 Apostrophe 为 CMS 的最终用户提供的服务.在您看来，作为一个经验丰富的 Symfony 甚至 Apostrope 开发人员，专业的 PHP 开发人员是否能够建立一个网站(在代码端没有太多的定制——前端有很多，但那是另一回事)而不是一个Symfony 专家?或者这是灾难的秘诀?

To be very honest, I'm not really keen on learning Symfony in depth right now: I'm sure it's a great framework, but I have tons of other obligations. I just really like what Apostrophe offers to the end user of the CMS. In your opinion as a seasoned Symfony or even Apostrope developer, will a professional PHP developer be able to set up a web site (without much customization on the code end - lots on the front-end, but that's a different matter) without being a Symfony expert? Or is this a recipe for disaster?

根据您的经验，是否还有其他论据支持或反对在我的情况下使用撇号?

Are there any other arguments that, from your experience, speak for or against using Apostrophe in my situation?

推荐答案

我是 P'unk Avenue 的核心 Apostrophe 开发人员之一.

I'm one of the core Apostrophe developers at P'unk Avenue.

现在，Apostrophe 的开源版本面向愿意在一定程度上跟上 Symfony 的人，是的，至少在了解 Symfony 项目的布局和学习编辑模板方面是这样.您需要具备添加新页面模板和编辑全局布局的技能.

Right now Apostrophe's open source release is oriented toward folks who are willing to get somewhat up to speed with Symfony, yes, at least so far as understanding the layout of a Symfony project and learning to edit templates. You need those skills to add new page templates and edit the global layout.

不过，您不必创建全新的 PHP 类来启动和维护 Apostrophe 站点.有时，轻量级 PHP"技能(创建新模板)就足够了.

You don't have to create entirely new PHP classes to launch and maintain an Apostrophe site, though. Sometimes "light PHP" skills (creating new templates) are all that is required.

通常 Apostrophe 生态系统是这样工作的:客户想与我们或其他开发人员合作，创建一个网站，然后他们可以自己维护，而不会出现客户不小心破坏设计、破坏设计的常见问题从 Microsoft Word 等粘贴可怕的 HTML 的布局.

Usually the Apostrophe ecosystem works like this: a client wants to work with us, or with another developer, to create a site that they can then maintain on their own without the usual problems of the client accidentally trashing the design, busting the layout with horrible HTML pasted from Microsoft Word, et cetera.

Apostrophe 通过强大的内置 HTML 过滤器和媒体插槽非常彻底地解决了这个问题，这些过滤器和媒体插槽积极管理图像和视频，以便它们针对给定的页面模板等正确显示.

Apostrophe solves that problem very thoroughly with robust built-in HTML filters and media slots that aggressively manage images and video so that they display correctly for a given page template and so on.

所以我们非常重视帮助客户(他们在自己的知识领域非常有能力，但不是设计师)安全地维护自己的内容的问题，并有一些独特的解决方案作为系统中的标准设备.

So we take the problem of helping clients (who are very competent in their own knowledge domain, but not designers) to maintain their own content safely very seriously and have some unique solutions as standard equipment in the system.

至于您的托管情况，是的，在零命令行访问的情况下很难使用 Apostrophe(或其他真正现代的 PHP 代码).Symfony 任务用于清除 Symfony 缓存并在夜间重新优化搜索引擎.您可以使用其他一些技巧来解决前者以清空缓存文件夹，而忽略后者，如果站点很小，这将起作用.

As for your hosting situation though, yes, it is difficult to use Apostrophe (or other really modern PHP code) with zero command line access. Symfony tasks are used to clear the Symfony cache and to reoptimize the search engine nightly. You could work around the former with some other hack to empty the cache folder and the latter by ignoring it, which will work if the site is small.

共享主机的另一个问题是它不会将 APC 作为字节码缓存运行.如果没有 APC，几乎所有 PHP 代码的运行速度都会慢得多.包含大量 PHP 类的系统不应该在没有 APC 的情况下运行，而且它们看起来比没有 APC 时真正准确的要慢得多.

Another problem with shared hosting is that it won't have APC running as a bytecode cache. Without APC pretty much all PHP code runs much much much slower. Systems with a lot of PHP classes are not meant to be run without APC and they appear much slower than is really accurate without APC.

我强烈建议您查看 ServerGrove (www.servergrove.com) 的产品.当您的客户可以以 20 美元/月的价格拥有一台拥有所有安全优势的虚拟机时，我认为不使用它是一个值得怀疑的决定.(使用你想要的任何主机，这里的主要原则是 VM 托管总是更安全，性能也比老式共享托管好得多.ServerGrove 确实专注于 Symfony 托管，尽管这是一个很好的优势.)

I would strongly urge you to check out the offerings of ServerGrove (www.servergrove.com). When your client can have a virtual machine all to themselves for $20/month with all the security benefits that brings, I think it's a questionable decision not to go for it. (Use whatever host you want, the main principle here is that VM hosting is always vastly more secure and performs much better than old-school shared hosting. ServerGrove does specialize in Symfony hosting though which is a nice plus.)

一些共享托管服务在这方面并不完全糟糕 - servergrove 确实有共享托管产品，但仍然没有 APC(这对于任何大型 PHP 系统来说都是一个严重的缺点，包括 WordPress 或 Drupal)但它们确实通过防止其他客户端能够通过 PHP 通过文件系统找到您的文件，为您提供 shell 访问权限并保护系统.一些共享主机根本不这样做，这是一个可怕的安全漏洞.

Some shared hosting services are not completely terrible in this regard - servergrove does have a shared hosting offering, still no APC (which is a serious disadvantage for any big PHP system, including WordPress or Drupal) but they do give you shell access and secure the system by preventing other clients from being able to find your files through the filesystem via PHP. Some shared hosts don't do that at all, which is a horrendous security hole.

有一个撇号社区可以帮助您:

There is an apostrophenow community to help you along:

http://groups.google.com/group/apostrophenow

无论您选择什么，祝您的网站好运！

Whatever you choose, good luck with your site!

这篇关于Apostrophe CMS:托管问题 + 在没有 Symfony 经验的情况下是否可行?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！