config file extensions

New features which should be implemented in Porteus Kiosk Edition and the kiosk wizard.
Post Reply
ch4lk
White ninja
White ninja
Posts: 19
Joined: 28 Apr 2017, 06:03
Distribution: kiosk-cloud
Location: Australia

config file extensions

Post#1 by ch4lk » 07 Nov 2018, 22:19

Would it be possible to allow file extensions besides .txt for the config files?
Unless I have been doing the wrong thing, when I don't give my kiosk config file a '.txt' extension, it won't be read/found.

I would even love it more if one did not have to give a config file an extension at all.

example:
instead of a kiosk file name 'kiosklocB.txt'
the file could be named
kiosklocB.asc
or
kiosklocB.inf
or
kioslocB.kfc [...not the chicken restaurant but: Kiosk Config File]
or simply
kiosklocB
or even with a full stop at the end of the filename to more easily distinguish it from a foldername like;
kiosklocB.
or, more in keeping with configuration files in linux
kiosklocB.conf

maybe a list of allowable config file extensions in the setup wizard?

User avatar
fanthom
Site Admin
Site Admin
Posts: 4903
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

config file extensions

Post#2 by fanthom » 08 Nov 2018, 09:28

Hello ch4lk,

From kiosk point of view file extensions does not matter as its linux:
https://askubuntu.com/questions/803434/ ... ing-system

Maybe your web or proxy servers treats the files differently based on their extension?

We use .txt by default for Windows compatibility so users can edit their remote configs in notepad, wordpad, etc.

Remote config file could be created with no extension at all:
kiosk_config=http://domain.com/files/config

at that should still work unless your web server messes things up.
I think its proxy configuration fault so if you use it then please double check it.

Thanks
Please add [Solved] to your thread title if the solution was found.

Post Reply