--config-toml argument (#296)

Fix #284

src/conf/args.rs

@@ -126,6 +126,10 @@ pub struct Args {
     #[clap(long, value_name = "project")]
     pub project: Option<String>,
 
+    /// Configuration passed as a TOML string
+    #[clap(long)]
+    pub config_toml: Option<String>,
+
     #[clap()]
     /// What to do: either a job, or a path, or both
     pub args: Vec<String>,

src/conf/settings.rs

@@ -88,6 +88,7 @@ impl Settings {
     /// * the package level `bacon.toml` file in package-root/.bacon.toml
     /// * the package level `bacon.toml` file in package-root/.config/.bacon.toml
     /// * the file whose path is in environment variable `BACON_CONFIG`
+    /// * the content of the `--config-toml` argument
     /// * args given as arguments, coming from the cli call
     pub fn read(
         args: &Args,
@@ -122,6 +123,12 @@ impl Settings {
             }
         }
 
+        if let Some(toml) = &args.config_toml {
+            let config = toml::from_str(toml)?;
+            info!("config loaded from --config-toml: {:#?}", &config);
+            settings.apply_config(&config);
+        }
+
         settings.apply_args(args);
         settings.check()?;
         info!("settings: {:#?}", &settings);

website/docs/community/bacon-dev.md

@@ -41,3 +41,5 @@ If bacon didn't understand correctly the output of a cargo tool, it may also be
 
 If you think you might help, as a tester or coder, you're welcome, but please read [Contributing to my FOSS projects](https://dystroy.org/blog/contributing/) before starting a PR.
 
+
+**Don't open a PR without discussing the design before**, either in the chat or in an issue, unless you're just fixing a typo. Coding is the easy part. Determining the exact requirement and how we want it to be done is the hard part. This is especially important if you plan to add a dependency or to change the visible parts, eg the launch arguments.

website/docs/config.md

@@ -17,6 +17,7 @@ Bacon loads in order:
 * the `bacon.toml` file in `package-root/`
 * the `bacon.toml` file in `package-root/.config/`
 * the file whose path is in environment variable `BACON_CONFIG`
+* the content of the `--config-toml` argument
 
 Each configuration file overrides the properties of previously loaded ones.
 

website/docs/cookbook.md

@@ -150,5 +150,28 @@ You would call it with
 bacon ex -- example4578
 ```
 
+# Bacon CLI snippets
 
+You may share a command-line snippet without requiring a bacon.toml file, using the `--config-toml` argument:
+
+```bash
+bacon -j cli-test --config-toml '
+[jobs.cli-test]
+command = [
+  "sh",
+  "-c",
+  "echo \"hello $(date +%H-%M-%S)\"; cargo run",
+]
+need_stdout = true
+allow_warnings = true
+background = false
+on_change_strategy = "kill_then_restart"
+kill = ["pkill", "-TERM", "-P"]'
+```
+
+Notes:
+
+* wrap the inline configuration item in single quotes so that you may use double-quotes inside
+* this configuration is simply added to the other ones and it may refer to them
+* if you add a job this way and want it executed, either define it as `default_job` in the same inline TOML or use the `--job`/`-j` argument as in the example above