feat: something other than yaml

[MatthewCroughan]

Can we configure this using toml or json or something? This makes it easier to write configurations from other languages.

[rochacbruno]

Hi @MatthewCroughan what exactly is the use case for writing the config from other langs?

We can add support for other formats, I am happy to take a PR

The significant lines are

marmite/src/site.rs

Lines 39 to 45 in e72ec83

	let site: Marmite = match serde_yaml::from_str::<Marmite>(config_content) {
	Ok(site) => site,
	Err(e) => {
	error!("Failed to parse config YAML: {}", e);
	process::exit(1);
	}
	};

[MatthewCroughan]

@rochacbruno in my case it would be nice to be able to use the Nix language to instruct marmite what to do, in order to generate static sites that live in the /nix/store and are produced by Ci and Nix functions. Nix functions that generate json/toml are easy, but yml not so much.

[rochacbruno]

Most of the config parameters can be passed via CLI

$ marmite path/to/folder --generate-config \
   --name MySite --tagline "Awesome website" --url mysite.com ...

This will generate a marmite.yaml on the path/to/folder