Automated message: This issue was created using the Report Issue Wizard on the Composr homesite.

I think you should just drop that feature (keep the code, don't use it). Supporting personal demos is a cost nobody is paying for, and the very notion of hosting such things implies a bigger central authority than we want to exist going forward.
Our competitors don't do it, and it was always horribly difficult to maintain and a performance worry.
Hosting demos would be a great thing for an interested third party to provide, and then this could be linked to our site however people voted for it to be.
We also are holding back the market, as companies maybe would consider having free Composr trials if we didn't effectively do the same thing.

Noted. I don't have enough of a justification to keep it if you desire we just drop it. It is an incredibly complex system to set up and lots of security problems to worry about for little benefit.

Should we leave it in the repos? My suggestion is we make a new repos for "archived" addons so we can keep them out of the main development branch and thus don't have to worry about it breaking anything being there and having to put unnecessary maintenance time into it.

> My suggestion is we make a new repos for "archived" addons

Great idea!

Noted! On the repository, I was thinking we have a folder for each archived addon (by name). The contents of the folder is the Composr file structure itself for the addon (e.g. the extracted contents of the addon tar file). Or, I can just take the tar files themselves and put them up, but others won't be able to inspect code via GitLab that way.

"The contents of the folder is the Composr file structure itself for the addon" - agreed

demonstrator is up/planned for archiving