OpenWrt Forum Archive

Topic: Notepad / changelog in web interface

The content of this topic has been archived on 1 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

I would like to see a notepad option in the webinterface, Or a changelog, that can be backed up in the config file.

This way a changelog can later be used to turn in a config tutorial. etc.

Yea i know.. devs are swamped... just sharing the idea, since i can't write code. (still learning, and not much time to really build skills in that area.)

Try to create a text file in the etc\config\ folder.  You can not access it via the gui, but it should get backed up.  I just keep it on the local client I config from.

Thanks,  i hope this does the trick. 
Would be cool though if the web gui had an option to add a text editor that could access all config files.
Even if it is read only that would save time, to be able to see quickly what gets changed when you change config settings in the GUI, then look in the text file without the need to also login in a console.
It would help me a lot to figure out some gui settings.  the firewall for instance, there the Gui is better understandable then the text file.

And it would be even cooler if LuCI would write a log of all the actions it performs. Here's why: It makes re-configuration repeatable.

I have manually created a script for reconfiguring my router after flashing (I always use factory builds and re-configure - no worry about whether the settings are preserved across re-flashes...) It's a long set of LuCI commands but I can always get back to where I want to be. You can see my current set at https://github.com/richb-hanover/OpenWr … openwrt.sh

So my request would be for the web GUI to append each of the luci commands it executes to some kind of luci.log file

(Last edited by richbhanover on 30 Aug 2015, 14:59)

you could just do a  shell script o install all required and apply configs..
seems you preffer bloated/resource hungry interfaces.. 2 bad.. on this side of he screen im thinking of dropping luci...

I used this mod to add a tab to Luci for my OpenVPN log files.  I think it's an easy tweak to point it to the "text" file.
https://forum.openwrt.org/viewtopic.php?id=58715
Save your old and modified files so you can restore the original or import to your upgrade.

richbhanover wrote:

And it would be even cooler if LuCI would write a log of all the actions it performs. Here's why: It makes re-configuration repeatable.

oh yes that would be nice!   An automated changelog.
A bit like synaptic. the "Generate package download script" This allows you to replicate a setup on different hardware.

makarel wrote:

you could just do a  shell script o install all required and apply configs..
seems you preffer bloated/resource hungry interfaces.. 2 bad.. on this side of he screen im thinking of dropping luci...

It doesn't have to be default bload.
But it would be nice to have the option to by installing a package that adds this.
For me it is also bload if i need to manually open a console, browse to whatever file, open it in a text editor and do all stuff that could be avoided.    Specially for new users this could build a bridge back to the console...

Today most people can't even imagine a CLI...  So letting them view the naked config file in all its glory might get them a little exited and curious what all the 'CLI-porn' is about. 

I think it's better to have hint's already in the system instead of scaring them away with CLI talk on the first day they show a little interest. CLI is not that hard, but it is a learning curve. And for me that learning curve would have been less steep if some stuff would have been introduced to me in the GUI .

So why use CLI  for stuff that makes more sense in a GUI?

Now when people see the contents of a config file and how their GUI settings change it, then they might ask.. Hey, how do I edit this file...
Answer: Connect with SSH and type nano <filename>

And since they then already know about the changes in the config they will have less questions about that...
See it as intergated education
Noobedu.ipk

But yeah, bload is evil.

RangerZ wrote:

I used this mod to add a tab to Luci for my OpenVPN log files.  I think it's an easy tweak to point it to the "text" file.
https://forum.openwrt.org/viewtopic.php?id=58715
Save your old and modified files so you can restore the original or import to your upgrade.

indeed,

Kernel log
System log
VPN log
Change log

Or just one page that can be used to view whatever textfile?
That also makes it easy to copy and paste info for forum questions.

frietpan wrote:

It doesn't have to be default bload.
But it would be nice to have the option to by installing a package that adds this.
For me it is also bload if i need to manually open a console, browse to whatever file, open it in a text editor and do all stuff that could be avoided.    Specially for new users this could build a bridge back to the console...

Today most people can't even imagine a CLI...  So letting them view the naked config file in all its glory might get them a little exited and curious what all the 'CLI-porn' is about. 

I think it's better to have hint's already in the system instead of scaring them away with CLI talk on the first day they show a little interest. CLI is not that hard, but it is a learning curve. And for me that learning curve would have been less steep if some stuff would have been introduced to me in the GUI .

So why use CLI  for stuff that makes more sense in a GUI?

Now when people see the contents of a config file and how their GUI settings change it, then they might ask.. Hey, how do I edit this file...
Answer: Connect with SSH and type nano <filename>

And since they then already know about the changes in the config they will have less questions about that...
See it as intergated education
Noobedu.ipk

But yeah, bload is evil.

whell it would  be nice a dropdown list with all config/log files which can be edited/apply settings (its easyer to copy paste..)
i dont like eyecandy though

(Last edited by makarel on 31 Aug 2015, 14:36)

Yeah, everything that can break the barrier for noobs is a good feature.  The time they save is time they can invest in helping with other stuff.  If a CLI is included in the GUI that can do basic stuff that would save a lot of time going back and fwd to ssh clients. Having all that stuff in one place would be very welcome to me too.

frietpan wrote:

Yeah, everything that can break the barrier for noobs is a good feature.  The time they save is time they can invest in helping with other stuff.  If a CLI is included in the GUI that can do basic stuff that would save a lot of time going back and fwd to ssh clients. Having all that stuff in one place would be very welcome to me too.

CLI inside luci interface lol no.. putty does the job very well
just a plain file editor/viewer

Ah ok,

yea editor/viewer is enough...  it's not all that far away from being a CLI

I now realise that a CLI in a GUI also has security implications. hehe
I'm a bit tired today...  Seems i was not fully aware when i wrote that...  Signs of getting old LOL

having a changelog in /config  is actually working great for me.  (As long as i don't forget to make notes)
Working with multiple boxes became a bit less confusing.

The discussion might have continued from here.