benluteijn / cherokee

Automatically exported from code.google.com/p/cherokee
0 stars 1 forks source link

Cherokee-Admin: Undo/Redo support #229

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
It'd be interesting if cherokee-admin supported Undo & Redo:

  http://lists.octality.com/pipermail/cherokee/2008-November/009344.html

Original issue reported on code.google.com by alobbs on 19 Nov 2008 at 6:10

GoogleCodeExporter commented 9 years ago
Probably this could be dealt with by implementing backup files - The 
configuration
could be copied over to cherokee.conf~ at cherokee-admin's startup. Or even a 
number
of backup files could be supported. That's way easier to implement, and won't 
clutter
with multi-level-undo-capabilities the interface.

Original comment by gunnarwo...@gmail.com on 20 Nov 2008 at 12:08

GoogleCodeExporter commented 9 years ago
Gunnar, that's been cherokee-admin behavior since a few months ago. Before 
writing the new file, it generates 
a cherokee.conf.backup file with configuration file content it read on start-up.

Actually, it is ${name}.backup; the configuration file name isn't hardcoded.

Original comment by alobbs on 5 Dec 2008 at 10:53

GoogleCodeExporter commented 9 years ago
Issue 194 has been merged into this issue.

Original comment by tah...@gmail.com on 20 Oct 2009 at 8:01

GoogleCodeExporter commented 9 years ago
Issue 654 has been merged into this issue.

Original comment by skar...@gmail.com on 5 Dec 2009 at 11:01

GoogleCodeExporter commented 9 years ago
Is this really necessary? I don't now any Software where you can undo/redo your 
config. Usually you have an OK/Apply button to save your changes, or "Cancel" 
to discard them.

Original comment by psaod8fz...@gmail.com on 19 Dec 2012 at 4:17

GoogleCodeExporter commented 9 years ago
The user should always have backups, anyway.

Original comment by psaod8fz...@gmail.com on 19 Dec 2012 at 4:18

GoogleCodeExporter commented 9 years ago
Undo/Redo is a feature I would like to see.

Original comment by ste...@opengeo.nl on 19 Dec 2012 at 7:19