Loading...
 

History: How to build a system to demo WikiSuite

Preview of version: 91

We'll start on this as soon as most of the apps are complete.

See also WikiSuite development environment

Goals

Build a fully 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 has challenges:

  • 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.

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 the most commonly uses apps in WikiSuite. Kimchi is exempted because this will typically already be running virtualized.

Not yet properly packaged

Questions

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

rm -f /etc/ssh/*key*

To do

  • Later, we want instead to do yum-config-manager --enable clearos-epel but this is not working in unregistered mode.
  • Convert all these components to be proper ClearOS apps

How to find relevant package names?

History

Advanced
Information Version
Marc Laporte 94
View
Marc Laporte 93
View
Marc Laporte Tiki will include Cypth webmail, and track its own stats 92
View
Marc Laporte Was too optimistic... 91
View
Marc Laporte 90
View
Marc Laporte 89
View
Marc Laporte 88
View
Marc Laporte 87
View
Marc Laporte 86
View
Marc Laporte Remove old stuff so it's clear that it needs to be done 85
View
Marc Laporte 84
View
Marc Laporte was already there 83
View
Marc Laporte 82
View
Marc Laporte app-attack-detector should be standard. FusionPBX as well because we want to have freeSWITCH and configure some phone numbers for Openfire Meetings 81
View
Marc Laporte edge case 80
View
Marc Laporte 79
View
Marc Laporte autotoc 78
View
nathalie.laporte 77
View
nathalie.laporte grammar was faulty. 76
View
charles.robert 75
View
charles.robert 74
View
charles.robert 73
View
charles.robert Code Plugin modified by editor. 72
View
charles.robert 71
View
charles.robert 70
View
charles.robert 69
View
charles.robert 68
View
charles.robert 67
View
charles.robert 66
View
Marc Laporte 65
View
luis.lucio 64
View
luis.lucio 63
View
luis.lucio 62
View
luis.lucio 61
View
luis.lucio 60
View
luis.lucio Better procedure 59
View
System Administrator 58
View
System Administrator 57
View
Marc Laporte 56
View
Marc Laporte 55
View
Marc Laporte 54
View
Marc Laporte 53
View
Marc Laporte 52
View
Marc Laporte 51
View
Marc Laporte 50
View
Marc Laporte 49
View
Marc Laporte 48
View
Marc Laporte 47
View
Marc Laporte Code Plugin modified by editor. 46
View
Marc Laporte 45
View
  • «
  • 1 (current)
  • 2