如何处理已被客户修改的白标网站的更新

发布于 2024-09-25 13:23:43 字数 595 浏览 4 评论 0原文

我计划制作一种白标产品并将其交付给客户。

该产品是使用 MVC 框架(特别是 CakePHP)开发的,其想法是让客户不仅可以修改 CSS 等基本内容,还可以修改模板。

现在,模板虽然是“视图”,但它们仍然具有一些逻辑。主要是对列表进行大量循环,并根据这些列表中的数据以不同的方式显示它们。

我关心的是更新。与任何软件一样,我们会时不时地发送更新,修复错误并添加新功能。

问题是如何最大程度地减少客户在进行这些更新时的痛苦(假设他们会自己下载并安装它们)。我在这里只是谈论视图层,这是他们应该修改的内容。如果他们触及模型或控制器,则所有赌注都会失败。

一些明显的想法是:
- 如果客户的技术水平足以使用合并工具,这实际上并不是什么大问题。
- 如果我们自己进行更新安装并将该费用计入维护费用中,那也没什么大不了的(尽管我不想成为那个必须这样做的人)。

但是,如果您有做这样的事情的经验(或者使用这样做的系统,并且其更新是由客户自己安装的),我很想听听您对我可以做的非显而易见的事情的想法,以使事情变得更容易每个人。

更新:出于良好的商业原因,我们自己托管代码不是一个选择,但我无法解决。客户将在自己的服务器上运行我们自己的 PHP 网站副本。

I'm planning to make a white-label product that will be delivered to clients.

The product is developed using an MVC framework (CakePHP in particular), and the idea is to let the customer modify not only basic stuff like the CSS, but also the templates.

Now, templates, although they are "views", they still have some logic to them. Lots of looping over lists and doing stuff to show them differently based on data in those lists, mainly.

My concern is about updates. Like any software, we'd be sending out updates every now and then, fixing bugs and adding new features.

The question is how can I minimize the pain for the customer when doing these updates (assuming they'll download them and install them by themselves). I'm just talking about the View layer here, which is what they're supposed to modify. If they touch Models or Controllers, all bets are off.

Some obvious thoughts are:
- If the customer is technical enough to use a merge tool, this is not a big deal really.
- If we do the update installations ourselves and we include that cost in our maintenance fees, that's also not a big deal (although i'd love to not be the one having to do it).

But if you've had experience doing things like this (or working with systems that do and whose updates are installed by the clients themselves), I'd love to hear your thoughts on non-obvious things I could do to make things easier for everyone.

UPDATE: Hosting the code ourselves is NOT an option, for good business reasons that I can't work around. Clients will have their own copy of our PHP website running in their own servers.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。
列表为空,暂无数据
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文