Instalando Plone 5.2.0 on OpenSuse 15
zypper lr -u | grep "[r]epo-"
4 | repo-debug | Debug Repository | Yes | (r ) Yes | Yes | http://download.opensuse.org/debug/distribution/leap/15.1/repo/oss/
5 | repo-debug-non-oss | Debug Repository (Non-OSS) | Yes | (r ) Yes | Yes | http://download.opensuse.org/debug/distribution/leap/15.1/repo/non-oss/
6 | repo-debug-update | Update Repository (Debug) | Yes | (r ) Yes | Yes | http://download.opensuse.org/debug/update/leap/15.1/oss/
7 | repo-debug-update-non-oss | Update Repository (Debug, Non-OSS) | Yes | (r ) Yes | Yes | http://download.opensuse.org/debug/update/leap/15.1/non-oss/
8 | repo-non-oss | Non-OSS Repository | Yes | (r ) Yes | Yes | http://download.opensuse.org/distribution/leap/15.1/repo/non-oss/
9 | repo-oss | Main Repository | Yes | (r ) Yes | Yes | http://download.opensuse.org/distribution/leap/15.1/repo/oss/
10 | repo-source | Source Repository | Yes | (r ) Yes | Yes | http://download.opensuse.org/source/distribution/leap/15.1/repo/oss/
11 | repo-source-non-oss | Source Repository (Non-OSS) | Yes | (r ) Yes | Yes | http://download.opensuse.org/source/distribution/leap/15.1/repo/non-oss/
12 | repo-update | Main Update Repository | Yes | (r ) Yes | Yes | http://download.opensuse.org/update/leap/15.1/oss/
13 | repo-update-non-oss | Update Repository (Non-Oss) | Yes | (r ) Yes | Yes | http://download.opensuse.org/update/leap/15.1/non-oss/
zypper in gcc
zypper in python2-devel
zypper in gcc-c++
zypper in zlib zlib-devel
zypper in libopenssl-1_1-devel
zypper in wv wv-devel
zypper in patch
zypper in libopenssl-devel
zypper in python2-lxml-devel
ypper in libflxmlrpc1 flxmlrpc flxmlrpc-devel
./install.sh zeo --password=XXXXXXXXXX --target=/opt/Plone-5.2.0 --clients=2
Testing /usr/bin/python2.7 for Zope/Plone requirements....
/usr/bin/python2.7 looks OK. We will use it.
Root install method chosen. Will install for use by users:
ZEO & Client Daemons: plone_daemon
Code Resources & buildout: plone_buildout
Detailed installation log being written to /home/mario.luz/Downloads/Plone/Plone-5.2.0-UnifiedInstaller-r2/install.log
Installing Plone 5.2.0 at /opt/Plone-5.2.0
Using useradd and groupadd to create users and groups.
plone_group already exists; no need to create it.
User plone_daemon already exists. No need to create it.
Adding user plone_daemon to group plone_group.
User plone_buildout already exists. No need to create it.
Adding user plone_buildout to group plone_group.
Creating Python virtual environment.
No LICENSE.txt / LICENSE found in source
New python executable in /opt/Plone-5.2.0/zeocluster/bin/python2.7
Also creating executable in /opt/Plone-5.2.0/zeocluster/bin/python
Installing setuptools, pip, wheel...
done.
Installing Python requirements in virtual environment.
Copying buildout skeleton
Building Zope/Plone; this takes a while...
Buildout completed
#####################################################################
###################### Installation Complete ######################
Plone successfully installed at /opt/Plone-5.2.0
See /opt/Plone-5.2.0/zeocluster/README.html
for startup instructions.
Use the account information below to log into the Zope Management Interface
The account has full 'Manager' privileges.
Username: admin
Password: XXXXXXXXXX
This account is created when the object database is initialized. If you change
the password later (which you should!), you'll need to use the new password.
Use this account only to create Plone sites and initial users. Do not use it
for routine login or maintenance.- If you need help, ask in our forum https://community.plone.org - Live chat channels also exists at http://plone.org/support/chat - Submit feedback and report errors at https://github.com/plone/Products.CMFPlone/issues (For install problems, https://github.com/plone/Installers-UnifiedInstaller/issue
----------------------------------------------------------------------------------------------------------------
/opt/Plone-5.2.0/zeocluster/README.html
----------------------------------------------------------------------------------------------------------------
Starting Zope/Plone
Before you start Plone, you should review the settings in:
/opt/Plone-5.2.0/zeocluster/buildout.cfg
Adjust the ports Plone uses before starting the site, if necessary, and run buildout to apply settings.
To start Plone, issue the following command in a terminal window:
sudo -u plone_daemon /opt/Plone-5.2.0/zeocluster/bin/plonectl start
To stop Plone, issue the following command in a terminal window:
sudo -u plone_daemon /opt/Plone-5.2.0/zeocluster/bin/plonectl stop
Quick operating instructions
After starting, you should be able to view the welcome page at::
http://localhost:8080/
That page offer an options to create a new Plone site and to use the lower-level Zope Management Interface (ZMI).
Use the admin password provided at:
/opt/Plone-5.2.0/zeocluster/adminPassword.txt
(If you used a GUI installer, you may have been asked for a password, and this file is not created.)
You should change the administrative password at your first convenience.
To change the admin password, click the "Password" link for the admin user at:
http://localhost:8080/acl_users/users/manage_users
Password changes will not be reflected in adminPassword.txt.
Updating After Installation
Always back up your installation before customizing or updating.
Customizing the installation
You may control most aspects of your installation, including changing ports and adding new packages and products by editing the buildout.cfg file in your instance home at /opt/Plone-5.2.0/zeocluster.
See Managing projects with zc.buildout for information on buildout options.
Apply settings by running "sudo -u plone_buildout bin/buildout" in your instance directory.
Updating the installation
To update your installation components, stop Plone, backup, edit your buildout.cfg file and run:
sudo -u plone_buildout bin/buildout
from your instance directory.
Check portal_migration in the ZMI after update to perform version migration if necessary. You may also need to visit the product installer to update product versions.