bash-commons VS mo

I think I phrased what I said poorly and unintentially communicated that I want to have all my code in one file. that' the opposite of what I'm wanting. To clarify, and I know this is splitting hairs but it illustrates my point. I think this log shell file is a good example of what I want to NOT do with my library. instead of having one file with 5 functions, I think it should be 5 files with no functions. that's to say the new file "log_info" would contain this text:

I recently had to generate multiple configuration files for Apache httpd server. My first choice was Apache Module mod_macro, however, it has too many limitations. My second choice was to use mustache templates and I was super excited that it is also available in bash! Everything seems great until I attempted to use arrays, and it did not work. Most likely because it was implemented for Bash 3.x which is 10 years old. I did not want to mess with my environment by adding or switching to older version of Bash. Because Scala is my weapon of choice, I decided for my third attempt, to try solving this problem using Scala and Twirl templating engine. I know it might seem like an overkill, however, my previous choices have failed me, so I wanted my next attempt to be the final one! 😎