History: How to build a system to demo WikiSuite

Goals

Build a full functioning WikiSuite environment where admins simply have to configure a few things to enjoy the vast feature set. Ex.:

• Set domain name and DNS
• Create some users

Options

• Generating some time-limited hosted instances with a sub-domain (ex.: abc.suite.wiki, def.suite.wiki)
  • Pros: Easy for team testing and emails will work (joe@def.suite.wiki)
  • Cons: We need to set up such a hosting infrastructure. Danger of misbehavior (spam, etc.)
• Generating a virtual machine which folks run on their environment
  • Pros: No need for hosting
  • Cons: Things like emails won't work well. Hard to share access and test tools

For any option, we need to be able to make a snapshot of a fully configured ClearOS instance, but that causes problems

• A clone of a ClearOS instance will have same ID as the original, causing issues with ClearCenter registration system
• We can't register users because we don't have the info

So perhaps we could set up a fully working WikiSuite instance as unregistered, and as they get used, admins are encouraged to register. While unregistered, some features (such as the market place) won't be available.

We want everything to work for at least 60 days without needing to register

• User creation
• Website creation

ClearOS would need to be installed as unregistered with all apps with the following pattern (because marketplace GUI is not available, they can't install via GUI). Unique system SSH keys would need to be removed before packing the virtual machine, so when each VM is booted, it gets a unique key.

Building WikiSuite with all the packages

This will install packages useful for all apps in WikiSuite (except Kimchi which is for virtualization)

• Elasticsearch and Kibana
• Fail2ban
• Openfire Meetings
• PhantomJS
• Syncthing
• PHP app
  • Tiki Wiki CMS Groupware
  • Roundcube
  • Piwik
  • FusionPBX

Add some repos

• yum-config-manager --enable clearos-epel
• yum install http://repo.okay.com.mx/centos/7/x86_64/release/okay-release-1-1.noarch.rpm
• yum install http://rpms.famillecollet.com/enterprise/remi-release-7.rpm
• yum-config-manager --enable remi-php56
• rpm --import https://packages.elastic.co/GPG-KEY-elasticsearch

• nano /etc/yum.repos.d/elasticsearch.repo

• and paste and save the following

  [elasticsearch-2.x]
  name=Elasticsearch repository for 2.x packages
  baseurl=http://packages.elastic.co/elasticsearch/2.x/centos
  gpgcheck=1
  gpgkey=http://packages.elastic.co/GPG-KEY-elasticsearch
  enabled=1

• and paste and save the following

  nano /etc/yum.repos.d/kibana.repo

• [kibana-4.4]
  name=Kibana repository for 4.4.x packages
  baseurl=http://packages.elastic.co/kibana/4.4/centos
  gpgcheck=1
  gpgkey=http://packages.elastic.co/GPG-KEY-elasticsearch
  enabled=1

Base dependencies and components

yum --enablerepo=clearos-centos install mc subversion catdoc zlib.i686 dejavu-sans-fonts fail2ban fail2ban-systemd fusionpbx-all

Standard packages

yum install app-web-server app-mariadb app-disk-usage app-file-scan app-intrusion-prevention app-mail-antivirus app-intrusion-detection app-resource-report app-system-report app-services app-software-repository app-openldap-directory phantomjs syncthing php-opcache php-mcrypt poppler-utils java elasticsearch kibana

Some special cases

yum --enablerepo=clearos-contribs install roundcubemail

Restart

service httpd restart

Questions

• What files must we delete for the system to regenerate SSH keys at next reboot?

To do

Related notes

How to find relevant package names?

• App names of an existing install are at: /var/clearos/configuration_backup/installed_apps.txt
• Format should be findable as per: https://www.clearos.com/resources/documentation/clearos/content:en_us:cc_doc_marketplace_quick_select
• See also: https://www.clearos.com/resources/documentation/clearos/index:all7apps