在运行Plone扩展时覆盖完整性检查吗?

本文介绍了在运行Plone扩展时覆盖完整性检查吗?的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

我正在为我的Jira/Confluence应用程序运行带有apache服务器的Ubuntu 12.04 LTS. 现在，我需要另外安装一个Plone实例(生产). 但是Jira已经占用了8080端口，直到现在我都找不到改变它的有效说明.

I'm running Ubuntu 12.04 LTS with an apache server for my Jira/Confluence application. Now I need to additionally install an instance of Plone (production). But port 8080 is already taken by Jira and until now I couldn't find working instructions to change this.

我按照以下说明安装了plone: developer.plone/getstarted/ubuntu_production.html 在这些说明中，我是否必须照顾端口?

I followed these instructions to install plone: developer.plone/getstarted/ubuntu_production.html Do I have to take care of the port during these instructions?

我找到了该站点(2.5.创建新实例): http ://plone/documentation/manual/installing-plone/referencemanual-all-pages 表示必须更改buildout.cfg中的某些设置.但是即使是sudoer，我也无法运行这些指令.我明白了:

I have found this site (2.5. Creating New Instances): plone/documentation/manual/installing-plone/referencemanual-all-pages where it says you have to change some settings in buildout.cfg. But even as sudoer I can't run these instructions. I get this:

buildout.sanitycheck: *********************************************************** Buildout should not be run while superuser. Doing so allows untrusted code to be run as root. Instead, you probably wish to do something like: sudu -u plone_buildout bin/buildout If you have a good reason to bypass this restriction, remove the buildout.sanitycheck extension from your buildout. *********************************************************** While: Installing. Loading extensions. Error: User attempt to give system ownership to Internet *************** PICKED VERSIONS **************** [versions] *************** /PICKED VERSIONS ***************

但是如何删除健全性检查?我在此文件中找不到它.

But how can I remove the sanity check? I can't find it in this file.

推荐答案

我们在这里遇到了多个问题.

We've got multiple issues here.

更改端口

要更改Plone附加的端口，请编辑buildout.cfg并查找以下行:

To change the port Plone attaches to, edit buildout.cfg and look for the lines:

[instance] <= instance_base recipe = plone.recipe.zope2instance http-address = 8080

将"8080"更改为所需的端口.如果这是ZEO配置，请查找"client#"部件，然后更改其端口号.选择端口">"1024".编辑后，运行扩展.

Change '8080' to the desired port. If this is a ZEO configuration, look for 'client#' parts instead and change their port numbers. Choose ports > 1024. After editing, run buildout.

运行内建

如果使用sudo运行统一安装程序，则会导致其创建plone_buildout和plone_daemon系统用户. "plone_buildout"用户用于运行buildout，并拥有代码文件. "plone_daemon"用户用于运行连接到Internet的长期进程，并且拥有数据.

If you used sudo to run the Unified Installer, that caused it to create plone_buildout and plone_daemon system users. The "plone_buildout" user is meant to be used to run buildout, and owns the code files. The "plone_daemon" user is meant to be used to run the long-lived processes that connect to the Internet, and it owns the data.

此方案经过精心设计，因此您不必以root用户身份运行buildout，从而使长期存在的守护进程具有(接近)最低特权.在这种方案下，您通常使用以下命令以plone_buildout用户身份运行buildout:

This scheme is carefully contrived so that you do not have to run buildout as root, and so that the long-lived daemon processes will have (close to) minimum privileges. Under this scheme, you run buildout as the plone_buildout user, generally with the command:

sudo -u plone_buildout bin/buildout

sudo -u plone_buildout bin/buildout

命令"sudo -u username"使其余命令行在指定用户的有效所有权下执行.

The command "sudo -u username" causes the rest of the command line to be executed under the effective ownership of the specified user.

以root身份运行buildout通常是一个非常非常糟糕的主意.这就是存在健全性检查的原因.以root用户身份运行buildout意味着您将系统的控制权交给了buildout下载的每个模块中每个setup.py文件的作者. 不要这样做.

It is generally a very, very bad idea to run buildout as root. That's why the sanity check exists. Running buildout as root means that you are giving control of your system to the author of every setup.py file in every module downloaded by buildout. Don't do it.

关于一个常见误解的注释:统一安装程序通过sudo以root身份运行时，不会不以root身份运行扩展(至少不是在任何最新版本中) ).它使用root特权创建一个plone_buildout用户，然后以该用户身份运行buildout.

A note on a common misconception: The Unified Installer, when run as root, via sudo, does not run buildout as root (at least not in any recent version). It uses root privileges to create a plone_buildout user, then runs buildout as that user.