Add .conf validation Linux configuration

[vicheanath]

The .conf is a Linux configuration file

https://www.redhat.com/en/topics/management/what-are-configuration-files

https://docs.fileformat.com/programming/config/

for example :

worker_processes 1;

events {
	worker_connections 1024;
}

http {
	include mime.types;
	default_type application/octet-stream;
	sendfile on;
	keepalive_timeout 65;
	server {
		listen 80;
		server_name localhost;
		location / {
			root html;
			index index.php index.html index.htm;
		}
		location /live {
			types {
				application/vnd.apple.mpegurl m3u8;
			}
			alias /home/hls/live;
			add_header Cache-Control no-cache;
		}
		location /dash {
			alias /home/dash/live;
			add_header Cache-Control no-cache;
		}
	}
}

rtmp {

	server {
		listen 1935;
		chunk size 8192;
		
		application live {
			live on;
			allow publish 127.0.0.1;
			allow publish all;
			allow play all;
			record all;
			record_path /home/video_recordings;
			record_unique on;
			hls on;
			hls_nested on;
			hls_path /home/hls;
			hls_fragment 10s;
			dash on;
			dash_path /home/dash;
			dash_nested on;
		}

		# Video on Demand
		application vod {
			play /home/vod;
		}

		# Restream
		application restream {
			live on;
			# push server1:1935
			# push server2:1935
		}

	}

}

[zhenrong-wang]

The format of Linux conf file is not strict at all. Considering there are too many distros. I think this would be a hard work.

[vicheanath]

The format of Linux conf file is not strict at all. Considering there are too many distros. I think this would be a hard work.

it's just my problem went I'm using it .conf on Nginx, and the validator should handle some paths not all types, especially nginx.conf. just idea

[kehoecj]

Maybe we add support for nginx.conf specifically as it is its own custom config format. There is a go nginx config parser we can probably use. We'd have to lock it in to only detecting files named nginx.conf or some kind of wildcard like *.nginx.conf until we can implement some parts of #5

I can see a lot of value in using the config-file-validator for to catch issues in nginx.conf files - especially for if someone is utilizing different dev/test/prod configurations

[zhenrong-wang]

The format of Linux conf file is not strict at all. Considering there are too many distros. I think this would be a hard work.

it's just my problem went I'm using it .conf on Nginx, and the validator should handle some paths not all types, especially nginx.conf. just idea

Sure, as long as the format is strict, it can be checked and handled in a programmable way. My concern is that even for application level config file such as .nginx.conf, there might be too much freedom for the format. Anyway, I think it is totally feasible, just need to figure out all the rules of the format.
A good starting point may be listing out all the critical rules of the conf file's format.

[kehoecj]

@vicheanath Are you okay closing this in favor of #100?

[vicheanath]

that's fine for me.