Improve appliance READMEs to clarify security and include manual update instructions

[JedMeister]

See what Liraz did with Jenkins README and rewrite other appliance READMEs to be somewhat in line with that.

So we want to include:

• note about what is manually installed and will require manual update
• how to do a manual update

Apps that install from upstream (using curl):

• [ ] b2evolution
• [x] bugzilla
• [ ] cakephp
• [ ] codeigniter
• [ ] collabtive
• [x] concrete-cms
• [ ] couchdb
• [x] dokuwiki (was pkg, now curl)
• [ ] e107
• [ ] elgg
• [x] espocrm
• [x] ezplatform (formerly ezpublish)
• [ ] foodsoft
• [x] foswiki (new for v15.0)
• [ ] gallery
• [ ] gnusocial
• [x] icescrum
• [ ] joomla3
• [x] limesurvey
• [x] magento
• [ ] mahara
• [x] mantis
• [ ] mediaserver
• [ ] mediaserverplus
• [ ] mibew
• [ ] moinmoin
• [ ] mongodb
• [ ] moodle
• [ ] observium
• [ ] omeka
• [x] openldap
• [x] orangehrm
• [ ] oscommerce
• [x] phpbb (formerly debian pkg, now curl)
• [ ] phplist
• [ ] phreebooks - [ ] pligg (renamed to kliqqi - then died, deprecated for v15.0)
• [x] plone
• [ ] prestashop
• [ ] processmaker
• [ ] projectpier
• [x] redmine
• [x] sahana-eden
• [x] silverstripe
• [x] simplemachines
• [ ] sitracker - [ ] sugarcrm (deprecated for v15.0)
• [x] suitecrm
• [ ] symfony
• [ ] tomatocart
• [ ] torrentserver
• [ ] tracks
• [ ] twiki
• [x] vanilla
• [x] vtiger
• [x] wordpress
• [ ] xoops
• [x] yiiframework
• [ ] zencart
• [ ] zurmo

Apps that install from upstream (using git):

• [x] punbb
• [x] simpleinvoices
• [ ] ushahidi

Apps that install from upstream (using pip):

• [ ] ansible
• [ ] couchdb

Apps that install from upstream (3rd party apt or backports)

• [x] asp-net-apache
• [x] jenkins
• [x] odoo (formerly pip, now installed via package)
• [x] matomo (formerly piwik)
• [x] syncthing
• [x] zoneminder

Apps that install from upstream using something else (e.g. Composer; Drush, etc)

• [x] drupal7 (see updated README)
• [x] drupal8 (see updated README)
• [x] typo3
• [x] ghost
• [x] mattermost
• [ ] canvas
• [x] gitlab

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[a3s7p]

TYPO3 needs to be moved to Apps that install from upstream using something else, marked as done.

[JedMeister]

:+1:

[JedMeister]

@spaghettimaster & @qq7 - when you guys find yourselves at a loose end and want some more work, this still needs doing.

Please prioritise v15.0 appliance work, but it'd be great to get this tidied up in the not too distant future!

I haven't double checked recently, so some may have already been done, but not updated here, so best to double check before doing too much work on it. Any questions, please don't hesitate to ask (here or on slack).

[JedMeister]

Just done SilverStripe: https://github.com/turnkeylinux-apps/silverstripe/commit/45749db5fa80a155ab72410b3ab1bc3fae674a5c#diff-88b99bb28683bd5b7e3a204826ead112

[OnGle]

Ping on this @JedMeister. Is this done?

[OnGle]

@JedMeister need an update on this. It needs to be moved to 17.0 or closed.

[JedMeister]

We need to go through the appliances outstanding (as per the OP) and confirm that they have notes (I've tried to update them as I've gone, but may not have noted the updates in this issue).

In the meantime, I'll move to v17.0

[UncleDan]

concrete-cms (formerly concrete5) seems up to date even before my pull request https://github.com/turnkeylinux-apps/concrete-cms/pull/24 (it is now installed via composer)

[Christie018]

I've gone through and double checked that limesurvey's readme.md file already includes information on how to manually update the appliance.

[JedMeister]

OpenLDAP no longer relevant as we're installing phpldap-admin from Debian repos now.

[l-arnold]

Odoo subjects elated to the larger subject here:

Would it be possible to not have Odoo Package install into /etc/python3 ?

It would be very nice if Odoo code were more accessible.
Also would be nice if there were some ways to "personalize" (ie Git Clone etc) the Odoo code base in a TKL container.

Related, have an issue where TKLBam migrating from 16.x to 17.x TKL Odoo, some of the data sets change and the restoration does not work. Would be best there, to have a way to move the 17.x Odoo code base into 16.x, run Database -U command (verify that that works in fact), then run a backup on 16.x system. Open 17.x system and run a restore.

[a3s7p]

@l-arnold thanks for your feedback.

Reworking the Odoo appliance to address the concerns you bring up and also making Odoo Enterprise easier to install is one of my next todo items.

I'll let you know when it happens so you can check if it fits your use cases.

[JedMeister]

@l-arnold & @a3s7p

I think a separate issue to track the Odoo specific request(s)/idea(s) here would be a good idea. I'm not sure whether it would be best to just have a single "meta" issue noting specific items (list/checklist?) or individual issues for each specific item?