search

plone / ai-team

This is the project repository of the Plone Automatization And Infrastructure Team (AI-team)
0 stars 0 forks source link

demoplone server with old 52.classic.demo.plone.org server has been shut down #7

Open fredvd opened 9 months ago

fredvd commented 9 months ago

This is more for documentation and informing people. Last year we moved most of our demo instances from a linode VM to the Plone docker swarm cluster. The demo sites are containers deployed from https://github.com/plone/demo.plone.org

Before, the demo sites were installed using a combination of local ansiable and buildout wizardry, graciously copied from the plone.de demo setup and this was developped from what I saw by https://starzel.de @pbauer and colleagues.

Only the 5.2 demo sites was still 'happily' running on the linode vm, until I found out somewhere at the beginning of 2023 that the daily reset function no longer worked because of git/other issues in the script. I restored the script, but about 4-6 weeks ago the reset/install script for the Plone 5.2 demo site crashed again and became unavailable. The documentation team was impacted by this because we link in the documentation also to the demo site and the linkchecker gave an alarm.

We discussed this with several people in the community: yes it would be nice to have a 'vanilla' Plone 5. site available for testing things until Plone 5.2 reaches end of life October '24. But for demonstration and marketing purposes, we should stick to presentiong the Plone 6 Volto and Clasic demo sites, and not mention Plone 5.2 when it is so close to becoming unsupported.

I have turned off the linode VM server today and will delete it in 30 days if nobody else responds

We are short on volunteer time in the community and the aiteam/marketing support teams. If somebody REALLY wants to revive the Plone 5.2 demo, there is I think a possibility with not that much effort: The current Classic Plone 6 demo that runs containerised AFAIK still uses almost the same add'on to provide default content and the admin/user login button modifications as was in the Plone 5.2 site. (plonedemo.site) . The current Plone 6 ClassicUI container setup could be backported to install and run Plone 5.2 in the demo.plone.org repo for who is up for that.

Then again: the usefullness of having a Plone 5.2 demo online is 'minimal' and a small convenience: if you need a vanilla Plone 5.2 site, clone the correct buildout.coredev branch and install.

FYI: @pbauer @mauritsvanrees @sneridagh @esteele @stevepiercy @ericof @tkimnguyen

tkimnguyen commented 9 months ago

Maybe an easier way to get a 5.2 demo site running would be to use an older Docker image.

I support not spending more effort keeping a 5.2 demo site running.