[WikiToLearn] Staging for editors

[Luca Toma]

The idea is: have a spare copy of production site to make tests about
managing content, try new templates and all this kind of stuff.

Like tuttorotto.org or wikitolearn.vodka for tech stuff but for editing
stuff

Toma Luca

2016-03-18 9:53 GMT+01:00 Sofia Liguori <s.liguori4 at campus.unimib.it>:

> I didn't get the point... what are you suggesting? A box with the most
> important conventions and templates?
>
> 2016-03-17 21:58 GMT+01:00 Luca Toma <toma.luca95 at gmail.com>:
>
>> Automatic reset can be dangerous if a work is longer than short amount of
>> time or you forgot about automatic reset.
>>
>> I think we can build something with email from mantainers or a telegram
>> bot command center
>>
>> Toma Luca
>> Il 16 mar 2016 21:43, "Riccardo Iaconelli" <riccardo at kde.org> ha scritto:
>>
>>> On Wednesday, March 16, 2016 09:12:43 PM Luca Toma wrote:
>>> > Hi!
>>> > What do you think about mantaining some kind of staging env for editing
>>> > stuff?
>>> >
>>> > For example templates, all kind of content stuff.
>>> >
>>> > The idea is create a sandbox for editors to avoid tuttorotto stuff on
>>> > production site.
>>> >
>>> > This instance will be managed as a production env (rollout, backup and
>>> > stuff like that).
>>> >
>>> > Can be usefull?
>>> >
>>> > If it is we can plain to boot it up with all new server stuff.
>>>
>>> Hi,
>>>
>>> that makes lots of sense, but can you elaborate a little more on the data
>>> management? Would it be used only for ephemeral development (i.e. reset
>>> every
>>> 24 hours), or...?
>>>
>>> Bye,
>>> -Riccardo
>>>
>>>
>>>
>>>
>> _______________________________________________
>> WikiToLearn mailing list
>> WikiToLearn at kde.org
>> https://mail.kde.org/mailman/listinfo/wikitolearn
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/wikitolearn/attachments/20160318/e4e67039/attachment.html>