DietPi-Config | Re-write

Created on 11 Dec 2016  路  6Comments  路  Source: MichaIng/DietPi

https://github.com/Fourdee/DietPi/issues/621#issuecomment-266234177

Needs an improved menu layout, menu names, options and cats. Basically a complete rethink of where everything goes :)

Enhancement Priority Low

Most helpful comment

@Fourdee

we can have a look, how other system sort and handle this, for example:

openmediavault

http://www.openmediavault.org/wp-content/uploads/2014/07/altnavpanel.png

or Synology Diskstation

DSM 6.1 Beta Online Demo

All 6 comments

@Fourdee

puh ... it's really difficult.

I don't know, where your journey will end up ...

Desktops? Audio Player? Multimedia? Gaming? Web-Services? NAS? IOT? Home Service? More embedded Tools and Programs? Networking? Security?

For the moment: dietpi-config


1 - System Options

  • Locale
  • Change Hostname
  • _User Data Location_ *
  • Timezone
  • Time sync mode
  • _NTP Server_ **
  • Swapfile size
  • _Log System_ *
  • Apt Mirror
  • _Apt IP Version_ **
  • Change Root Password
  • Update firmware

2 - Performance Options

  • Overclocking
  • Change CPU Governor
  • CPU Throttle Up
  • Ondemand Sample Rate
  • Ondemand Down Factor
  • CPU Max Freq Limit
  • ARM Initial Turbo
  • ARM Temp Limit
  • _SD-Card Overclocking_ **

3 - Display Options

  • Change Resolution
  • GPU/RAM Memory Split
  • HDMI Boost
  • Overscan
  • LCD Panel addon

4 - Audio Options

  • Soundcard

5 - Peripheral Options

  • Keyboard
  • Serial console
  • Remote controls **
  • Max USB current
  • I2c state
  • I2c frequency
  • RPi Camera
  • RPI Camera led

6 - Network Options

  • Ethernet
  • WiFi
  • Bluetooth
  • IPv6
  • Proxy
  • Test

7 - Connectivity Options

  • _SSH Server_ *
  • _File Server_ *
  • Samba Client
  • FTP Client
  • NFS Client

8 - Advanced Options

  • ??? **
  • _DietPi Survey_ **
  • _DietPi Update Check_ **
  • _DietPi Git Branch_ **

9 - AutoStart Options

  • Console: Manual
  • Console: Automatic
  • Kodi
  • Desktops
  • DietPi-Cloudshell
  • CAVA
  • RetroPie
  • Uae4ARM: (Fast boot)
  • Uae4ARM
  • DXX-Rebith
  • OpenTyrian

10 - Tools

  • Benchmarks
  • Stress Test

(_* = comes from dietpi-software_)
( _** = new/wishes/future options_ )


Better in dietpi-software :

  • NoIp

But nothing is fix or final.
Had to sleep some nights over it and rethink this.

Have a look and give an opinion.

@k-plan
Excellent work, I really like this layout 馃憤

A few things pop out that we could maybe move:

  • LCD Panel addon > 5 - Peripheral Options ?
  • Bluetooth > 7 - Connectivity Options?

@Fourdee

A few things pop out that we could maybe move:

  • LCD Panel addon > 5 - Peripheral Options ?
  • Bluetooth > 7 - Connectivity Options?

Yes, for sure, you can do all this.
But let me explain my consideration.

  • LCD Panel addon
    (-) yes, it is a peripheral device. It is something like a monitor/TV, especially if you use a Deskop on your device.
    But if you will switch it on or off, you have to change your display resolution, if you use a external monitor. So you don't have to navigate to a different category

  • Bluetooth
    (-) yes, it is for connectivity, just like USB, serial, WiFi, ethernet. And yes it is peripheral device, if you don't have a RPI3 for example. So peripheral is a possible option as well.
    For me, it is technical a PAN Network , so I have put it under network.

Maybe it is possible, that I have miss bearing of connectivity.
Example: Bluetooth is for me more something like Media layers ( Layer 1-3 in OSI )
Connectivity is more Host layer ( Layer 4-7 in OSI ) so I have put in here services like SSH, FTP, NFS, AFP, Samba ...

But this are only my view of things.
Don't know if it is self-explanatory and most user can/will follow this/my logic. 馃槦
Better you follow your own logic, because you have to implement, enlarge and groom it.

@Fourdee

we can have a look, how other system sort and handle this, for example:

openmediavault

http://www.openmediavault.org/wp-content/uploads/2014/07/altnavpanel.png

or Synology Diskstation

DSM 6.1 Beta Online Demo

@Fourdee @k-plan
Yey another great construction site 馃槂.

I would follow @k-plan's arguments about LCD Panel and Bluetooth:

  • LCD Panel is also some sort of display, otherwise displays are peripheral as well, where the "Display" category also contains some settings that could fit into "Performance". Finally as there are some more settings related to device visual output that need to be configured together, it makes sense to put these into a separate category, as done above.
  • Bluetooth also from my sight fits better into "Network", but it's more a feeling than knowledge based 馃槈. "Network" so far contains settings, that look more hardware related to me, where "Connectivity" looks more like software related aspects. Don't know it this separation somehow goes along with "media layer" and "host layer" 馃槅.
  • Some of the "**" features are great and I was also thinking already about the one or the other, e.g. DietPi-Survey switch and Git-Branch choose. Especially the sd card overclocking worked really great on my RPi2, pushing felt performance quite a lot, but I didn't make benchmarks, it just feels more responsive (Nextcloud navigation as well) in general. But I did not yet open an issue about it, as I read that using with non U1+ sd cards it can lead to data corruption which occurs even silently, so that you just recognize it, when it's already too late. I am a bid scared to offer this to our users, when it seems so dangerous, or what you think?
  • Maybe rename "Tools" into "Diagnostic"? Or does this imply too much assumptions?

About SSH, file server etc. in general. I am not yet sure if this is better placed within config or software. Maybe it makes sense to leave everything (especially those choices/preferences) that can be installed via dietpi-software there, so not have the same options in both scripts? Perhaps we could add a "Software config" category to dietpi-config, which contains subcategories for e.g. Samba etc. based on what is actually installed? This could be extended, e.g. by allowing some settings for webserver, database, Nextcloud/ownCloud or what we can think of in the future. Also dietpi-letsencrypt could be possibly integrated. But in this case it makes sense to leave those software settings within separate files/scripts to call from main dietpi-config in case.

Just had mood to add my thoughts, don't take this as a push at this topic, as usual we have more great ideas and opened feature requests than we can handle 馃槢.

Will get completed as/when i'am able.

In the mean time, this can be closed.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

MichaIng picture MichaIng  路  3Comments

and09 picture and09  路  3Comments

mok-liee picture mok-liee  路  3Comments

pfeerick picture pfeerick  路  3Comments

1021683053 picture 1021683053  路  3Comments