pipeline changes

git-vendor-name: ConsultantProfilePipeline-Server
git-vendor-dir: vendor/git.knownelement.com/reachableceo/ConsultantProfile-Pipeline-Server
git-vendor-repository: https://git.knownelement.com/reachableceo/ConsultantProfile-Pipeline-Server.git
git-vendor-ref: main

.gitignore

@@ -1,10 +1,3 @@
-local/build-output/JSONResume/*.json
-local/build-output/MarkdownResume/*/*.doc
-local/build-output/MarkdownResume/*/*.md
-local/build-output/MarkdownResume/*/*.pdf
-
-local/build-temp/MarkdownResume/*.yml
-local/build-temp/MarkdownResume/*.md
-local/build-temp/MarkdownResume/*/*.md
-local/build-temp/MarkdownResume/*/*.pdf
-local/build-temp/MarkdownResume/*/*.doc
+local/build-temp/*
+RenderedAssets/*
+.vscode/sftp.json

Joplin/CharlesNWyble-ConsultantProfile/CharlesNWyble-ConsultantProfile.md

@@ -0,0 +1,172 @@
+# Charles N Wyble (aka @ReachableCEO)
+
+## Enterprise Technical Solutions Architect
+
+## Executive Summary
+
+With 25+ years of enterprise infrastructure expertise, Charles N Wyble transforms businesses through comprehensive technical solutions spanning high-performance computing, enterprise security, large-scale infrastructure optimization, and advanced proprietary Claude AI implementation via The Wyble Method.
+
+His proprietary Wyble Method delivers measurable outcomes across multiple domains—reducing documentation time by 80%, increasing development velocity by 70%, and decreasing technical debt by up to 90%—creating competitive advantages others simply cannot match.
+
+He is located in the beautiful Austin TX metro area and is available for remote engagement world wide (and select on-site engagement in the USA)
+
+[Book Charles](https://supporters.reachableceo.com)  
+
+---
+
+## Professional Highlights
+
+### Core Expertise
+
+- **Enterprise Infrastructure Architecture**: Large-scale systems design & optimization
+- **Advanced Claude AI Implementation**: Proprietary methodologies for business transformation
+- **High-Performance Computing**: CUDA runtime implementation (bare metal, docker , k8s) & HPC management
+- **Enterprise Security**: Comprehensive , multi layered, in-depth requirements gathering (not just "check the box" security compliance) and development of a right sized architecture and scaleable implementation over time.
+- **Incident response** : Full service incident response/containment/mitigation and remediation.  
+
+### Key Achievements
+
+- **Disney**: Managed $8 billion capital deployment with 86-day datacenter implementation
+- **HostGator**: Reduced operational overhead by 60% through automation
+- **TippingPoint**: Supported 50,000 daily CI/CD deployments with 99.99% reliability
+- **Evite**: Built email infrastructure handling 1M+ messages per minute
+
+---
+
+## Business Impact Results
+
+1. **Enterprise Infrastructure Optimization**: For a Fortune 100 client, Charles reduced physical/virtual/container/embedded appliance provisioning time by 95% and eliminated 80+ hours of weekly maintenance through a custom cloud orchestration system. This enabled teams to focus on revenue-generating activities instead of infrastructure management, resulting in $5M annual operational savings.
+
+2. **AI-Powered Technical Documentation**: Charles transformed enterprise documentation systems using Claude AI for a stealth aerospace startup client, reducing update cycles from weeks to minutes while cutting maintenance costs by 95% and improving knowledge retention across technical and business teams, resulting in measurable improvements in both developer and end-user satisfaction.
+
+---
+
+## The Wyble Method™ for Claude Implementation
+
+### A Proprietary Framework for Enterprise Business Transformation
+
+The Wyble Method™ transforms how organizations leverage Claude AI technology through a structured approach that delivers measurable business outcomes:
+
+#### Phase 1: Discovery & Strategy
+
+- Claude-powered stakeholder interviews identify precise requirements with 70% greater accuracy
+- Business objective mapping connects technical solutions to financial outcomes
+- Opportunity assessment quantifies potential ROI across operations
+
+#### Phase 2: Implementation & Integration
+
+- Custom prompt engineering unlocks capabilities beyond typical use cases
+- Seamless integration with existing workflows and systems
+- Specialized training ensures teams maximize Claude's potential
+
+#### Phase 3: Optimization & Scale
+
+- Continuous refinement based on performance metrics
+- Progressive expansion across business functions
+- Proprietary SDLC integration for software development acceleration
+
+#### Typical Business Outcomes
+
+- 40% reduction in documentation time
+- 70% increase in development velocity
+- 90% improvement in requirements accuracy
+- 95% decrease in rework and technical debt
+
+*"The Wyble Method doesn't just implement Claude—it transforms how organizations operate, creating competitive advantages through AI that others simply cannot match."*
+
+---
+
+## Service Offerings
+
+### Strategic Technical Consulting
+
+Comprehensive enterprise infrastructure assessment, optimization planning, and implementation oversight to align technology with business objectives and maximize ROI.
+
+### Infrastructure Implementation & Migration
+
+End-to-end execution of complex enterprise infrastructure projects with zero unplanned downtime, thorough knowledge transfer, and complete documentation.
+
+### Claude AI Business Integration
+
+Transform operations through advanced Claude implementation using proprietary methodologies that unlock capabilities beyond typical use cases, tailored for enterprise environments.
+
+---
+
+## Pricing & Engagement Options
+
+### Premium Service Tiers
+
+| Expertise Level | Delivery Format | Pricing | Ideal For |
+|-----------------|-----------------|------------|-----------|
+| **Enterprise Operations** | Remote Consulting | $150/hour | System optimization, infrastructure deployment |
+| **Specialized Solutions** | Remote Consulting | $250/hour | Bespoke architectures, Claude implementation |
+| **On-Site Expertise** | In-Person | $1,000/day* | Critical deployments, team training, strategic planning |
+| **Software Development** | Project-Based | From $10,000** | Custom solutions for truly bespoke business needs. |
+
+*Plus prepaid travel expenses  
+**$5,000 due upon project initiation
+
+### Software Development Process
+
+- **Initial Consultation:** (remote) $2,500 (non refundable, not credited toward project upon engagement)
+
+### Delivery & Artifact Management
+
+All engagements include (as standard) complete source code and documentation delivery to client.
+
+Additional delivery options:
+
+| Artifact Service | Description | Price|
+|------------------|-------------|------------|
+| **Certified Destruction Upon Completion** | Secure removal of all artifacts from ReachableCEO Enterprises systems after project handover | $2,000 fee |
+| **Complete Transfer** | Full knowledge transfer and ownership of artifacts to client (and certified artifact destruction)| Custom pricing based on scope starting at $5,000.00|
+
+*Flexible arrangements available for long-term engagements and retainer relationships*
+
+---
+
+## Value-First Approach
+
+To ensure clients receive maximum value, initial engagements begin with Charles's proprietary Enterprise Assessment Framework, a comprehensive diagnostic process focused on understanding business objectives and technical environments.
+
+This systematic approach typically reduces total project costs by 30% by:
+
+- Identifying root causes rather than symptoms
+- Aligning technical solutions with business priorities
+- Establishing clear success metrics from the outset
+- Creating a prioritized roadmap for implementation
+
+---
+
+---
+
+## Technical Expertise Details
+
+### Enterprise Infrastructure & System Administration
+
+* Large-scale systems architecture and administration
+- Virtualization & storage solutions optimization
+- Advanced security architecture & network design
+
+### Web & Application Technologies
+
+* Enterprise deployment of 150+ FOSS business applications
+- Cloudron and Coolify management platforms integration
+- Load balancing & web application security hardening
+
+### Specialized Technical Services
+
+* High-performance computing & CUDA implementation
+- Advanced Claude AI implementation & enterprise prompt engineering
+- Infrastructure automation & orchestration for mission-critical systems
+
+## Take the Next Step
+
+Ready to transform your enterprise with advanced Claude AI implementation or infrastructure optimization? Here's how to get started:
+
+**Book Your 60-Minute Strategic Assessment ($75.00)**: Discuss your specific challenges and learn how The Wyble Method™ can address them.
+
+**Contact Information:**
+[Book Charles](https://supporters.reachableceo.com/assessment)
+
+*Typically responds within 24 hours with availability to begin most engagements within 2 weeks of agreement*

Joplin/CharlesNWyble-ConsultantProfile/CharlesNWyble-ConsultantProfile.sh

@@ -0,0 +1,16 @@
+#!/bin/bash
+
+set -euo pipefail
+
+if [ -f "D:/tsys/ReachableCEOPublic/MarketingMaterials/outputs/profile-consulting.reachableceo.com/CharlesNWyble-ConsultantProfile.pdf" ]; 
+then
+    rm -vf "D:/tsys/ReachableCEOPublic/MarketingMaterials/outputs/profile-consulting.reachableceo.com/CharlesNWyble-ConsultingProfile.pdf" 
+fi
+
+pandoc \
+CharlesNWyble-ConsultantProfile.md \
+--template "eisvogel" \
+--metadata-file="./CharlesNWyble-ConsultantProfile.yml" \
+--from markdown \
+--to=pdf \
+--output D:/tsys/ReachableCEOPublic/MarketingMaterials/outputs/profile-consulting.reachableceo.com/CharlesNWyble-ConsultantProfile.pdf

Joplin/CharlesNWyble-ConsultantProfile/CharlesNWyble-ConsultantProfile.yml

@@ -0,0 +1,14 @@
+title: "Charles N Wyble Consultant Profile"
+titlepage: true
+titlepage-logo: "D:/tsys/ReachableCEOPublic/MarketingMaterials/inputs/ReachableCEO-Profile-FTE/joplin/Common/ReachableCEO.png"
+toc: true
+toc-own-page: true
+date: \today
+header-left: "\\hspace{1cm}"
+header-center: "\\leftmark"
+header-right: "Page \\thepage"
+footer-left: "Charles N Wyble"
+footer-center: "Candor. Consistency. Completion."
+footer-right: "[Source code](https://git.knownelement.com/reachableceo/ReachableCEO-Profile-Consulting/src/branch/main/joplin/CharlesNWyble-ConsultantProfile)"
+urlcolor: "blue"
+page-background: "../common/background5.pdf"

Joplin/Common/background5.pdf

@@ -0,0 +1,70 @@
+%PDF-1.5
+%<25><><EFBFBD><EFBFBD>
+3 0 obj
+<< /Length 4 0 R
+   /Filter /FlateDecode
+>>
+stream
+x<EFBFBD>m<EFBFBD>;<0E>@D<>=<3D>/<2F><><EFBFBD><EFBFBD><EFBFBD>18	<14><>K삢D
+r<EFBFBD><EFBFBD><EFBFBD><EFBFBD>Ư<EFBFBD>0f<EFBFBD><EFBFBD>|%<25>߅ <20>1<EFBFBD><31><EFBFBD><EFBFBD>D<EFBFBD><44>g,7<>
+!<21>i<03>jҔ<6A>P	<09>/c<>h<06>px<70>r‰<72><C289><EFBFBD><EFBFBD>1W<31>^<5E><>Q<EFBFBD>d<>%q<>!<21><>9ZD<12>j<EFBFBD><6A>
+U<EFBFBD>Ѫ<EFBFBD><EFBFBD><EFBFBD><EFBFBD>A<EFBFBD>p<EFBFBD><EFBFBD>r$<24>&]x_<78><5F>ʑȽ<CA91>I<EFBFBD>W<><7F>?f<>r)<1F>6EU
+endstream
+endobj
+4 0 obj
+   168
+endobj
+2 0 obj
+<<
+   /ExtGState <<
+      /a0 << /CA 1 /ca 1 >>
+   >>
+>>
+endobj
+5 0 obj
+<< /Type /Page
+   /Parent 1 0 R
+   /MediaBox [ 0 0 595.275574 841.889771 ]
+   /Contents 3 0 R
+   /Group <<
+      /Type /Group
+      /S /Transparency
+      /I true
+      /CS /DeviceRGB
+   >>
+   /Resources 2 0 R
+>>
+endobj
+1 0 obj
+<< /Type /Pages
+   /Kids [ 5 0 R ]
+   /Count 1
+>>
+endobj
+6 0 obj
+<< /Creator (cairo 1.14.8 (http://cairographics.org))
+   /Producer (cairo 1.14.8 (http://cairographics.org))
+>>
+endobj
+7 0 obj
+<< /Type /Catalog
+   /Pages 1 0 R
+>>
+endobj
+xref
+0 8
+0000000000 65535 f 
+0000000582 00000 n 
+0000000282 00000 n 
+0000000015 00000 n 
+0000000260 00000 n 
+0000000354 00000 n 
+0000000647 00000 n 
+0000000774 00000 n 
+trailer
+<< /Size 8
+   /Root 7 0 R
+   /Info 6 0 R
+>>
+startxref
+826

README.md

@@ -1,23 +1,21 @@
-# MarkdownResume-Pipeline-ClientExample
+# ReachableCEO Consultant Profile
 
-Example client repository for using the [MarkdownResume-Pipeline](https://git.knownelement.com/reachableceo/MarkdownResume-Pipeline) resume building
-microservice. The microservice is vendored into this repository.
 
-## Quickstart
+## Introduction
 
-### Runtime Requirements
+This is the profile that Charles N Wyble (@ReachableCEO) uses for seeking consulting engagements for a variety of services:
 
-- Bash (this entire project was developed on msys2 on Windows 10)
-- Ensure you have pandoc installed and in your path.
+- bespoke systems engineering/SRE/devops implementations
+- Extending TeamRental/YourDreamNameHere/sol-calc and other TSYS Group offerings.
 
-### Steps
+It contains the markdown/csv files that represent his production profile referenced from his website and various third party platforms.
+
+Two core artifacts are output from those files by this process:
+
+- PDF containing an in-depth portfolio
+- Rate sheet and engagement information
+
+## Production use
+
+- [My consulting site](https://consulting.reachableceo.com)
 
-- Edit local/build/CandidateVariables.env to refelct your information.
-- Edit local/Templates/MarkdownResume/WorkHistory/WorkHistory.csv
-- Create and edit local/Templates/MarkdownResume/JobHistoryDetails/<position>.md to match the value in the first field of WorkHistory.csv
-- Repeat as necessary for your job history.
-- Edit local/Templates/MarkdownResume/SkillsAndProjects/Projects.md
-- Edit local/Template/MarkdownResume/SkillsAndProjects/Skills.csv
-- Edit local/Templates/MarkdownResume/CandidateInfoSheet.md
-- cd to the local/build directory and run bash build-demo-markdown.sh
-- Examine the PDF/MSWord output in local/build-output/*

RenderedAssets/CharlesNWyble-ConsultantInfoSheet.md

@@ -0,0 +1,117 @@
+# Charles N Wyble Consultant Information Sheet
+
+## Introduction
+
+Hello,
+
+Thank you very much for reaching out to me on this platform in regards to doing some consulting work for you !
+
+I have been receiving a high number of inquiries and have developed a standardized response letter to help ensure
+alignment and save everyone time and to reduce back and forth emails/texts/calls in the early stages.
+
+If you have any introductry questions/comments/concerns not covered by this document, please let me know and I'm happy to address them!
+
+If you ask me something answered in this reply, I will not respond to you and will not move forward with the engagement, so please read it carefully!
+
+## Re: share my ID over email
+
+I am a US Citizen (by birth). 
+
+I am happy to get on a teams/zoom/google meet etc call and show my ID.
+
+I WILL NOT share my (full or redacted) photo ID over email or any other electronic written   communication. If that is a "requirement" then I have no interest in moving forward with this engagement and no further communication is necessary.
+
+
+## Re: professional references
+
+I am happy to provide project/professional references once an engagement letter has been signed. The engagement letter has a contingency clause allowing the client to back out if the reference review doesn't meet their requirements.
+
+I will NOT provide project/professional references up front. If that is a "requirement" then I have no interest in moving forward with this engagement and no further communication is necessary.
+
+## Re: on-site work/travel/expenses/relocation
+
+if the role is not able to be performed remotely and is not based in ****  I will need to re-locate. 
+
+| Question                                  | Answer |
+|-------------------------------------------|--------|
+| Am I open to relocation?                  | Yes    |
+| Am I willing to re-locate at own expense? | No     |
+| Am I open to up to 100% travel            | Yes    |
+
+Please be aware that:
+
+- I will **only re-locate at the employer expense**.
+- I will need **two weeks of time** to re-locate.
+- The net amount of the re-location benefit **MUST be at least ** to fully compensate me for the time/effort to re-locate.
+- The full re-location benefit **must be provided prior to the confirmed start date**.
+- I **will NOT** accept a reimbursement based re-location package.
+- I am happy to come onsite (at client expense (paid up front)) for training/orientation etc.
+
+\pagebreak
+
+## Rate Schedule 
+
+
+- **** per hour(w2)
+- **** per hour (1099/corp to corp)
+
+
+### On-site/hybrid roles
+
+Travel Time: 100.00 per hour, two hour minimum
+
+- **** per hour(w2) or more
+- **** annually or more
+- **** per hour (1099/corp to corp) or more
+
+In regards to compensation type, I am open to:
+
+- w2
+- corp to corp (I have my own LLC)
+- 1099  
+
+If you have a rate for any of the compensation options above, send them all. I will pick which one works best for my situation and the opportunity.
+
+If it's a different rate with/without benefits, send both.
+
+If the above is in alignment with this opportunity, please feel free to send me an RTR with the best rate you can offer.
+
+\pagebreak
+
+## Details needed for submission
+
+### My resume
+
+[Download Candidate resume(format)](https://some.resume.somewhere/some-Resume.pdf)
+
+I am happy to discuss and make edits to the resume content specific to the opportunity if you feel they are needed.
+
+### Candidate details  
+
+Here are my complete candidate details for submission to the role.
+
+|    | Question                              | Answer                              |
+|----|---------------------------------------|-------------------------------------|
+|    | Full name                             |                    |
+|    | E-mail address                        |                    |
+|    | Phone number                          |                   |
+|    | Preferred form of contact             |  |
+|    | Work authorization                    |       |
+|    | Are you employed presently?           |        |
+|    | Current location                      |         |
+|    | Current timezone                      |         |
+|    | Timezones I can work in               |       |
+|    | Availability to interview             |   |
+|    | Availability to start                 |       |
+|    | Highest Education                     |        |
+|    | Graduated Year                        |          |
+| dd | Name of school                        |              |
+|    |                                       |                                     |
+|    | Location of school                    |          |
+|    | Linkedin Profile                      | ()             |
+|    | Github Profile                        | ()               |
+|    | Last project                          |             |
+|    | DOB                                   |                     |
+|    | Total IT/career experience            |         |
+|    | Open to in-office/hybrid/remote       | Yes                                 |
+|    | Any trips planned in next six months? | No                                  |

local/Templates/ConsultantContactInfo.md

@@ -0,0 +1,8 @@
+# Consultant Contact Information
+
+{{ConsultantName}}
+=====
+
+{{ConsultantOneLinerSummary}}
+
+[ [Github Profile]({{ConsultantGithub}}) ] .  [ [Linkedin Profile]({{ConsultantLinkedin}}) ] . [ {{ConsultantEmail}} ] . [ {{ConsultantPhone}} ] . [ {{ConsultantTImezone}} ]

local/Templates/ConsultantInfoSheet.md

@@ -0,0 +1,117 @@
+# {{ConsultantName}} Consultant Information Sheet
+
+## Introduction
+
+Hello,
+
+Thank you very much for reaching out to me on this platform in regards to doing some consulting work for you !
+
+I have been receiving a high number of inquiries and have developed a standardized response letter to help ensure
+alignment and save everyone time and to reduce back and forth emails/texts/calls in the early stages.
+
+If you have any introductry questions/comments/concerns not covered by this document, please let me know and I'm happy to address them!
+
+If you ask me something answered in this reply, I will not respond to you and will not move forward with the engagement, so please read it carefully!
+
+## Re: share my ID over email
+
+I am a US Citizen (by birth). 
+
+I am happy to get on a teams/zoom/google meet etc call and show my ID.
+
+I WILL NOT share my (full or redacted) photo ID over email or any other electronic written   communication. If that is a "requirement" then I have no interest in moving forward with this engagement and no further communication is necessary.
+
+
+## Re: professional references
+
+I am happy to provide project/professional references once an engagement letter has been signed. The engagement letter has a contingency clause allowing the client to back out if the reference review doesn't meet their requirements.
+
+I will NOT provide project/professional references up front. If that is a "requirement" then I have no interest in moving forward with this engagement and no further communication is necessary.
+
+## Re: on-site work/travel/expenses/relocation
+
+if the role is not able to be performed remotely and is not based in **{{CandidateLocation}}**  I will need to re-locate. 
+
+| Question                                  | Answer |
+|-------------------------------------------|--------|
+| Am I open to relocation?                  | Yes    |
+| Am I willing to re-locate at own expense? | No     |
+| Am I open to up to 100% travel            | Yes    |
+
+Please be aware that:
+
+- I will **only re-locate at the employer expense**.
+- I will need **two weeks of time** to re-locate.
+- The net amount of the re-location benefit **MUST be at least {{CandidateRelocationNetMinimumAmount}}** to fully compensate me for the time/effort to re-locate.
+- The full re-location benefit **must be provided prior to the confirmed start date**.
+- I **will NOT** accept a reimbursement based re-location package.
+- I am happy to come onsite (at client expense (paid up front)) for training/orientation etc.
+
+\pagebreak
+
+## Rate Schedule 
+
+
+- **{{CandidateRateSheetRemoteW2HourlyMinimum}}** per hour(w2)
+- **{{CandidateRateSheetRemote1099HourlyMinimum}}** per hour (1099/corp to corp)
+
+
+### On-site/hybrid roles
+
+Travel Time: 100.00 per hour, two hour minimum
+
+- **{{CandidateRateSheetRemoteW2HourlyPrefer}}** per hour(w2) or more
+- **{{CandidateRateSheetRemoteW2AnnualPrefer}}** annually or more
+- **{{CandidateRateSheetRemote1099HourlyPrefer}}** per hour (1099/corp to corp) or more
+
+In regards to compensation type, I am open to:
+
+- w2
+- corp to corp (I have my own LLC)
+- 1099  
+
+If you have a rate for any of the compensation options above, send them all. I will pick which one works best for my situation and the opportunity.
+
+If it's a different rate with/without benefits, send both.
+
+If the above is in alignment with this opportunity, please feel free to send me an RTR with the best rate you can offer.
+
+\pagebreak
+
+## Details needed for submission
+
+### My resume
+
+[Download Candidate resume(format)](https://some.resume.somewhere/some-Resume.pdf)
+
+I am happy to discuss and make edits to the resume content specific to the opportunity if you feel they are needed.
+
+### Candidate details  
+
+Here are my complete candidate details for submission to the role.
+
+|    | Question                              | Answer                              |
+|----|---------------------------------------|-------------------------------------|
+|    | Full name                             | {{CandidateName}}                   |
+|    | E-mail address                        | {{CandiateEmail}}                   |
+|    | Phone number                          | {{CandidatePhone}}                  |
+|    | Preferred form of contact             | {{CandidatePreferredContactMethod}} |
+|    | Work authorization                    | {{CandidateWorkAuthorization}}      |
+|    | Are you employed presently?           | {{CandidateEmploymentStatus}}       |
+|    | Current location                      | {{CandidateCurrentLocation}}        |
+|    | Current timezone                      | {{CandidateCurrentTimezone}}        |
+|    | Timezones I can work in               | {{CandidateWorkableTimezones}}      |
+|    | Availability to interview             | {{CandidateInterviewAvailability}}  |
+|    | Availability to start                 | {{CandidateStartAvailability}}      |
+|    | Highest Education                     | {{CandidateHighestEducation}}       |
+|    | Graduated Year                        | {{CandidateGraduationYear}}         |
+| dd | Name of school                        | {{CandidateSchoolName}}             |
+|    |                                       |                                     |
+|    | Location of school                    | {{CandidateSchoolLocation}}         |
+|    | Linkedin Profile                      | ({{CandidateLinkedin}})             |
+|    | Github Profile                        | ({{CandidateGithub}})               |
+|    | Last project                          | {{CandidateLastProject}}            |
+|    | DOB                                   | {{CandidateDOB}}                    |
+|    | Total IT/career experience            | {{CandidateTotalExperience}}        |
+|    | Open to in-office/hybrid/remote       | Yes                                 |
+|    | Any trips planned in next six months? | No                                  |

local/Templates/ConsultantProfile.md

@@ -0,0 +1,24 @@
+# Consultant Profile
+
+## Introduction
+
+### Professional History
+
+- See my resume
+
+## Rate Information
+
+### Per Hour
+
+These are the rates that I charge per hour.
+
+- Standard Rack Rate :
+- Bespoke Rate :
+
+### Flat Rate
+
+I offer some flat rate work.
+
+- YDN/TeamRental Build Out: $500.00
+
+## Types of hourly work offered

local/Templates/JSONResume/awards.csv

@@ -1,3 +0,0 @@
-# CSV File: awards.csv
-# Columns: title,awarder,date,summary
-Defender of the Internet,Fight For The Future,2014-10-02,"For my work against mass surveillance and building out civic tools for digital democracy."

local/Templates/JSONResume/certificates.csv

@@ -1,3 +0,0 @@
-# CSV File: certificates.csv
-# Columns: name,date,issuer,url
-Certified Kubernetes Administrator,2021-05-01,Cloud Native Computing Foundation,http://certificates.com/kubernetes

local/Templates/JSONResume/education.csv

@@ -1,3 +0,0 @@
-institution,url,area,studyType,startDate,endDate,score,courses
-"The University of Queensland",,"Software Engineering (incomplete)","Bachelors","2008-02-12","2009-12-12",,
-"University of Technology","http://universityoftechnology.com","Computer Science","Bachelor","2010-09-01","2014-06-30","3.8 GPA","CS101 - Introduction to Computer Science; CS201 - Data Structures and Algorithms; CS301 - Operating Systems"

local/Templates/JSONResume/interests.csv

@@ -1,6 +0,0 @@
-# CSV File: interests.csv
-# Columns: name,keywords
-Gardening,"Lazy Gardening"
-Music,"Guitar;Singing;Dancing"
-Books,"Reading;Writing;History"
-Open Source,"All of it"

local/Templates/JSONResume/languages.csv

@@ -1,3 +0,0 @@
-# CSV File: languages.csv
-# Columns: language,fluency
-English,Native speaker

local/Templates/JSONResume/profiles.csv

@@ -1,5 +0,0 @@
-# CSV File: profiles.csv
-# Columns: username,url,network
-ajaxdavis,https://twitter.com/ajaxdavis,twitter
-thomasdavis,https://github.com/thomasdavis,github
-

local/Templates/JSONResume/publications.csv

@@ -1,3 +0,0 @@
-# CSV File: publications.csv
-# Columns: name,publisher,releaseDate,url,summary
-Advanced JavaScript Techniques,Tech Books Publishing,2019-08-01,http://techbookspublishing.com/advanced-javascript,"A comprehensive guide to modern JavaScript development."

local/Templates/JSONResume/references.csv

@@ -1,6 +0,0 @@
-# CSV File: references.csv
-# Columns: reference,name
-"Thomas was hired as a lead developer and, upon the leaving of our co-founder took over as CTO of Earbits. Thomas is, hands down, one of those A Players you hear of companies dying to hire. He is incredibly smart, not just at code but about everything from classical music to Chinese language and culture. Thomas is great to work with and, as a well established contributor to open source projects and several successful ventures, commands the respect of engineers at all levels. I would suggest doing anything you can to have him on your team.","Joey Flores, Co-founder and CEO of Earbits, Inc."
-"I've had the great pleasure of working with Thomas for the past three years at Earbits, and on a few side projects. Two years ago our CTO left on a moment's notice, Thomas saved our company by quickly stepping up to fill this role. He has been with our company through thick and thin and made serious personal sacrifices in order to help the company during tough times. He is a phenomenal hacker and a true team player. Highly recommended!","Yotam Rosenbaum, SVP of Operations, Earbits, Inc."
-"Thomas is an extremely talented engineer with a very broad range of skills and experience. From being a thought leader in the front-end community via backbonetutorials.com and cdnjs.com, to designing and implementing the API for cdnjs.com, working with Thomas has been fantastic learning experience. Thomas is truly a full stack develop, and his work output is incredible. If there is any opportunity to work with Thomas, I take it. He is the definition of an A player.","Ryan Kirkman, Senior Software Engineer at Nerdwallet"
-"On Thomas Davis... Hire this guy. Do not be fooled. Incredibly capable and fast. Plays well with others. Unbelievable at front-end work end programming but that is just the start. Visionary. Hire him before I do.","Greg Davis"

local/Templates/JSONResume/skills.csv

@@ -1,5 +0,0 @@
-# CSV File: skills.csv
-# Columns: name,level,keywords
-Frontend,Senior,"HTML / JSX;SCSS / CSS / BEM / Styled Components;Javascript / Typescript;React / Next;Redux / Apollo"
-Backend,Senior,"Node;Ruby;Python;Postgres;Redis;Serverless"
-Devops,Senior,"AWS;G Cloud;Heroku;Caching"

local/Templates/JSONResume/volunteer.csv

@@ -1,5 +0,0 @@
-# CSV File: volunteer.csv
-# Columns: organization,position,url,startDate,summary,highlights
-Open Source Project,Contributor,http://opensourceproject.com,2016-01-01,"Contributing to open source projects to improve software quality.","Fixed critical bugs and added new features.;Mentored new contributors."
-
-add_vo

local/Templates/JSONResume/work.csv

@@ -1,13 +0,0 @@
-# CSV File: work.csv
-# Columns: name,position,location,website,startDate,endDate,summary,highlights
-Misc Companies,Product Engineer,Melbourne,https://lordajax.com/,2020-05-05,,"Over the past several years, I've worked at various roles and companies. Mostly early stage startups, doing full stack product development.","React / Next;Node / Laravel;LLM's;Diagrams / Canvas"
-Tokenized,Senior Javascript Developer,Melbourne,https://tokenized.com/,2020-05-05,2021-05-05,"Tokenized is a Bitcoin wallet for issuing, managing and trading digital tokens. I built out the front end which was packaged as an electron app. It was a difficult frontend to build because we store the users keys locally and used them to sign transactions and contracts.","React;Redux;SCSS;Product"
-Blockbid,Senior Javascript Developer,Melbourne,https://platform.blockbid.io,2018-03-01,2020-01-01,"Blockbid is an Australian crypto currency exchange. I started off on the frontend but eventually became lead tech and worked on every moving piece of the exchange. I really enjoyed working with liquidity providers and connecting their platforms to help us achieve liquid markets.","React, Apollo, Styled Components;Node.js / Rails;Docker / Heroku / GCP;Used Figma for design and UX work;Optimizing markets with tens of millions of rows using SQL."
-Listium,Developer,,https://listium.com,2016-01-01,2018-01-01,"Built a very large and complex React / Redux application. It works on all platforms and has IOS/Android builds due to it being a PWA. (wrapped it in React Native though only implementing a WebView)","Worked with Postgres, Redis and Dynamodb for storage.;Hosted on a mixture of Heroku Apps and EC2 servers.;Caching by Fastly and Cloudflare;Hybrid app supported on all platforms"
-Electronic Frontier Foundation,Developer,,http://www.eff.org,2014-04-01,2016-01-01,"Hired to take EFF's campaigning to the next level by building an action centre in Ruby on Rails. The action centre is built around some large open source tools that lower the barrier to entry when contacting congress.","Developed new tools for contacting congress;Brainstormed campaign ideas to raise maximum awareness about issues;Lots of social networking integration"
-Earbits,CTO,,http://www.earbits.com,2013-03-08,2015-01-09,"Started off as a front end developer but took on the role of CTO in early 2013. The application frontend is built with Javascript and organized as a single page application that talks to a collection of Rails web servers which are connected to MongoDB.","Managed a small team of developers and designers;Built the entire frontend application with Backbone.js;Transferred all of the infrastructure from Heroku to AWS"
-JSON Resume,Founder,,http://jsonresume.org,2014-04-01,,"JSON Resume is a community driven open source initiative to create a JSON based standard for resumes. There is no reason why there can't be a common standard for writing a resume that can be extended with an ecosystem of open source tools.","This resume is built with JSON Resume;Over 3000 stars on Github;Community developed themes;Tens of thousands of users"
-Taskforce.is,Developer,,http://www.taskforce.is,2013-06-01,2016-01-01,"Worked on many politically charged campaigns against mass surveillance. Not only technically challenging work but also a lot of networking and getting my hands dirty with politics.    Our biggest project was \"TheDayWeFightBack\"..","Generated  37,000,000 banner views;100, 000 phone calls to congress;500, 000 emails;250, 000 signatures"
-Drone Hire,Co-Founder,,http://www.dronehire.org,2013-01-01,,"An international directory of civilian drone / UAV operators for hire. Services include aerial photography, aerial video, mapping, surveying, precision agriculture, real estate photography, remote inspections and infrared imaging. Our plan is to be the place to go when looking for UAV/Drone services. The website is built in Backbone.js and API is built with Node.js and Postgres.","The site and blog combined have managed to receive over 200,000 visitors in 2014."
-BackboneTutorials.com,Founder,,http://backbonetutorials.com,2011-01-01,2014-01-01,"I write tutorials and blog post regarding the popular Javascript framework Backbone.js. The tutorials cover a range of topics regarding front end development aimed at beginners, experts and anyone in between.","Over two million unique visitors a year;25,000+ ebook downloads;300,000+ Youtube views"
-Ephox,Front-end Developer,,http://ephox.com,2011-01-01,2012-06-01,"Ephox is a worldwide company who is heavily involved with the development of TinyMce and enterprise editors. My primary role included building front-end widgets and applications. Worked on a major product using Backbone.js as a base. Heavily involved in UI/UX design and wire-framing. Also spend a lot of time designing API specifications and documentation.",

local/Templates/MarkdownResume/CandidateInfoSheet/CandidateInfoSheet.md

@@ -1,121 +0,0 @@
-# {{CandidateName}} Candidate Information Sheet
-
-## Introduction
-
-Hello,
-
-I apologize for the form letter response.
-
-I receive a high volume of recruiter emails every day and I've found this letter to be the most efficient way to
-handle the high volume of emails and reduce back and forth emails/texts/calls.
-
-If you have any questions/comments/concerns not covered by this document, please let me know via e-mail and I'm happy to address them!
-
-If you ask me something answered in this document, I will not respond and will not move forward with the opportunity, so please read it in detail!
-
-## Re: share my ID over email
-
-I WILL NOT share my (full or redacted) photo ID over email or any other electronic written  
-communication. If that is "required" then I have no interest in moving forward with this opportunity.
-
-I am happy to get on a teams/zoom/google meet etc call and show my ID.
-
-## Re: professional references
-
-I am happy to provide professional references once an interview with the end client/customer/hiring manager/team has been scheduled. I will NOT provide references up front. If that is "required" then I have no interest in moving forward with this opportunity.
-
-## Re: relocation
-
-if the role is not based in **{{CandidateLocation}}** or **Other Location** I will need to re-locate
-
-| Question                                  | Answer |
-|-------------------------------------------|--------|
-| Am I open to relocation?                  | Yes    |
-| Am I willing to re-locate at own expense? | No     |
-| Am I open to up to 100% travel            | Yes    |
-
-Please be aware that:
-
-- I will **only re-locate at the employer expense**.
-- I will need **two weeks of time** to re-locate.
-- The net amount of the re-location benefit **MUST be at least {{CandidateRelocationNetMinimumAmount}}** to fully compensate me for the time/effort to re-locate.
-- The full re-location benefit **must be provided prior to the confirmed start date**.
-- I **will NOT** accept a reimbursement based re-location package.
-- I am happy to come onsite (at client expense (paid up front)) for training/orientation etc.
-
-\pagebreak
-
-## Rate Schedule (compensation expectations)
-
-### Fully remote roles
-
-I have a **very strong** preference for fully remote roles.
-
-I am open to (at the absolute bottom of my range):
-
-- **{{CandidateRateSheetRemoteW2HourlyMinimum}}** per hour(w2)
-- **{{CandidateRateSheetRemoteW2AnnualMinimum}}** annually
-- **{{CandidateRateSheetRemote1099HourlyMinimum}}** per hour (1099/corp to corp)
-
-I have a strong preference for roles that are :
-
-- **{{CandidateRateSheetRemoteW2HourlyPrefer}}** per hour(w2) or more
-- **{{CandidateRateSheetRemoteW2AnnualPrefer}}** annually or more
-- **{{CandidateRateSheetRemote1099HourlyPrefer}}** per hour (1099/corp to corp) or more
-
-### On-site/hybrid roles
-
-- **{{CandidateRateSheetRemoteW2HourlyPrefer}}** per hour(w2) or more
-- **{{CandidateRateSheetRemoteW2AnnualPrefer}}** annually or more
-- **{{CandidateRateSheetRemote1099HourlyPrefer}}** per hour (1099/corp to corp) or more
-
-In regards to compensation type, I am open to:
-
-- w2
-- corp to corp (I have my own LLC)
-- 1099  
-
-If you have a rate for any of the compensation options above, send them all. I will pick which one works best for my situation and the opportunity.
-
-If it's a different rate with/without benefits, send both.
-
-If the above is in alignment with this opportunity, please feel free to send me an RTR with the best rate you can offer.
-
-\pagebreak
-
-## Details needed for submission
-
-### My resume
-
-[Download Candidate resume(format)](https://some.resume.somewhere/some-Resume.pdf)
-
-I am happy to discuss and make edits to the resume content specific to the opportunity if you feel they are needed.
-
-### Candidate details  
-
-Here are my complete candidate details for submission to the role.
-
-| Question                              | Answer                              |
-|---------------------------------------|-------------------------------------|
-| Full name                             | {{CandidateName}}                   |
-| E-mail address                        | {{CandiateEmail}}                   |
-| Phone number                          | {{CandidatePhone}}                  |
-| Preferred form of contact             | {{CandidatePreferredContactMethod}} |
-| Work authorization                    | {{CandidateWorkAuthorization}}      |
-| Are you employed presently?           | {{CandidateEmploymentStatus}}       |
-| Current location                      | {{CandidateCurrentLocation}}        |
-| Current timezone                      | {{CandidateCurrentTimezone}}        |
-| Timezones I can work in               | {{CandidateWorkableTimezones}}      |
-| Availability to interview             | {{CandidateInterviewAvailability}}  |
-| Availability to start                 | {{CandidateStartAvailability}}      |
-| Highest Education                     | {{CandidateHighestEducation}}       |
-| Graduated Year                        | {{CandidateGraduationYear}}         |
-| Name of school                        | {{CandidateSchoolName}}             |
-| Location of school                    | {{CandidateSchoolLocation}}         |
-| Linkedin Profile                      | ({{CandidateLinkedin}})             |
-| Github Profile                        | ({{CandidateGithub}})               |
-| Last project                          | {{CandidateLastProject}}            |
-| DOB                                   | {{CandidateDOB}}                    |
-| Total IT/career experience            | {{CandidateTotalExperience}}        |
-| Open to in-office/hybrid/remote       | Yes                                 |
-| Any trips planned in next six months? | No                                  |

local/Templates/MarkdownResume/ContactInfo/ContactInfo-ClientSubmit.md

@@ -1,4 +0,0 @@
-{{CandidateName}}
-=====
-
-{{CandidateOneLinerSummary}}

local/Templates/MarkdownResume/ContactInfo/ContactInfo-JobBoard.md

@@ -1,6 +0,0 @@
-{{CandidateName}}
-=====
-
-{{CandidateOneLinerSummary}}
-
-[ [Github Profile]({{CandidateGithub}}) ] .  [ [Linkedin Profile]({{CandidateLinkedin}}) ] . [ {{CandidateEmail}} ] . [ {{CandidatePhone}} ] . [ {{CandidateLocation}} ]

local/Templates/MarkdownResume/JobHistoryDetails/job1.md

@@ -1,3 +0,0 @@
-- Stuff
-- Things
-- Amazing project!

local/Templates/MarkdownResume/JobHistoryDetails/job2.md

@@ -1,3 +0,0 @@
-- Stuff
-- Things
-- Amazing project!

local/Templates/MarkdownResume/SkillsAndProjects/Projects.md

@@ -1,2 +0,0 @@
-- Cool project 1.
-- cool project 2.

local/Templates/MarkdownResume/SkillsAndProjects/Skills.csv

@@ -1,2 +0,0 @@
-skill1|1 years|skill,1,details,and,stuff
-skill2|2 years|skill2,2,details,and,stuff,and,things

local/Templates/MarkdownResume/WorkHistory/WorkHistory.csv

@@ -1,2 +0,0 @@
-job1,Title of job 1,January 1 1970 - January 6 1980
-job2,Title of Job 2,January 1 1970 - January 6 1980

local/Templates/SkillsAndProjects/Skills.csv

@@ -0,0 +1,7 @@
+LLM|2 years|Whispher,OpenWebUI,QA/validation,RAG,data cleaning/prep
+Programming|5 years|J2ME,PHP,Ruby,TCL/TK,Java,C,C++
+Embedded development|5 years|Raspberry pi,arduino,seeduino,Lego Mindstorms
+Free/Libre/Open Source software|25 years|Apache,Postfix,Qmail,Dovecot,Courier IMAP,Nginx,Matamo,Discourse,Wordpress, Mautic,Dolibarr,Revive Ad Server,Firefly,Cloudron,Coolify,Gitea,  HomeAssistant,  Jenkins,Rundeck,N8N,  LetsEncrypt,ACME,cfssl
+SRE|5 years| Grafana,Prometheus,Signoz,Wazuh
+Databases|25 years| MySQL,PostgreSQL,  Dbeaver,PHPMyAdmin,PostGIS
+Configuration management/Infrastructure As Code (IAC)|25 years|CfEngine,FetchApply,Terraform/OpenTOfU,Ansible,AWX,Hashicorp Packer/Vault

local/build-output/JSONResume/job-board/ignore-this-dir

@@ -1 +0,0 @@
-ignore

local/build-output/MarkdownResume/client-submit/ignore-this-dir

@@ -1 +0,0 @@
-ignore

local/build-output/MarkdownResume/job-board/ignore-this-dir

@@ -1 +0,0 @@
-ignore

local/build-output/MarkdownResume/recruiter/ignore-this-dir

@@ -1 +0,0 @@
-ignore

local/build-temp/MarkdownResume/ignore-this-dir

@@ -1 +0,0 @@
-ignore

local/build/BuildTemplate-ClientSubmission.yml

@@ -1,7 +0,0 @@
-title: "{{CandidateName}} Resume"
-header-left: "\\hspace{1cm}"
-header-center: "\\leftmark"
-header-right: "Page \\thepage"
-footer-left: "{{CandidateName}}"
-urlcolor: {{URLCOLOR}}
-page-background: "{{PAGEBACKGROUND}}"

local/build/BuildTemplate-ConsultantInfoSheet.yml

@@ -0,0 +1,14 @@
+title: "{{ConsultantName}} Consultant Information Sheet"
+titlepage: true
+titlepage-logo: "{{ConsultantLogo}}"
+toc: true
+toc-own-page: true
+date: \today
+header-left: "\\hspace{1cm}"
+header-center: "\\leftmark"
+header-right: "Page \\thepage"
+footer-left: "{{ConsultantName}}"
+footer-center: "{{ConsultantTagline}}"
+footer-right: "[Source code]({{SourceCode}})"
+urlcolor: {{URLCOLOR}}
+page-background: "{{PAGEBACKGROUND}}"

local/build/BuildTemplate-ConsultantProfile.yml

@@ -1,14 +1,14 @@
-title: "{{CandidateName}} Candidate Information Sheet"
+title: "{{ConsultantName}} Consultant Profile"
 titlepage: true
-titlepage-logo: "{{CandidateLogo}}"
+titlepage-logo: "{{ConsultantLogo}}"
 toc: true
 toc-own-page: true
 date: \today
 header-left: "\\hspace{1cm}"
 header-center: "\\leftmark"
 header-right: "Page \\thepage"
-footer-left: "{{CandidateName}}"
-footer-center: "{{CandidateTagline}}"
+footer-left: "{{ConsultantName}}"
+footer-center: "{{ConsultantTagline}}"
 footer-right: "[Source code]({{SourceCode}})"
 urlcolor: {{URLCOLOR}}
 page-background: "{{PAGEBACKGROUND}}"

local/build/BuildTemplate-JobBoard.yml

@@ -1,12 +0,0 @@
-title: "{{CandidateName}} Resume"
-titlepage: true
-titlepage-logo: "{{CandidateLogo}}"
-date: \today
-header-left: "\\hspace{1cm}"
-header-center: "\\leftmark"
-header-right: "Page \\thepage"
-footer-left: "{{CandidateName}}"
-footer-center: "{{CandidateTagline}}"
-footer-right: "[Source code]({{SourceCode}})"
-urlcolor: {{URLCOLOR}}
-page-background: "{{PAGEBACKGROUND}}"

local/build/CandidateVariables.env

@@ -1,102 +0,0 @@
-###################################################
-# Modify these values to suit
-###################################################
-
-#############################################################################
-#SET THIS NEXT VARIABLE OR NOTHING WILL WORK!!!!
-
-export PipelineClientWorkingDir="D:/tsys/@ReachableCEO/MarkdownResume-Pipeline-ClientExample/local"
-
-#SET THE PREVIOUS VARIABLE OR NOTHING WILL WORK!!!!
-#############################################################################
-
-########################
-# Contact info
-########################
-
-export CandidateName="First Middle Last"
-export CandidatePhone="1 123 456 7890"
-export CandidateRole="Jack of all trades"
-export CandidateLocation="Place 1/Place 2"
-export CandidateCity="City"
-export CandidateCountry="Country"
-export CandidateZipCode="Zip"
-export CandidateSkypeID="SkypeID"
-export CandidateEmail="candidate@domain.com"
-export CandidateAvatar="URLTOAVATAR"
-export CandidateWebsite="URLTOCANDIDATEWEbSITE"
-
-########################
-# Profile information
-########################
-
-export CandidateTagline="Your.Tagline.Here."
-export CandidateOneLineSummary="Super awesome and stuff."
-export CandidateLinkedin="https://www.linkedin.com/in/ab1"
-export CandidateGithubUsername="ghuser"
-export CandidateTwitterUsername="twxuser"
-
-##########################################
-# Layout/title page /formatting options
-##########################################
-
-export CandidateLogo=""
-export SourceCode="https://git.knownelement.com/reachableceo/MarkdownResume-Pipeline"
-export URLCOLOR="blue"
-export PAGEBACKGROUND="./background3.pdf"
-export JSONRESUME_THEME="professional"
-export PANDOC_TEMPLATE="eisvogel"
-
-###########################
-# Yaml files used by pandoc
-###########################
-
-export YamlInputTemplateFileCandidateInfoSheet="$PipelineClientWorkingDir/build/BuildTemplate-CandidateInfoSheet.yml"
-export YamlInputTemplateFileJobBoard="$PipelineClientWorkingDir/build/BuildTemplate-JobBoard.yml"
-export YamlInputTemplateFileClientSubmission="$PipelineClientWorkingDir/build/BuildTemplate-ClientSubmission.yml"
-export WordOutputReferenceDoc="$PipelineClientWorkingDir/build/resume-docx-reference.docx"
-
-##########################
-# Candidate info sheet
-##########################
-
-export CandidatePreferredContactMethod="Email will get the fastest response."
-export CandidateWorkAuthorization="US Citizen"
-export CandidateEmploymentStatus="Not currently employed"
-export CandidateCurrentLocation="City,State,Country etc"
-export CandidateCurrentTimezone="Timezone"
-export CandidateWorkableTimezones="Timezones"
-export CandidateInterviewAvailability="Sometime"
-export CandidateStartAvailability="Sometime"
-export CandidateHighestEducation="Some education level"
-export CandidateGraduationYear="Graduation year"
-export CandidateSchoolName="School name"
-export CandidateSchoolLocation="School location"
-export CandidateLastProject="Last project"
-export CandidateDOB="MM/DD"
-export CandidateTotalExperience="epoch"
-
-
-########################
-#Compensation targets
-########################
-
-export CandidateRelocationNetMinimumAmount="1,987.11"
-
-export CandidateRateSheetRemoteW2HourlyMinimum="\$12.34"
-export CandidateRateSheetRemoteW2AnnualMinimum="\$123,456.00"
-export CandidateRateSheetRemote1099HourlyMinimum="\$56.78"
-
-export CandidateRateSheetRemoteW2HourlyPrefer="\$34.56"
-export CandidateRateSheetRemoteW2AnnualPrefer="\$321,987.00"
-export CandidateRateSheetRemote1099HourlyPrefer="\$78.90"
-
-# Other resume data
-# Awards
-# Interests
-# College/University education
-# Certifactes
-
-# Please see:
-# the CSV files in ../Templates/JSONResume 
-# the CSV files in ../Templates/MarkdownResume

local/build/ConsultantVariables.env

@@ -0,0 +1,74 @@
+#############################################################################
+#SET THESE TWO VARIABLE CORRECTLY OR NOTHING WILL WORK
+export PipelineClientWorkingDir="/home/localuser/ReachableCEO/ReachableCEO-OutreachMaterial/ReachableCEO-Profile-Consulting/local/"
+export BUILD_OUTPUT_DIR="/home/localuser/ReachableCEO/ReachableCEO-OutreachMaterial/ReachableCEO-Profile-Consulting/RenderedAssets/"
+#SET THESE TWO VARIABLE CORRECTLY OR NOTHING WILL WORK
+#############################################################################
+
+###################################################
+# Modify these values to suit
+###################################################
+
+########################
+# Contact info
+########################
+
+export ConsultantName="Charles N Wyble"
+export ConsultantPhone="1 818 280 7059"
+export ConsultantEmail="reachableceo@reachableceo.com"
+
+########################
+# Profile information
+########################
+
+export ConsultantOneLineSummary="Senior (**Staff level**) **System Engineer/SRE/Architect** with extensive Linux/Windows/Networking/Cyber security background and experience 
+"
+export ConsultantLinkedin="https://www.linkedin.com/in/charles-wyble-412007337"
+export ConsultantGithub="https://git.knownelement.com/reachableceo"
+export ConsultantTagline="Candor. Consistency. Completion."
+
+########################
+# Formatting options
+########################
+
+export ConsultantLogo="~/localuser/ReachableCEO/ReachableCEOOutreachMaterial/ReachableCEO.png"
+export SourceCode="https://git.knownelement.com/reachableceo/ReachableCEO-Profile-Consulting"
+export URLCOLOR="blue"
+export PAGEBACKGROUND="$PipelineClientWorkingDir/build/background3.pdf"
+export PANDOC_TEMPLATE="$PipelineClientWorkingDir/build/eisvogel.tex"
+
+###########################
+# Yaml files used by pandoc
+###########################
+
+export YamlInputTemplateFileConsultantInfoSheet="$PipelineClientWorkingDir/build/BuildTemplate-ConsultantInfoSheet.yml"
+export YamlInputTemplateFileConsultantProfile="$PipelineClientWorkingDir/build/BuildTemplate-ConsultantProfile.yml"
+
+##########################
+# Consultant info sheet
+##########################
+
+export ConsultantPreferredContactMethod="Email will get the fastest response."
+export ConsultantCurrentTimezone="CST"
+export ConsultantWorkableTimezones="PST/CST/EST"
+export ConsultantTotalExperience="22 years"
+
+########################
+#Compensation targets
+########################
+
+export ConsultantHourlyRateStandard="145.00"
+export ConsultantHourlyRateBespoke="245.00"
+
+###############################
+# Output location/filenames
+###############################
+
+export PROFILE_FILE_NAME="$(echo $ConsultantName|sed 's/ //g')"
+
+
+export ConsultantInfoSheetMarkdownOutputFile="$BUILD_OUTPUT_DIR/$PROFILE_FILE_NAME-ConsultantInfoSheet.md"
+export ConsultantInfoSheetPDFOutputFile="$BUILD_OUTPUT_DIR/$PROFILE_FILE_NAME-ConsultantInfoSheet.pdf"
+
+export ConsultantProfileMarkdownOutputFile="$BUILD_OUTPUT_DIR/$PROFILE_FILE_NAME-ConsultantProfile.md"
+export ConsultantProfilePDFOutputFile="$BUILD_OUTPUT_DIR/$PROFILE_FILE_NAME-ConsultantProfile.pdf"

local/build/build-consulting-profile.sh

@@ -0,0 +1,59 @@
+#!/bin/bash
+
+# Exit on error
+set -e
+
+# A client script to setup variables for and execute the consultant profile pipeline
+# Executes: ../../vendor/git.knownelement.com/reachableceo/ConsultantProfile-Pipeline-Server/build/build-pipeline-server-markdown.sh
+
+# Check if ConsultantVariables.env exists
+if [ ! -f "./ConsultantVariables.env" ]; then
+	echo "Error: ConsultantVariables.env not found"
+	exit 1
+fi
+
+# Source the environment file with error handling
+if ! source ./ConsultantVariables.env; then
+	echo "Error: Failed to source ConsultantVariables.env. Please check the file for syntax errors."
+	exit 1
+fi
+
+# Verify required environment variables
+required_vars=("PipelineClientWorkingDir" "BUILD_OUTPUT_DIR")
+for var in "${required_vars[@]}"; do
+	if [ -z "${!var}" ]; then
+		echo "Error: Required environment variable $var is not set"
+		exit 1
+	fi
+done
+
+####################################################
+#DO NOT CHANGE ANYTHING BELOW THIS LINE
+####################################################
+
+##################################################################
+# Setup globals for use by the build-pipeline-server.sh script
+##################################################################
+
+export MO_PATH="bash ../../vendor/git.knownelement.com/ExternalVendorCode/mo/mo"
+export BUILD_TEMP_DIR="$PipelineClientWorkingDir/build-temp/ConsultantProfile"
+export BUILDYAML_CONSULTANT_INFOSHEET="$BUILD_TEMP_DIR/ConsultantInfoSheet.yml"
+export BUILDYAML_CONSULTANT_PROFILE="$BUILD_TEMP_DIR/ConsultantProfile.yml"
+
+# Create necessary directories if they don't exist
+mkdir -p "$BUILD_TEMP_DIR"
+mkdir -p "$BUILD_OUTPUT_DIR"
+
+# Cleanup previous intermediate and final output artifacts
+rm -vf "$BUILD_TEMP_DIR"/*.yml
+rm -vf "$BUILD_OUTPUT_DIR"/*
+
+# Verify pipeline server script exists
+PIPELINE_SERVER="../../vendor/git.knownelement.com/reachableceo/ConsultantProfile-Pipeline-Server/build/build-pipeline-server-markdown.sh"
+if [ ! -f "$PIPELINE_SERVER" ]; then
+	echo "Error: Pipeline server script not found at: $PIPELINE_SERVER"
+	exit 1
+fi
+
+# Call the build-pipeline-server in the vendored repository to produce updated output artifacts
+bash "$PIPELINE_SERVER"

local/build/build-demo-json.sh

@@ -1,37 +0,0 @@
-#!/usr/bin/env bash
-
-
-# This is a demo script for the MarkdownResumePipeline server
-# This script creates PDF/MSWord output from markdown/csv input
-
-
-############################################
-#Edit this file to reflect your information
-############################################
-
-source "./CandidateVariables.env"
-
-####################################################
-####################################################
-####################################################
-#DO NOT CHANGE ANYTHING BELOW THIS LINE
-####################################################
-####################################################
-####################################################
-
-######################################################################################
-# Setup key variables that will be used by the build-pipeline-server-markdown.sh script
-######################################################################################
-
-export BUILD_OUTPUT_DIR="$PipelineClientWorkingDir/build-output/JSONResume"
-export JSON_TEMPLATE_DIRECTORY="$PipelineClientWorkingDir/Templates/JSONResume"
-
-export JobBoardJSONOutputFile="$BUILD_OUTPUT_DIR/job-board/Candidate-Resume.json"
-export ClientSubmissionJSONOutputFile="$BUILD_OUTPUT_DIR/client-submit/Candidate-Resume.json"
-
-echo "Cleaning up from previous runs..."
-
-rm $JobBoardJSONOutputFile
-rm $ClientSubmissionJSONOutputFile
-
-bash ../../vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/build/build-pipeline-server-json.sh  

vendor/git.knownelement.com/ExternalVendorCode/mo/.eslintrc.yaml

@@ -0,0 +1,168 @@
+parserOptions:
+    ecmaVersion: latest
+    sourceType: module
+env:
+    es6: true
+    jasmine: true
+    node: true
+extends: eslint:recommended
+rules:
+    accessor-pairs: error
+    array-bracket-spacing:
+        - error
+        - never
+    array-callback-return: error
+    block-spacing:
+        - error
+        - never
+    brace-style: error
+    comma-dangle: error
+    comma-spacing: error
+    comma-style: error
+    complexity:
+        - error
+        - 10
+    computed-property-spacing: error
+    consistent-return: error
+    consistent-this: error
+    constructor-super: error
+    curly: error
+    default-case: error
+    dot-notation: error
+    eol-last: error
+    eqeqeq: error
+    generator-star-spacing: error
+    global-require: off
+    guard-for-in: error
+    jsx-quotes: error
+    key-spacing: error
+    keyword-spacing: error
+    linebreak-style: error
+    lines-around-comment:
+        - error
+        -
+            allowBlockStart: true
+            allowObjectStart: true
+            allowArrayStart: true
+    max-statements-per-line: error
+    new-cap: error
+    new-parens: error
+    no-array-constructor: error
+    no-bitwise: error
+    no-caller: error
+    no-case-declarations: error
+    no-catch-shadow: error
+    no-class-assign: error
+    no-cond-assign: error
+    no-confusing-arrow: error
+    no-console: off
+    no-const-assign: error
+    no-constant-condition: error
+    no-continue: error
+    no-delete-var: error
+    no-dupe-args: error
+    no-dupe-class-members: error
+    no-dupe-keys: error
+    no-duplicate-case: error
+    no-duplicate-imports: error
+    no-empty: off
+    no-empty-character-class: error
+    no-empty-pattern: error
+    no-eq-null: error
+    no-eval: error
+    no-extend-native: error
+    no-extra-bind: error
+    no-extra-boolean-cast: error
+    no-extra-label: error
+    no-extra-semi: error
+    no-fallthrough: error
+    no-func-assign: error
+    no-implied-eval: error
+    no-inner-declarations: error
+    no-invalid-this: error
+    no-invalid-regexp: error
+    no-irregular-whitespace: error
+    no-iterator: error
+    no-label-var: error
+    no-labels: error
+    no-lone-blocks: error
+    no-lonely-if: error
+    no-loop-func: error
+    no-mixed-spaces-and-tabs: error
+    no-multi-spaces: error
+    no-multi-str: error
+    no-multiple-empty-lines:
+        - error
+        -
+            max: 2
+    no-native-reassign: error
+    no-negated-condition: error
+    no-nested-ternary: error
+    no-new: error
+    no-new-func: error
+    no-new-object: error
+    no-new-symbol: error
+    no-new-wrappers: error
+    no-obj-calls: error
+    no-octal: error
+    no-octal-escape: error
+    no-path-concat: error
+    no-plusplus: error
+    no-proto: error
+    no-redeclare: error
+    no-regex-spaces: error
+    no-restricted-globals: error
+    no-return-assign: error
+    no-script-url: error
+    no-self-assign: error
+    no-self-compare: error
+    no-sequences: error
+    no-shadow: error
+    no-shadow-restricted-names: error
+    no-spaced-func: error
+    no-sparse-arrays: error
+    no-this-before-super: error
+    no-throw-literal: error
+    no-trailing-spaces: error
+    no-undef: error
+    no-undef-init: error
+    no-unexpected-multiline: error
+    no-unmodified-loop-condition: error
+    no-unneeded-ternary: error
+    no-unreachable: error
+    no-unsafe-finally: error
+    no-unused-expressions: error
+    no-unused-labels: error
+    no-unused-vars: error
+    no-useless-call: error
+    no-useless-computed-key: error
+    no-useless-concat: error
+    no-useless-constructor: error
+    no-useless-escape: error
+    no-void: error
+    no-warning-comments: warn
+    no-whitespace-before-property: error
+    no-with: error
+    operator-assignment: error
+    padded-blocks:
+        - error
+        - never
+    prefer-const: error
+    quote-props:
+        - error
+        - as-needed
+    radix: error
+    require-yield: error
+    semi: error
+    semi-spacing: error
+    space-before-blocks: error
+    space-in-parens: error
+    space-infix-ops:
+        - error
+        -
+            int32Hint: false
+    space-unary-ops: error
+    spaced-comment: error
+    use-isnan: error
+    valid-typeof: error
+    yield-star-spacing: error

vendor/git.knownelement.com/ExternalVendorCode/mo/.github/workflows/ci.yaml

@@ -0,0 +1,13 @@
+name: CI
+on: [push]
+jobs:
+  test:
+    name: Test
+    runs-on: ubuntu-latest
+    steps:
+      - name: Check out code
+        uses: actions/checkout@v1
+      - name: Run tests
+        run: ./run-tests
+      - name: Run against spec
+        run: ./run-spec

vendor/git.knownelement.com/ExternalVendorCode/mo/.github/workflows/release.yaml

@@ -0,0 +1,45 @@
+name: docker push
+on: [push]
+jobs:
+  push_to_registry:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@master
+      - name: Docker meta
+        if: startsWith(github.ref, 'refs/tags/')
+        id: docker_meta
+        uses: crazy-max/ghaction-docker-meta@v1
+        with:
+          images: ghcr.io/${{ github.repository }}
+          tag-match: v(.*)
+      - name: Set up QEMU
+        if: startsWith(github.ref, 'refs/tags/')
+        uses: docker/setup-qemu-action@v1
+      - name: Set up Docker Buildx
+        id: buildx
+        uses: docker/setup-buildx-action@v1
+      - name: Cache Docker layers
+        if: startsWith(github.ref, 'refs/tags/')
+        uses: actions/cache@v2
+        with:
+          path: /tmp/.buildx-cache
+          key: ${{ runner.os }}-buildx-${{ github.sha }}
+          restore-keys: |
+            ${{ runner.os }}-buildx-
+      - name: Login to GitHub Container Registry
+        if: startsWith(github.ref, 'refs/tags/')
+        uses: docker/login-action@v1
+        with:
+          registry: ghcr.io
+          username: ${{ github.repository_owner }}
+          password: ${{ secrets.GITHUB_TOKEN }}
+      - name:  Build and push
+        uses: docker/build-push-action@v2
+        if: startsWith(github.ref, 'refs/tags/')
+        with:
+          builder: ${{ steps.buildx.outputs.name }}
+          platforms: linux/amd64,linux/arm64
+          tags: ${{ steps.docker_meta.outputs.tags }}
+          cache-from: type=local,src=/tmp/.buildx-cache
+          cache-to: type=local,dest=/tmp/.buildx-cache
+          push: true

vendor/git.knownelement.com/ExternalVendorCode/mo/.gitignore

@@ -0,0 +1,9 @@
+*.swp
+diagnostic.partial
+diagnostic.test
+tests/*.diff
+spec/
+spec-runner/
+node_modules/
+package.json
+package-lock.json

vendor/git.knownelement.com/ExternalVendorCode/mo/API.md

@@ -0,0 +1,616 @@
+API / Function Documentation
+============================
+
+This documentation is generated automatically from the source of [mo] thanks to [tomdoc.sh].
+
+
+`mo()`
+------
+
+Public: Template parser function.  Writes templates to stdout.
+
+* $0 - Name of the mo file, used for getting the help message.
+* $@ - Filenames to parse.
+
+Returns nothing.
+
+
+`mo::debug()`
+-------------
+
+Internal: Show a debug message
+
+* $1 - The debug message to show
+
+Returns nothing.
+
+
+`mo::debugShowState()`
+----------------------
+
+Internal: Show a debug message and internal state information
+
+No arguments
+
+Returns nothing.
+
+
+`mo::error()`
+-------------
+
+Internal: Show an error message and exit
+
+* $1 - The error message to show
+* $2 - Error code
+
+Returns nothing. Exits the program.
+
+
+`mo::errorNear()`
+-----------------
+
+Internal: Show an error message with a snippet of context and exit
+
+* $1 - The error message to show
+* $2 - The starting point
+* $3 - Error code
+
+Returns nothing. Exits the program.
+
+
+`mo::usage()`
+-------------
+
+Internal: Displays the usage for mo.  Pulls this from the file that contained the `mo` function.  Can only work when the right filename comes is the one argument, and that only happens when `mo` is called with `$0` set to this file.
+
+* $1 - Filename that has the help message
+
+Returns nothing.
+
+
+`mo::content()`
+---------------
+
+Internal: Fetches the content to parse into MO_UNPARSED.  Can be a list of partials for files or the content from stdin.
+
+* $1 - Destination variable name
+* $2-@ - File names (optional), read from stdin otherwise
+
+Returns nothing.
+
+
+`mo::contentFile()`
+-------------------
+
+Internal: Read a file into MO_UNPARSED.
+
+* $1 - Destination variable name.
+* $2 - Filename to load - if empty, defaults to /dev/stdin
+
+Returns nothing.
+
+
+`mo::indirect()`
+----------------
+
+Internal: Send a variable up to the parent of the caller of this function.
+
+* $1 - Variable name
+* $2 - Value
+
+Examples
+
+    callFunc () {
+        local "$1" && mo::indirect "$1" "the value"
+    }
+    callFunc dest
+    echo "$dest"  # writes "the value"
+
+Returns nothing.
+
+
+`mo::indirectArray()`
+---------------------
+
+Internal: Send an array as a variable up to caller of a function
+
+* $1 - Variable name
+* $2-@ - Array elements
+
+Examples
+
+    callFunc () {
+        local myArray=(one two three)
+        local "$1" && mo::indirectArray "$1" "${myArray[@]}"
+    }
+    callFunc dest
+    echo "${dest[@]}" # writes "one two three"
+
+Returns nothing.
+
+
+`mo::trimUnparsed()`
+--------------------
+
+Internal: Trim leading characters from MO_UNPARSED
+
+Returns nothing.
+
+
+`mo::chomp()`
+-------------
+
+Internal: Remove whitespace and content after whitespace
+
+* $1 - Name of the destination variable
+* $2 - The string to chomp
+
+Returns nothing.
+
+
+`mo::parse()`
+-------------
+
+Public: Parses text, interpolates mustache tags. Utilizes the current value of MO_OPEN_DELIMITER, MO_CLOSE_DELIMITER, and MO_STANDALONE_CONTENT. Those three variables shouldn't be changed by user-defined functions.
+
+* $1 - Destination variable name - where to store the finished content
+* $2 - Content to parse
+* $3 - Preserve standalone status/content - truthy if not empty. When set to a value, that becomes the standalone content value
+
+Returns nothing.
+
+
+`mo::parseInternal()`
+---------------------
+
+Internal: Parse MO_UNPARSED, writing content to MO_PARSED. Interpolates mustache tags.
+
+No arguments
+
+Returns nothing.
+
+
+`mo::parseBlock()`
+------------------
+
+Internal: Handle parsing a block
+
+* $1 - Invert condition ("true" or "false")
+
+Returns nothing
+
+
+`mo::parseBlockFunction()`
+--------------------------
+
+Internal: Handle parsing a block whose first argument is a function
+
+* $1 - Invert condition ("true" or "false")
+* $2-@ - The parsed tokens from inside the block tags
+
+Returns nothing
+
+
+`mo::parseBlockArray()`
+-----------------------
+
+Internal: Handle parsing a block whose first argument is an array
+
+* $1 - Invert condition ("true" or "false")
+* $2-@ - The parsed tokens from inside the block tags
+
+Returns nothing
+
+
+`mo::parseBlockValue()`
+-----------------------
+
+Internal: Handle parsing a block whose first argument is a value
+
+* $1 - Invert condition ("true" or "false")
+* $2-@ - The parsed tokens from inside the block tags
+
+Returns nothing
+
+
+`mo::parsePartial()`
+--------------------
+
+Internal: Handle parsing a partial
+
+No arguments.
+
+Indentation will be applied to the entire partial's contents before parsing. This indentation is based on the whitespace that ends the previously parsed content.
+
+Returns nothing
+
+
+`mo::parseComment()`
+--------------------
+
+Internal: Handle parsing a comment
+
+No arguments.
+
+Returns nothing
+
+
+`mo::parseDelimiter()`
+----------------------
+
+Internal: Handle parsing the change of delimiters
+
+No arguments.
+
+Returns nothing
+
+
+`mo::parseValue()`
+------------------
+
+Internal: Handle parsing value or function call
+
+No arguments.
+
+Returns nothing
+
+
+`mo::isFunction()`
+------------------
+
+Internal: Determine if the given name is a defined function.
+
+* $1 - Function name to check
+
+Be extremely careful.  Even if strict mode is enabled, it is not honored in newer versions of Bash.  Any errors that crop up here will not be caught automatically.
+
+Examples
+
+    moo () {
+        echo "This is a function"
+    }
+    if mo::isFunction moo; then
+        echo "moo is a defined function"
+    fi
+
+Returns 0 if the name is a function, 1 otherwise.
+
+
+`mo::isArray()`
+---------------
+
+Internal: Determine if a given environment variable exists and if it is an array.
+
+* $1 - Name of environment variable
+
+Be extremely careful.  Even if strict mode is enabled, it is not honored in newer versions of Bash.  Any errors that crop up here will not be caught automatically.
+
+Examples
+
+    var=(abc)
+    if moIsArray var; then
+       echo "This is an array"
+       echo "Make sure you don't accidentally use \$var"
+    fi
+
+Returns 0 if the name is not empty, 1 otherwise.
+
+
+`mo::isArrayIndexValid()`
+-------------------------
+
+Internal: Determine if an array index exists.
+
+* $1 - Variable name to check
+* $2 - The index to check
+
+Has to check if the variable is an array and if the index is valid for that type of array.
+
+Returns true (0) if everything was ok, 1 if there's any condition that fails.
+
+
+`mo::isVarSet()`
+----------------
+
+Internal: Determine if a variable is assigned, even if it is assigned an empty value.
+
+* $1 - Variable name to check.
+
+Can not use logic like this in case invalid variable names are passed.      [[ "${!1-a}" == "${!1-b}" ]]
+
+Returns true (0) if the variable is set, 1 if the variable is unset.
+
+
+`mo::isTruthy()`
+----------------
+
+Internal: Determine if a value is considered truthy.
+
+* $1 - The value to test
+* $2 - Invert the value, either "true" or "false"
+
+Returns true (0) if truthy, 1 otherwise.
+
+
+`mo::evaluate()`
+----------------
+
+Internal: Convert token list to values
+
+* $1 - Destination variable name
+* $2-@ - Tokens to convert
+
+Sample call:
+
+      mo::evaluate dest NAME username VALUE abc123 PAREN 2
+
+Returns nothing.
+
+
+`mo::evaluateListOfSingles()`
+-----------------------------
+
+Internal: Convert an argument list to individual values.
+
+* $1 - Destination variable name
+* $2-@ - A list of argument types and argument name/value.
+
+This assumes each value is separate from the rest. In contrast, mo::evaluate will pass all arguments to a function if the first value is a function.
+
+Sample call:
+
+      mo::evaluateListOfSingles dest NAME username VALUE abc123
+
+Returns nothing.
+
+
+`mo::evaluateSingle()`
+----------------------
+
+Internal: Evaluate a single argument
+
+* $1 - Name of variable for result
+* $2 - Type of argument, either NAME or VALUE
+* $3 - Argument
+
+Returns nothing
+
+
+`mo::evaluateKey()`
+-------------------
+
+Internal: Return the value for @key based on current's name
+
+* $1 - Name of variable for result
+
+Returns nothing
+
+
+`mo::evaluateVariable()`
+------------------------
+
+Internal: Handle a variable name
+
+* $1 - Destination variable name
+* $2 - Variable name
+
+Returns nothing.
+
+
+`mo::findVariableName()`
+------------------------
+
+Internal: Find the name of a variable to use
+
+* $1 - Destination variable name, receives an array
+* $2 - Variable name from the template
+
+The array contains the following values
+    * [0] - Variable name
+    * [1] - Array index, or empty string
+
+Example variables      a="a"
+      b="b"
+      c=("c.0" "c.1")
+      d=([b]="d.b" [d]="d.d")
+
+Given these inputs (function input, current value), produce these outputs      a c => a
+      a c.0 => a
+      b d => d.b
+      b d.d => d.b
+      a d => d.a
+      a d.d => d.a
+      c.0 d => c.0
+      d.b d => d.b
+      '' c => c
+      '' c.0 => c.0
+ Returns nothing.
+
+
+`mo::join()`
+------------
+
+Internal: Join / implode an array
+
+* $1    - Variable name to receive the joined content
+* $2    - Joiner
+* $3-@ - Elements to join
+
+Returns nothing.
+
+
+`mo::evaluateFunction()`
+------------------------
+
+Internal: Call a function.
+
+* $1 - Variable for output
+* $2 - Content to pass
+* $3 - Function to call
+* $4-@ - Additional arguments as list of type, value/name
+
+Returns nothing.
+
+
+`mo::standaloneCheck()`
+-----------------------
+
+Internal: Check if a tag appears to have only whitespace before it and after it on a line. There must be a new line before and there must be a newline after or the end of a string
+
+No arguments.
+
+Returns 0 if this is a standalone tag, 1 otherwise.
+
+
+`mo::standaloneProcess()`
+-------------------------
+
+Internal: Process content before and after a tag. Remove prior whitespace up to the previous newline. Remove following whitespace up to and including the next newline.
+
+No arguments.
+
+Returns nothing.
+
+
+`mo::indentLines()`
+-------------------
+
+Internal: Apply indentation before any line that has content in MO_UNPARSED.
+
+* $1 - Destination variable name.
+* $2 - The indentation string.
+* $3 - The content that needs the indentation string prepended on each line.
+
+Returns nothing.
+
+
+`mo::escape()`
+--------------
+
+Internal: Escape a value
+
+* $1 - Destination variable name
+* $2 - Value to escape
+
+Returns nothing
+
+
+`mo::getContentUntilClose()`
+----------------------------
+
+Internal: Get the content up to the end of the block by minimally parsing and balancing blocks. Returns the content before the end tag to the caller and removes the content + the end tag from MO_UNPARSED. This can change the delimiters, adjusting MO_OPEN_DELIMITER and MO_CLOSE_DELIMITER.
+
+* $1 - Destination variable name
+* $2 - Token string to match for a closing tag
+
+Returns nothing.
+
+
+`mo::tokensToString()`
+----------------------
+
+Internal: Convert a list of tokens to a string
+
+* $1 - Destination variable for the string
+* $2-$@ - Token list
+
+Returns nothing.
+
+
+`mo::getContentTrim()`
+----------------------
+
+Internal: Trims content from MO_UNPARSED, returns trimmed content.
+
+* $1 - Destination variable
+
+Returns nothing.
+
+
+`mo::getContentComment()`
+-------------------------
+
+Get the content up to and including a close tag
+
+* $1 - Destination variable
+
+Returns nothing.
+
+
+`mo::getContentDelimiter()`
+---------------------------
+
+Get the content up to and including a close tag. First two non-whitespace tokens become the new open and close tag.
+
+* $1 - Destination variable
+
+Returns nothing.
+
+
+`mo::getContentWithinTag()`
+---------------------------
+
+Get the content up to and including a close tag. First two non-whitespace tokens become the new open and close tag.
+
+* $1 - Destination variable, an array
+* $2 - Terminator string
+
+The array contents:      [0] The raw content within the tag
+      [1] The parsed tokens as a single string
+
+Returns nothing.
+
+
+`mo::tokenizeTagContents()`
+---------------------------
+
+Internal: Parse MO_UNPARSED and retrieve the content within the tag delimiters. Converts everything into an array of string values.
+
+* $1 - Destination variable for the array of contents.
+* $2 - Stop processing when this content is found.
+
+The list of tokens are in RPN form. The first item in the resulting array is the number of actual tokens (after combining command tokens) in the list.
+
+Given: a 'bc' "de\"\n" (f {g 'h'}) Result: ([0]=4 [1]=NAME [2]=a [3]=VALUE [4]=bc [5]=VALUE [6]=$'de\"\n' [7]=NAME [8]=f [9]=NAME [10]=g [11]=VALUE [12]=h [13]=BRACE [14]=2 [15]=PAREN [16]=2
+
+Returns nothing
+
+
+`mo::tokenizeTagContentsName()`
+-------------------------------
+
+Internal: Get the contents of a variable name.
+
+* $1 - Destination variable name for the token list (array of strings)
+
+Returns nothing
+
+
+`mo::tokenizeTagContentsDoubleQuote()`
+--------------------------------------
+
+Internal: Get the contents of a tag in double quotes. Parses the backslash sequences.
+
+* $1 - Destination variable name for the token list (array of strings)
+
+Returns nothing.
+
+
+`mo::tokenizeTagContentsSingleQuote()`
+--------------------------------------
+
+Internal: Get the contents of a tag in single quotes. Only gets the raw value.
+
+* $1 - Destination variable name for the token list (array of strings)
+
+Returns nothing.
+
+
+`MO_ORIGINAL_COMMAND`
+---------------------
+
+Save the original command's path for usage later
+
+
+[mo]: ./mo
+[tomdoc.sh]: https://github.com/tests-always-included/tomdoc.sh

vendor/git.knownelement.com/ExternalVendorCode/mo/Dockerfile

@@ -0,0 +1,7 @@
+FROM alpine
+
+RUN apk add --no-cache bash
+ADD mo /usr/local/bin/mo
+RUN chmod +x /usr/local/bin/mo
+
+ENTRYPOINT /usr/local/bin/mo

vendor/git.knownelement.com/ExternalVendorCode/mo/LICENSE.md

@@ -0,0 +1,7 @@
+Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+Except as contained in this notice, the name(s) of the above copyright holders shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization.
+
+The end-user documentation included with the redistribution, if any, must include the following acknowledgment: "This product includes software developed  by contributors", in the same place and form as other third-party acknowledgments. Alternately, this acknowledgment may appear in the software itself, in the same form and location as other such third-party acknowledgments.

vendor/git.knownelement.com/ExternalVendorCode/mo/README.md

@@ -0,0 +1,340 @@
+Mo - Mustache Templates in Bash
+===============================
+
+[Mustache] templates are simple, logic-less templates.  Because of their simplicity, they are able to be ported to many languages.  The syntax is quite simple.
+
+    Hello, {{NAME}}.
+
+    I hope your {{TIME_PERIOD}} was fun.
+
+The above file is [`demo/fun-trip.mo`](demo/fun-trip.mo).  Let's try using this template some data from bash's environment.  Go to your checked out copy of the project and run a command like this:
+
+    NAME=Tyler TIME_PERIOD=weekend ./mo demo/fun-trip.mo
+
+Your result?
+
+    Hello, Tyler.
+
+    I hope your weekend was fun.
+
+This bash version supports conditionals, functions (both as filters and as values), as well as indexed arrays (for iteration).  You are able to leverage these additional features by adding more information into the environment.  It is easiest to do this when you source `mo`.  See the [demo scripts](demo/) for further examples.
+
+
+Requirements
+------------
+
+* Bash 3.x (the aim is to make it work on Macs)
+* The "coreutils" package (`basename` and `cat`)
+* ... that's it.  Why?  Because bash **can**!
+
+If you intend to develop this and run the official specs, you also need node.js.
+
+
+Installation
+------------
+
+There are a few ways you can install this tool.  How you install it depends on how you want to use it.
+
+
+### Globally; For Everyone
+
+You can install this file in `/usr/local/bin/` or `/usr/bin/` by simply downloading it, changing the permissions, then moving it to the right location.  Double check that your system's PATH includes the destination folder, otherwise users may have a hard time starting the command.
+
+    # Download
+    curl -sSL https://raw.githubusercontent.com/tests-always-included/mo/master/mo -o mo
+
+    # Make executable
+    chmod +x mo
+
+    # Move to the right folder
+    sudo mv mo /usr/local/bin/
+
+    # Test
+    echo "works" | mo
+
+
+### Locally; For Yourself
+
+This is very similar to installing it globally but it does not require root privileges.  It is very important that your PATH includes the destination folder otherwise it won't work.  Some local folders that are typically used are `~/bin/` and `~/.local/bin/`.
+
+    # Download
+    curl -sSL https://raw.githubusercontent.com/tests-always-included/mo/master/mo -o mo
+
+    # Make executable
+    chmod +x mo
+
+    # Ensure destination folder exists
+    mkdir -p ~/.local/bin/
+
+    # Move to the right folder
+    mv mo ~/.local/bin/
+
+    # Test
+    echo "works" | mo
+
+
+### As A Library; For A Tool
+
+Bash scripts can source `mo` to include the functionality in their own routines.  This usage typically would have `mo` saved to a `lib/` folder in an application and your other scripts would use `. lib/mo` to bring it into your project.
+
+    # Download
+    curl -sSL https://raw.githubusercontent.com/tests-always-included/mo/master/mo -o mo
+
+    # Move into your project folder
+    mv mo ~/projects/amazing-things/lib/
+
+To allow it to work this way, you either should source the file (`. "lib/mo"`) or make it executable (`chmod +x lib/mo`) and run it from your scripts.
+
+
+How to Use
+----------
+
+If you only plan using strings and numbers, nothing could be simpler.  In your shell script you can choose to export the variables.  The below script is [`demo/using-strings`](demo/using-strings).
+
+    #!/usr/bin/env bash
+    cd "$(dirname "$0")" # Go to the script's directory
+    export TEST="This is a test"
+    echo "Your message:  {{TEST}}" | ../mo
+
+The result?  "Your message:  This is a test".
+
+Using arrays adds a slight level of complexity.  *You must source `mo`.*  Look at [`demo/using-arrays`](demo/using-arrays).
+
+    #!/usr/bin/env bash
+    cd "$(dirname "$0")" # Go to the script's directory
+    export ARRAY=( one two "three three three" four five )
+    . ../mo # This loads the "mo" function
+    cat << EOF | mo
+    Here are the items in the array:
+    {{#ARRAY}}
+        * {{.}}
+    {{/ARRAY}}
+    EOF
+
+The result?  You get a list of the five elements in the array.  It is vital that you source `mo` and run the function when you want arrays to work because you can not execute a command and have arrays passed to that command's environment.  Instead, we first source the file to load the function and then run the function directly.
+
+There are more scripts available in the [demos directory](demo/) that could help illustrate how you would use this program.
+
+There are additional features that the program supports. Try using `mo --help` to see what is available.
+
+Please note that this command is written in Bash and pulls data from either the environment or (when using `--source`) from a text file that will be sourced and loaded into the environment, which means you will need to have Bash-style variables defined. Please see the examples in `demo/` for different ways you can use `mo`.
+
+
+Enhancements
+------------
+
+In addition to many of the features built-in to Mustache, `mo` includes a number of unique features that make it a bit more powerful.
+
+### Loop @key
+
+`mo` implements Handlebar's `@key` references for outputting the key inside of a loop:
+
+Env:
+```bash
+myarr=( foo bar )
+
+# Bash v4+
+declare -A myassoc
+myassoc[hello]="mo"
+myassoc[world]="is great"
+```
+
+Template:
+```handlebars
+{{#myarr}}
+ - {{@key}} {{.}}
+{{/myarr}}
+
+{{#myassoc}}
+ * {{@key}} {{.}}
+{{/myassoc}}
+```
+
+Output:
+```markdown
+ - 0 foo
+ - 1 bar
+
+ * hello mo
+ * world is great
+```
+
+
+### Helpers / Function Arguments
+
+Function Arguments are not a part of the official Mustache implementation, and are more often associated with Handlebar's Helper functionality.
+
+`mo` allows for passing strings to functions.
+
+```handlebars
+{{myfunc foo bar}}
+```
+
+For security reasons, these arguments are not immediately available to function calls without a flag.
+
+#### with `--allow-function-arguments`
+
+```bash
+myfunc() {
+    # Outputs "foo, bar"
+    echo "$1, $2";
+}
+```
+
+#### Using `$MO_FUNCTION_ARGS`
+
+```bash
+myfunc() {
+    # Outputs "foo, bar"
+    echo "${MO_FUNCTION_ARGS[0]}, ${MO_FUNCTION_ARGS[1]}";
+}
+```
+
+### Triple Mustache, Parenthesis, and Quotes
+
+Normally, triple mustache syntax, such as `{{{var}}}` will avoid HTML escaping of the variable. Because HTML escaping is not supported in `mo`, this is now used differently. Anything within braces will be looked up and the values will be concatenated together and the result will be treated as a value. Anything in parenthesis will be looked up, concatenated, and treated as a name. Also, anything in single quotes is passed as a value; double quoted things first are unescaped and then passed as a value.
+
+```
+# Example input
+var=abc
+user=admin
+admin=Administrator
+u=user
+abc=([0]=zero [1]=one [2]=two)
+```
+
+| Mustache syntax | Resulting output | Notes |
+|-----------------|------------------|-------|
+| `{{var}}` | `abc` | Normal behavior |
+| `{{var us}}` | `abcus` | Concatenation |
+| `{{'var'}}` | `var` | Passing as a value |
+| `{{"a\tb"}}` | `a       b` | There was an escaped tab in the value |
+| `{{u}}` | `user` | Normal behavior |
+| `{{{u}}}` | `user` | Look up "$u", treat as the value `{{'user'}}` |
+| `{{(u)}}` | `admin` | Look up "$u", treat as the name `{{user}}` |
+| `{{var user}}` | `abcuser` | Concatenation |
+| `{{(var '.1')}}` | `one` | Look up "$var", treat as "abc", then concatenate ".1" and look up `{{abc.1}}` |
+
+In double-quoted strings, the following escape sequences are defined.
+
+* `\"` - Quote
+* `\b` - Bell
+* `\e` - Escape (note that Bash typically uses $'\E' for the same thing)
+* `\f` - Form feed
+* `\n` - Newline
+* `\r` - Carriage return
+* `\t` - Tab
+* `\v` - Vertical tab
+* Anything else will skip the `\` and place the next character. However, this implementation is allowed to change in the future if a different escape character mapping becomes commonplace.
+
+
+Environment Variables and Functions
+-----------------------------------
+
+There are several functions and variables used to process templates. `mo` reserves variables that start with `MO_` for variables exposing data or configuration, functions starting with `mo::`, and local variables starting with `mo[A-Z]`. You are welcome to use internal functions, though only ones that are marked as "Public" should not change their interface. Scripts may also read any of the variables.
+
+Functions are all executed in a subshell, with another subshell for lambdas. Thus, your lambda can't affect the parsing of a template. There's more information about lambdas when talking about tests that fail.
+
+* `MO_ALLOW_FUNCTION_ARGUMENTS` - When set to a non-empty value, this allows functions referenced in templates to receive additional options and arguments.
+* `MO_CLOSE_DELIMITER` - The string used when closing a tag. Defaults to "}}". Used internally.
+* `MO_CLOSE_DELIMITER_DEFAULT` - The default value of `MO_CLOSE_DELIMITER`. Used when resetting the close delimiter, such as when parsing a partial.
+* `MO_CURRENT` - Variable name to use for ".".
+* `MO_DEBUG` - When set to a non-empty value, additional debug information is written to stderr.
+* `MO_FUNCTION_ARGS` - Arguments passed to the function.
+* `MO_FAIL_ON_FILE` - If a filename from the command-line is missing or a partial does not exist, abort with an error.
+* `MO_FAIL_ON_FUNCTION` - If a function returns a non-zero status code, abort with an error.
+* `MO_FAIL_ON_UNSET` - When set to a non-empty value, expansion of an unset env variable will be aborted with an error.
+* `MO_FALSE_IS_EMPTY` - When set to a non-empty value, the string "false" will be treated as an empty value for the purposes of conditionals.
+* `MO_OPEN_DELIMITER` - The string used when opening a tag. Defaults to "{{". Used internally.
+* `MO_OPEN_DELIMITER_DEFAULT` - The default value of MO_OPEN_DELIMITER. Used when resetting the open delimiter, such as when parsing a partial.
+* `MO_ORIGINAL_COMMAND` - Used to find the `mo` program in order to generate a help message.
+* `MO_PARSED` - Content that has made it through the template engine.
+* `MO_STANDALONE_CONTENT` - The unparsed content that preceeded the current tag. When a standalone tag is encountered, this is checked to see if it only contains whitespace. If this and the whitespace condition after a tag is met, then this will be reset to $'\n'.
+* `MO_UNPARSED` - Template content yet to make it through the parser.
+
+
+Concessions
+-----------
+
+I admit that implementing everything in bash just doesn't make a lot of sense.  For example, the following things just don't work because they don't really mesh with the "bash way".
+
+Pull requests to solve the following issues would be helpful.
+
+
+### Mustache Syntax
+
+* Dotted names are supported but only for associative arrays (Bash 4).  See [`demo/associative-arrays`](demo/associative-arrays) for an example.
+* There's no "top level" object, so `echo '{{.}}' | ./mo` does not do anything useful.  In other languages you can say the data for the template is a string and in `mo` the data is always the environment.  Luckily this type of usage is rare and `{{.}}` works great when iterating over an array.
+* [Parents](https://mustache.github.io/mustache.5.html#Parents), where a template can override chunks of a partial, are not supported.
+* HTML encoding is not built into `mo`.  `{{{var}}}`, `{{&var}}` and `{{var}}` all do the same thing.  `echo '{{TEST}}' | TEST='<b>' mo` will give you "`<b>`" instead of "`&gt;b&lt;`".
+
+
+### General Scripting Issues
+
+* Using binary files as templates is simply not allowed.
+* Bash does not support anything more complex than strings/numbers inside of associative arrays.  I'm not able to add objects nor nested arrays to bash - it's just a shell after all!
+* You must make sure the data is in the environment when `mo` runs.  The easiest way to do that is to source `mo` in your shell script after setting up lots of other environment variables / functions.
+
+
+Developing
+----------
+
+Check out the code and hack away.  Please add tests to show off bugs before fixing them.  New functionality should also be covered by a test.
+
+First, make sure you install Node.js. After that, run `npm run install-tests` to get the dependencies and the repository of YAML tests. Run `npm run test` to run the JavaScript tests. There's over 100 of them, which is great. Not all of them will pass, but that's discussed later.
+
+When submitting patches, make sure to run them past [ShellCheck] and ensure no problems are found.  Also please use Bash 3 syntax if you are manipulating arrays.
+
+
+### Porting and Backporting
+
+In case of problems, setting MO_DEBUG to a non-empty value will give you LOTS of output.
+
+    MO_DEBUG=1 ./mo my-template
+
+
+### Failed Specs
+
+It is acceptable for some of the official spec tests to fail. The spec runner has specific exclusions and overrides to test similar functionality that avoid the following issues.
+
+ * Using `{{.}}` outside of a loop - In order to access any variable, you must use its name. In a loop, `{{.}}` will refer to the current value, but outside the loop you are unable to use this dot notation because there is no current value.
+ * Deeply nested data - Bash doesn't support complex data structure. Basically, just strings and arrays of strings.
+ * Interpolation; Multiple Calls:  This fails because lambdas execute in a subshell so their output can be captured. If you want state to be preserved, you will need to write it outside of the current environment and load it again later.
+ * HTML Escaping - Since bash is not often executed in a web server context, it makes no sense to have the output escaped as HTML.  Performing shell escaping of variables may be an option in the future if there's a demand.
+ * Lambdas - Function results are *not* automatically interpreted again. If you want to parse the results as Mustache content, use `mo::parse`. When they use `mo::parse`, it will use the current delimiters.
+
+ For lambdas, these examples may help.
+
+ ```bash
+ # Retrieve content into a variable.
+ content=$(cat)
+
+ # Retrieve all content and do not trim newlines at the end.
+ content=$(cat; echo -n '.')
+ content=${content%.}
+
+ # Parse content using the current delimiters
+ mo::parse results "This is my content. Hello, {{username}}"
+ echo -n "$results"
+
+ # Parse content using the default delimiters
+ MO_OPEN_DELIMITER=$MO_OPEN_DELIMITER_DEFAULT
+ MO_CLOSE_DELIMITER=$MO_CLOSE_DELIMITER_DEFAULT
+ mo::parse results "This is my content. Hello, {{username}}"
+ echo -n "$results"
+ ```
+
+
+### Future Enhancements
+
+There's a few places in the code marked with `TODO` to signify areas that could use improvement.  Care to help?  Keep in mind that this uses bash exclusively, so it might not look the prettiest.
+
+
+License
+-------
+
+This program is licensed under an MIT license with an additional non-advertising clause.  See [LICENSE.md](LICENSE.md) for the full text.
+
+
+[Mustache]: https://mustache.github.io/
+[ShellCheck]: https://github.com/koalaman/shellcheck

vendor/git.knownelement.com/ExternalVendorCode/mo/demo/associative-arrays

@@ -0,0 +1,19 @@
+#!/usr/bin/env bash
+
+cd "$(dirname "$0")" # Go to the script's directory
+
+declare -A DATA
+export DATA=([one]=111 [two]=222)
+. ../mo
+
+cat <<EOF | mo
+Accessing data directly:
+    DATA: {{DATA}}
+    One: {{DATA.one}}
+    Two: {{DATA.two}}
+
+Things in DATA:
+{{#DATA}}
+    Item: {{.}}
+{{/DATA}}
+EOF

vendor/git.knownelement.com/ExternalVendorCode/mo/demo/embedded-template

@@ -0,0 +1,28 @@
+#!/usr/bin/env bash
+#
+# This embeds a template in the script without using strange `cat` syntax.
+# shellcheck disable=SC1083 disable=SC1010 disable=SC1054 disable=SC1073 disable=SC1072 disable=SC1056 disable=SC1009
+
+cd "$(dirname "$0")" # Go to the script's directory
+
+export NAME="Tyler"
+export VEHICLE="Ford Explorer"
+export OVERDUE_LENGTH="2 months"
+export OPTIONS=(
+    "Call a service representative at 1-800-000-0000 to discuss payment options"
+    "Return the vehicle immediately and pay a fine of 1 million dollars"
+)
+. ../mo
+sed '0,/^# END/ d' "$(basename "$0")" | mo
+exit
+
+# END
+Attention {{NAME}},
+
+You need to pay for the {{VEHICLE}} you are leasing from us.
+It has been {{OVERDUE_LENGTH}} since your last payment.
+At this point you must do one of the following:
+
+{{#OPTIONS}}
+ * {{.}}
+{{/OPTIONS}}

vendor/git.knownelement.com/ExternalVendorCode/mo/demo/fun-trip.mo

@@ -0,0 +1,3 @@
+Hello, {{NAME}}
+
+I hope your {{TIME_PERIOD}} was fun.

vendor/git.knownelement.com/ExternalVendorCode/mo/demo/function-args

@@ -0,0 +1,31 @@
+#!/usr/bin/env bash
+#
+# This sources a simple script with the env. variables needed for the template.
+
+cd "$(dirname "$0")" # Go to the script's directory
+source ../mo
+
+export NAME="Alex"
+export ARRAY=( AAA BBB CCC )
+
+# Include an external template
+INCLUDE() {
+    # shellcheck disable=SC2031
+    cat "${MO_FUNCTION_ARGS[0]}"
+}
+
+# Print section title
+TITLE() {
+    echo "+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+"
+    # shellcheck disable=SC2031
+    echo "${MO_FUNCTION_ARGS[0]}"
+    echo "+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+"
+}
+
+cat <<EOF | mo -u
+{{TITLE 'Part 1'}}
+{{INCLUDE 'function-args-part1'}}
+
+{{TITLE 'Part 2'}}
+{{INCLUDE 'function-args-part2'}}
+EOF

vendor/git.knownelement.com/ExternalVendorCode/mo/demo/function-args-part1

@@ -0,0 +1 @@
+Hello, my name is {{NAME}}.

vendor/git.knownelement.com/ExternalVendorCode/mo/demo/function-args-part2

@@ -0,0 +1,3 @@
+{{#ARRAY}}
+    * {{.}}
+{{/ARRAY}}

vendor/git.knownelement.com/ExternalVendorCode/mo/demo/function-for-advanced-looping

@@ -0,0 +1,42 @@
+#!/usr/bin/env bash
+
+cd "$(dirname "$0")" # Go to the script's directory
+
+EVERY_REPO() {
+    # The block contents come in through standard input. Capture it here.
+    content=$(cat)
+
+    echo "# Starting EVERY_REPO"
+
+    # Get list of repos
+    for REPO in "${REPOS[@]}"; do
+        echo "## Looping one time for repo: $REPO"
+
+        # String replace REPO_ with the name
+        # This changes everything in the content block of the template.
+        # It rewrites {{__REPO__.name}} into {{resque.name}}, for instance.
+        # You can prefix your environment variables and do other things as well.
+        
+        echo "$content" | sed "s/__REPO__/${REPO}/"
+
+        echo "## Looped one time for repo: $REPO"
+    done
+
+    echo "# Finished EVERY_REPO"
+}
+
+REPOS=(resque hub rip)
+
+declare -A resque hub rip
+resque=([name]=Resque [url]=http://example.com/resque)
+hub=([name]=Hub [url]=http://example.com/hub)
+rip=([name]=Rip [url]=http://example.com/rip)
+. ../mo
+cat <<EOF | mo
+{{#EVERY_REPO}}
+The repo is __REPO__
+    Name:  {{__REPO__.name}}
+    URL:  {{__REPO__.url}}
+{{/EVERY_REPO}}
+
+EOF

vendor/git.knownelement.com/ExternalVendorCode/mo/demo/function-for-building-json

@@ -0,0 +1,39 @@
+#!/usr/bin/env bash
+
+cd "$(dirname "$0")" # Go to the script's directory
+
+# Detect if this is the first item and write a comma if it is.
+# Normally, I would track this using a variable, like so:
+#
+# COMMA_IF_NOT_FIRST_FLAG=false
+# COMMA_IF_NOT_FIRST() {
+#     $COMMA_IF_NOT_FIRST || echo ","
+#     COMMA_IF_NOT_FIRST_FLAG=true
+# }
+#
+# Since this function executes in a subshell, that approach will not work.
+# Instead, we peek inside mo and see what is being processed. If the variable
+# name in moParse() changes, this will need to get updated as well. An
+# alternate variable that is usable is context, but that is in moLoop() and is
+# two levels levels deep instead of just one.
+COMMA_IF_NOT_FIRST() {
+    [[ "${moCurrent#*.}" != "0" ]] && echo ","
+}
+
+# Create an array that will be embedded into the JSON. If you are manipulating
+# JSON, might I suggest you look at using jq? It's really good at processing
+# JSON.
+items=(
+    '{"position":"one","url":"1"}'
+    '{"position":"two","url":"2"}'
+    '{"position":"three","url":"3"}'
+)
+. ../mo
+cat <<EOF | mo
+{
+    {{#items}}
+    {{COMMA_IF_NOT_FIRST}}
+    {{.}}
+    {{/items}}
+}
+EOF

vendor/git.knownelement.com/ExternalVendorCode/mo/demo/function-for-foreach

@@ -0,0 +1,50 @@
+#!/usr/bin/env bash
+# Example for how #29 can get implemented.
+
+cd "$(dirname "$0")" # Go to the script's directory
+
+foreach() {
+    # Trying to use unique names
+    local foreachSourceName foreachIterator foreachEvalString foreachContent
+
+    foreachContent=$(cat)
+
+    local x
+    x=("${@}")
+    if [[ "$2" != "as" && "$2" != "in" ]]; then
+        echo "Invalid foreach - bad format."
+    elif [[ "$(declare -p "$1")" != "declare -"[aA]* ]]; then
+        echo "$1 is not an array"
+    else
+        foreachSourceName="${1}[@]"
+
+        for foreachIterator in "${!foreachSourceName}"; do
+            foreachEvalString=$(declare -p "$foreachIterator")
+            foreachEvalString="declare -A $3=${foreachEvalString#*=}"
+            eval "$foreachEvalString"
+            echo "$foreachContent" | mo
+        done
+    fi
+}
+
+
+# The links are associative arrays
+declare -A resque hub rip
+resque=([name]=Resque [url]=http://example.com/resque)
+hub=([name]=Hub [url]=http://example.com/hub)
+rip=([name]=Rip [url]=http://example.com/rip)
+
+# This is a list of the link arrays
+links=(resque hub rip)
+
+# Source mo in order to work with arrays
+. ../mo
+
+# Process the template
+cat <<EOF | mo --allow-function-arguments
+Here are your links:
+{{#foreach 'links' 'as' 'link'}}
+ * [{{link.name}}]({{link.url}})
+{{/foreach 'links' 'as' 'link'}}
+
+EOF

vendor/git.knownelement.com/ExternalVendorCode/mo/demo/important-file

@@ -0,0 +1,28 @@
+#!/usr/bin/env bash
+
+cd "$(dirname "$0")"/..
+
+date-string() {
+    date
+}
+wrapper() {
+    echo -n "*** $(cat) ***"
+}
+
+export IP=127.0.0.1
+export ALLOWED_HOSTS=( 192.168.0.1 192.168.0.2 192.168.0.3 )
+
+. ./mo  # Keep in mind this script is executing in the parent directory
+cat <<EOF | mo
+# {{#wrapper}}OH SO IMPORTANT{{/wrapper}}
+# This file automatically generated at {{date-string}}
+home_ip={{IP}}
+
+# ALLOWED HOSTS
+{{#ALLOWED_HOSTS}}allowed_host={{.}}
+{{/ALLOWED_HOSTS}}{{^ALLOWED_HOSTS}}# No allowed hosts{{/ALLOWED_HOSTS}}
+
+# DENIED HOSTS
+{{#DENIED_HOSTS}}denied_host={{.}}
+{{/DENIED_HOSTS}}{{^DENIED_HOSTS}}# No denied hosts{{/DENIED_HOSTS}}
+EOF

vendor/git.knownelement.com/ExternalVendorCode/mo/demo/indented-partial

@@ -0,0 +1,15 @@
+#!/usr/bin/env bash
+
+export data=$'line 1\nline 2'
+
+cat <<EOF | ../mo
+Here is a partial without an indent:
+
+{{> partial}}
+
+And here's the same partial with a 4-space indent:
+
+    {{> partial}}
+
+:-)
+EOF

vendor/git.knownelement.com/ExternalVendorCode/mo/demo/partial

@@ -0,0 +1 @@
+{{data}}

vendor/git.knownelement.com/ExternalVendorCode/mo/demo/sourcing

@@ -0,0 +1,13 @@
+#!/usr/bin/env bash
+#
+# This sources a simple script with the env. variables needed for the template.
+
+cd "$(dirname "$0")" # Go to the script's directory
+
+cat <<EOF | ../mo --source=sourcing.vars
+Hello, my name is {{NAME}}.
+And this is ARRAY's conntents:
+{{#ARRAY}}
+    * {{.}}
+{{/ARRAY}}
+EOF

vendor/git.knownelement.com/ExternalVendorCode/mo/demo/sourcing.vars

@@ -0,0 +1,2 @@
+export NAME="Alex"
+export ARRAY=( AAA BBB CCC )

vendor/git.knownelement.com/ExternalVendorCode/mo/demo/using-arrays

@@ -0,0 +1,10 @@
+#!/usr/bin/env bash
+cd "$(dirname "$0")" # Go to the script's directory
+export ARRAY=( one two "three three three" four five )
+. ../mo
+cat << EOF | mo
+Here are the items in the array:
+{{#ARRAY}}
+    * {{.}}
+{{/ARRAY}}
+EOF

vendor/git.knownelement.com/ExternalVendorCode/mo/demo/using-strings

@@ -0,0 +1,7 @@
+#!/usr/bin/env bash
+#
+# This example does not source `mo` and is intentionally restricted to
+# variables that are not arrays.
+cd "$(dirname "$0")" # Go to the script's directory
+export TEST="This is a test"
+echo "Your message:  {{TEST}}" | ../mo

vendor/git.knownelement.com/ExternalVendorCode/mo/demo/writing-out-braces

@@ -0,0 +1,12 @@
+#!/usr/bin/env bash
+
+cd "$(dirname "$0")" # Go to the script's directory
+
+
+export OPEN="{{"
+export CLOSE="}}"
+cat <<'EOF' | mo
+You can use environment variables to write output that has double braces.
+
+    {{OPEN}}sampleTag{{CLOSE}}
+EOF

vendor/git.knownelement.com/ExternalVendorCode/mo/make-api-doc

@@ -0,0 +1,20 @@
+#!/usr/bin/env bash
+#
+# This requires tomdoc.sh to be in your PATH.
+# https://github.com/tests-always-included/tomdoc.sh
+
+cd "${0%/*}" || exit 1
+
+cat <<'EOF'
+API / Function Documentation
+============================
+
+This documentation is generated automatically from the source of [mo] thanks to [tomdoc.sh].
+
+
+EOF
+sed 's/# shellcheck.*//' mo | tomdoc.sh -m
+cat <<'EOF'
+[mo]: ./mo
+[tomdoc.sh]: https://github.com/tests-always-included/tomdoc.sh
+EOF

vendor/git.knownelement.com/ExternalVendorCode/mo/run-spec

@@ -0,0 +1,22 @@
+#!/usr/bin/env bash
+
+# Install or update the specs
+if [[ ! -d spec ]]; then
+    git clone https://github.com/mustache/spec.git spec
+else
+    (
+        cd spec
+        git pull
+    )
+fi
+
+if [[ "$BASH_VERSION" == 3.* ]]; then
+    echo "WARNING! Specs assume you are using a version of Bash with associative arrays!"
+fi
+
+# Actually run the specs
+node run-spec.js spec/specs/*.json
+
+if [[ "$BASH_VERSION" == 3.* ]]; then
+    echo "Some tests may have failed because they assume Bash supports associative arays"
+fi

vendor/git.knownelement.com/ExternalVendorCode/mo/run-spec.js

@@ -0,0 +1,512 @@
+#!/usr/bin/env node
+
+const exec = require("child_process").exec;
+const fsPromises = require("fs").promises;
+
+// Skip or override portions of tests. The goal is to still have as much
+// coverage as possible, but skip things that Bash does not support.
+//
+// To skip a test, define a "skip" property and explain why the test is
+// skipped.
+//
+// To override any test property, just define that property. It replaces the
+// original property, not augmenting it.
+const testOverrides = {
+    "Comments -> Variable Name Collision": {
+        // Can't use variables with exclamation points easily
+        data: {
+            comment: 4
+        }
+    },
+    "Interpolation -> Dotted Names - Arbitrary Depth": {
+        skip: "Not able to use more than one level of depth"
+    },
+    "Interpolation -> Dotted Names - Broken Chain Resolution": {
+        data: {
+            a: {
+                b: "wrong"
+            },
+            name: "Jim"
+        },
+        template: '"{{a.name}}" == ""'
+    },
+    "Interpolation -> Dotted Names - Initial Resolution": {
+        data: {
+            a: {
+                name: "Phil"
+            },
+            name: "Wrong"
+        },
+        template: "\"{{#a}}{{name}}{{/a}}\" == \"Phil\""
+    },
+    "Interpolation -> Implicit Iterators - Ampersand": {
+        skip: "HTML escaping is not supported"
+    },
+    "Interpolation -> Implicit Iterators - Basic Interpolation": {
+        skip: "Can not use {{.}} outside of a loop. Need to use a variable name."
+    },
+    "Interpolation -> Implicit Iterators - Basic Integer Interpolation": {
+        skip: "Can not use {{.}} outside of a loop. Need to use a variable name."
+    },
+    "Interpolation -> Implicit Iterators - Triple Mustache": {
+        skip: "Can not use {{.}} outside of a loop. Need to use a variable name."
+    },
+    "Interpolation -> HTML Escaping": {
+        skip: "HTML escaping is not supported"
+    },
+    "Interpolation -> Implicit Iterators - HTML Escaping": {
+        skip: "HTML escaping is not supported"
+    },
+    "Inverted -> Dotted Names - Falsey": {
+        data: {
+            a: {
+                b: ""
+            }
+        },
+        template: '"{{^a.b}}Not Here{{/a.b}}" == "Not Here"'
+    },
+    "Inverted -> Dotted Names - Truthy": {
+        data: {
+            a: {
+                b: "1"
+            }
+        },
+        template: '"{{^a.b}}Not Here{{/a.b}}" == ""'
+    },
+    "Lambdas -> Escaping": {
+        skip: "HTML escaping is not supported"
+    },
+    "Lambdas -> Interpolation - Alternate Delimiters": {
+        skip: "There is no difference between a lamba used as a value and a lambda used as a block. Both will parse using the current delimiters."
+    },
+    "Lambdas -> Inverted Section": {
+        // This one passed mostly by accident. Correcting so the test still
+        // tests what is was designed to illustrate.
+        data: {
+            static: "static",
+            lambda: {
+                __tag__: 'code',
+                bash: 'false'
+            }
+        }
+    },
+    "Lambdas -> Interpolation": {
+        data: {
+            lambda: {
+                __tag__: 'code',
+                bash: 'echo -n "world"'
+            }
+        }
+    },
+    "Lambdas -> Interpolation - Expansion": {
+        data: {
+            lambda: {
+                __tag__: 'code',
+                bash: 'mo::parse result "{{planet}}"; echo -n "$result"'
+            },
+            planet: 'world'
+        }
+    },
+    "Lambdas -> Interpolation - Multiple Calls": {
+        skip: "Calls are not cached, but they run in isolated environments, so saving a global variable does not work."
+    },
+    "Lambdas -> Section": {
+        data: {
+            lambda: {
+                __tag__: 'code',
+                bash: 'if [[ "$(cat)" == "{{x}}" ]]; then echo -n yes; else echo -n no; fi'
+            },
+            x: "Error!"
+        }
+    },
+    "Lambdas -> Section - Alternate Delimiters": {
+        data: {
+            lambda: {
+                __tag__: 'code',
+                bash: 'local content=$(cat); mo::parse content "$content{{planet}} => |planet|$content"; echo -n "$content"'
+            },
+            planet: 'Earth'
+        }
+    },
+    "Lambdas -> Section - Expansion": {
+        data: {
+            lambda: {
+                __tag__: 'code',
+                bash: 'local content=$(cat); mo::parse content "$content{{planet}}$content"; echo -n "$content"'
+            },
+            planet: "Earth"
+        }
+    },
+    "Lambdas -> Section - Multiple Calls": {
+        data: {
+            lambda: {
+                __tag__: 'code',
+                bash: 'echo -n "__$(cat)__"'
+            }
+        }
+    },
+    "Partials -> Recursion": {
+        skip: "Complex objects are not supported and context is reset to the global level, so the recursion will loop forever"
+    },
+    "Sections -> Deeply Nested Contexts": {
+        skip: "Nested objects are not supported"
+    },
+    "Sections -> Dotted Names - Broken Chains": {
+        // Complex objects are not supported
+        template: `"{{#a.b}}Here{{/a.b}}" == ""`
+    },
+    "Sections -> Dotted Names - Falsey": {
+        // Complex objects are not supported
+        data: { a: { b: false } },
+        template: `"{{#a.b}}Here{{/a.b}}" == ""`
+    },
+    "Sections -> Dotted Names - Truthy": {
+        // Complex objects are not supported
+        data: { a: { b: true } },
+        template: `"{{#a.b}}Here{{/a.b}}" == "Here"`
+    },
+    "Sections -> Implicit Iterator - Array": {
+        skip: "Nested arrays are not supported"
+    },
+    "Sections -> List": {
+        // Arrays of objects are not supported
+        data: { list: [1, 2, 3] },
+        template: `"{{#list}}{{.}}{{/list}}"`
+    },
+    "Sections -> List Context": {
+        skip: "Deeply nested objects are not supported"
+    },
+    "Sections -> List Contexts": {
+        skip: "Deeply nested objects are not supported"
+    }
+};
+
+function specFileToName(file) {
+    return file
+        .replace(/.*\//, "")
+        .replace(".json", "")
+        .replace("~", "")
+        .replace(/(^|-)[a-z]/g, function (match) {
+            return match.toUpperCase();
+        });
+}
+
+function processArraySequentially(array, callback) {
+    function processCopy() {
+        if (arrayCopy.length) {
+            const item = arrayCopy.shift();
+            return Promise.resolve(item)
+                .then(callback)
+                .then((singleResult) => {
+                    result.push(singleResult);
+
+                    return processCopy();
+                });
+        } else {
+            return Promise.resolve(result);
+        }
+    }
+
+    const result = [];
+    const arrayCopy = array.slice();
+
+    return processCopy();
+}
+
+function debug(...args) {
+    if (process.env.DEBUG) {
+        console.debug(...args);
+    }
+}
+
+function makeShellString(value) {
+    if (typeof value === "boolean") {
+        return value ? '"true"' : '""';
+    }
+
+    if (typeof value === "string") {
+        // Newlines are tricky
+        return value
+            .split(/\n/)
+            .map(function (chunk) {
+                return JSON.stringify(chunk);
+            })
+            .join('"\n"');
+    }
+
+    if (typeof value === "number") {
+        return value;
+    }
+
+    return "ERR_CONVERTING";
+}
+
+function addToEnvironmentArray(name, value) {
+    const result = ["("];
+    value.forEach(function (subValue) {
+        result.push(makeShellString(subValue));
+    });
+    result.push(")");
+
+    return name + "=" + result.join(" ");
+}
+
+function addToEnvironmentObjectConvertedToAssociativeArray(name, value) {
+    const values = [];
+
+    for (const [k, v] of Object.entries(value)) {
+        if (typeof v === "object") {
+            if (v) {
+                // An object - abort
+                return `# ${name}.${k} is an object that can not be converted to an associative array`;
+            }
+
+            // null
+            values.push(`[${k}]=`);
+        } else {
+            values.push(`[${k}]=${makeShellString(v)}`);
+        }
+    }
+
+    return `declare -A ${name}\n${name}=(${values.join(" ")})`;
+}
+
+function addToEnvironmentObject(name, value) {
+    if (!value) {
+        // null
+        return `#${name} is null`;
+    }
+
+    if (value.__tag__ === "code") {
+        return `${name}() { ${value.bash || 'echo "NO BASH VERSION OF CODE"'}; }`;
+    }
+
+    return addToEnvironmentObjectConvertedToAssociativeArray(name, value);
+}
+
+function addToEnvironment(name, value) {
+    if (Array.isArray(value)) {
+        return addToEnvironmentArray(name, value);
+    }
+
+    if (typeof value === "object") {
+        return addToEnvironmentObject(name, value);
+    }
+
+    return `${name}=${makeShellString(value)}`;
+}
+
+function buildScript(test) {
+    const script = ["#!/usr/bin/env bash"];
+    Object.keys(test.data).forEach(function (name) {
+        script.push(addToEnvironment(name, test.data[name]));
+    });
+    script.push(". ./mo");
+    script.push("mo spec-runner/spec-template");
+    script.push("");
+
+    return script.join("\n");
+}
+
+function writePartials(test) {
+    return processArraySequentially(
+        Object.keys(test.partials),
+        (partialName) => {
+            debug("Writing partial:", partialName);
+
+            return fsPromises.writeFile(
+                "spec-runner/" + partialName,
+                test.partials[partialName]
+            );
+        }
+    );
+}
+
+function setupEnvironment(test) {
+    return cleanup()
+        .then(() => fsPromises.mkdir("spec-runner/"))
+        .then(() =>
+            fsPromises.writeFile("spec-runner/spec-script", test.script)
+        )
+        .then(() =>
+            fsPromises.writeFile("spec-runner/spec-template", test.template)
+        )
+        .then(() => writePartials(test));
+}
+
+function executeScript(test) {
+    return new Promise((resolve) => {
+        exec(
+            "bash spec-runner/spec-script 2>&1",
+            {
+                timeout: 2000
+            },
+            (err, stdout) => {
+                if (err) {
+                    test.scriptError = err.toString();
+                }
+
+                test.output = stdout;
+                resolve();
+            }
+        );
+    });
+}
+
+function cleanup() {
+    return fsPromises.rm("spec-runner/", { force: true, recursive: true });
+}
+
+function detectFailure(test) {
+    if (test.scriptError) {
+        return true;
+    }
+
+    if (test.output !== test.expected) {
+        return true;
+    }
+
+    return false;
+}
+
+function showFailureDetails(test) {
+    console.log(`FAILURE: ${test.fullName}`);
+    console.log("");
+    console.log(test.desc);
+    console.log("");
+    console.log(JSON.stringify(test, null, 4));
+}
+
+function applyTestOverrides(test) {
+    const overrides = testOverrides[test.fullName];
+    const originals = {};
+
+    if (!overrides) {
+        return;
+    }
+
+    for (const [key, value] of Object.entries(overrides)) {
+        originals[key] = test[key];
+        test[key] = value;
+    }
+
+    test.overridesApplied = true;
+    test.valuesBeforeOverride = originals;
+}
+
+function runTest(testSet, test) {
+    test.partials = test.partials || {};
+    test.fullName = `${testSet.name} -> ${test.name}`;
+    applyTestOverrides(test);
+    test.script = buildScript(test);
+
+    if (test.skip) {
+        debug("Skipping test:", test.fullName, `(${test.skip})`);
+
+        return Promise.resolve();
+    }
+
+    debug("Running test:", test.fullName);
+
+    return setupEnvironment(test)
+        .then(() => executeScript(test))
+        .then(cleanup)
+        .then(() => {
+            test.isFailure = detectFailure(test);
+
+            if (test.isFailure) {
+                showFailureDetails(test);
+            } else {
+                debug('Test pass:', test.fullName);
+            }
+        });
+}
+
+function processSpecFile(filename) {
+    debug("Read spec file:", filename);
+
+    return fsPromises.readFile(filename, "utf8").then((fileContents) => {
+        const testSet = JSON.parse(fileContents);
+        testSet.name = specFileToName(filename);
+
+        return processArraySequentially(testSet.tests, (test) =>
+            runTest(testSet, test)
+        ).then(() => {
+            testSet.pass = 0;
+            testSet.fail = 0;
+            testSet.skip = 0;
+            testSet.passOverride = 0;
+
+            for (const test of testSet.tests) {
+                if (test.isFailure) {
+                    testSet.fail += 1;
+                } else if (test.skip) {
+                    testSet.skip += 1;
+                } else {
+                    testSet.pass += 1;
+
+                    if (test.overridesApplied) {
+                        testSet.passOverride += 1;
+                    }
+                }
+            }
+            console.log(
+                `### ${testSet.name} Results = ${testSet.pass} passed (with ${testSet.passOverride} overridden), ${testSet.fail} failed, ${testSet.skip} skipped`
+            );
+
+            return testSet;
+        });
+    });
+}
+
+// 0 = node, 1 = script, 2 = file
+if (process.argv.length < 3) {
+    console.log("Specify one or more JSON spec files on the command line");
+    process.exit();
+}
+
+processArraySequentially(process.argv.slice(2), processSpecFile).then(
+    (result) => {
+        console.log("=========================================");
+        console.log("");
+        console.log("Failed Test Summary");
+        console.log("");
+        let pass = 0,
+            fail = 0,
+            skip = 0,
+            total = 0,
+            passOverride = 0;
+
+        for (const testSet of result) {
+            pass += testSet.pass;
+            fail += testSet.fail;
+            skip += testSet.skip;
+            total += testSet.tests.length;
+            passOverride += testSet.passOverride;
+
+            console.log(
+                `* ${testSet.name}: ${testSet.tests.length} total, ${testSet.pass} pass (with ${passOverride} overridden), ${testSet.fail} fail, ${testSet.skip} skip`
+            );
+
+            for (const test of testSet.tests) {
+                if (test.isFailure) {
+                    console.log(`    * Failure: ${test.name}`);
+                }
+            }
+        }
+
+        console.log("");
+        console.log(
+            `Final result: ${total} total, ${pass} pass (with ${passOverride} overridden), ${fail} fail, ${skip} skip`
+        );
+
+        if (fail) {
+            process.exit(1);
+        }
+    },
+    (err) => {
+        console.error(err);
+        console.error("FAILURE RUNNING SCRIPT");
+        console.error("Testing artifacts are left in script-runner/ folder");
+    }
+);

vendor/git.knownelement.com/ExternalVendorCode/mo/run-tests

@@ -0,0 +1,162 @@
+#!/usr/bin/env bash
+#
+# Run one or more tests.
+#
+# Command-line usage to run all tests.
+#
+#     ./run-tests
+#
+# To run only one test, run "tests/test-name".
+#
+# Usage within a test as a template. Source run-tests to get functions, export
+# any necessary variables, then call runTest.
+#
+#     #!/usr/bin/env bash
+#     cd "${0%/*}" || exit 1
+#     . ../run-tests
+#
+#     export template="This is a template"
+#     export expected="This is a template"
+#     runTest
+#
+# When used within the test, you control various aspects with environment
+# variables or functions.
+#
+# - The content passed into mo is either the variable "$template" or the output
+#   of the function called template.
+# - The expected result is either "$expected" or the function called expected.
+# - The expected return code is "$returnCode" and defaults to 0.
+# - The arguments to pass to mo is the array "${arguments[@]}" and defaults to ().
+#
+# When $MO_DEBUG is set to a non-empty value, the test does not run, but mo is
+# simply executed directly. This allows for calling mo in the same manner as
+# the test but does not buffer output nor expect the output to match the
+# expected.
+#
+# When $MO_DEBUG_TEST is set to a non-empty value, the expected and actual
+# results are shown using "declare -p" to provide an easier time seeing the
+# differences, especially with whitespace.
+
+testCase() {
+    echo "Input: $1"
+    echo "Expected: $2"
+}
+
+indirect() {
+    unset -v "$1"
+    printf -v "$1" '%s' "$2"
+}
+
+getValue() {
+    local name temp len hardSpace
+
+    name=$2
+    hardSpace=" "
+
+    if declare -f "$name" &> /dev/null; then
+        temp=$("$name"; echo -n "$hardSpace")
+        len=$((${#temp} - 1))
+
+        if [[ "${temp:$len}" == "$hardSpace" ]]; then
+            temp=${temp:0:$len}
+        fi
+    else
+        temp=${!name}
+    fi
+
+    local "$1" && indirect "$1" "$temp"
+}
+
+runTest() (
+    local testTemplate testExpected testActual hardSpace len testReturnCode testFail
+
+    hardSpace=" "
+    . ../mo
+
+    getValue testTemplate template
+    getValue testExpected expected
+
+    if [[ -n "${MO_DEBUG:-}" ]]; then
+        echo -n "$testTemplate" | mo ${arguments[@]+"${arguments[@]}"} 2>&1
+
+        return $?
+    fi
+
+    testActual=$(echo -n "$testTemplate" | mo ${arguments[@]+"${arguments[@]}"} 2>&1; echo -n "$hardSpace$?")
+    testReturnCode=${testActual##*$hardSpace}
+    testActual=${testActual%$hardSpace*}
+    testFail=false
+
+    if [[ "$testActual" != "$testExpected" ]]; then
+        echo "Failure"
+        echo "Expected:"
+        echo "$testExpected"
+        echo "Actual:"
+        echo "$testActual"
+
+        if [[ -n "${MO_DEBUG_TEST-}" ]]; then
+            declare -p testExpected
+            # Align the two declare outputs
+            echo -n "  "
+            declare -p testActual
+        fi
+
+        testFail=true
+    fi
+
+    if [[ "$testReturnCode" != "$returnCode" ]]; then
+        echo "Expected return code $returnCode, but got $testReturnCode"
+        testFail=true
+    fi
+
+    if [[ "$testFail" == "true" ]]; then
+        return 1
+    fi
+
+    return 0
+)
+
+runTestFile() (
+    local file=$1
+
+    echo "Test: $file"
+    "$file"
+)
+
+runTests() (
+    PASS=0
+    FAIL=0
+
+    if [[ $# -gt 0 ]]; then
+        for TEST in "$@"; do
+            runTestFile "$TEST" && PASS=$((PASS + 1)) || FAIL=$((FAIL + 1))
+        done
+    else
+        cd "${0%/*}"
+        for TEST in tests/*; do
+            if [[ -f "$TEST" ]]; then
+                runTestFile "$TEST" && PASS=$((PASS + 1)) || FAIL=$((FAIL + 1))
+            fi
+        done
+    fi
+
+    echo ""
+    echo "Pass: $PASS"
+    echo "Fail: $FAIL"
+
+    if [[ $FAIL -gt 0 ]]; then
+        exit 1
+    fi
+)
+
+# Clear test related variables
+template="Template not defined"
+expected="Expected not defined"
+returnCode=0
+arguments=()
+
+# If sourced, load functions.
+# If executed, perform the actions as expected.
+if [[ "$0" == "${BASH_SOURCE[0]}" ]] || [[ -z "${BASH_SOURCE[0]}" ]]; then
+    runTests ${@+"${@}"}
+fi

vendor/git.knownelement.com/ExternalVendorCode/mo/tests/ampersand

@@ -0,0 +1,9 @@
+#!/usr/bin/env bash
+cd "${0%/*}" || exit 1
+. ../run-tests
+
+export thing="Works"
+export template="{{&thing}}"
+export expected="Works"
+
+runTest

vendor/git.knownelement.com/ExternalVendorCode/mo/tests/array

@@ -0,0 +1,21 @@
+#!/usr/bin/env bash
+cd "${0%/*}" || exit 1
+. ../run-tests
+
+export repo=( "resque" "hub" "rip" )
+template() {
+    cat <<EOF
+{{#repo}}
+  <b>{{@key}} - {{.}}</b>
+{{/repo}}
+EOF
+}
+expected() {
+    cat <<EOF
+  <b>0 - resque</b>
+  <b>1 - hub</b>
+  <b>2 - rip</b>
+EOF
+}
+
+runTest

vendor/git.knownelement.com/ExternalVendorCode/mo/tests/assoc-array

@@ -0,0 +1,25 @@
+#!/usr/bin/env bash
+cd "${0%/*}" || exit 1
+. ../run-tests
+
+declare -A repo
+# The order of the array elements can be shuffled depending on the version of
+# Bash. Keeping this to a minimal set and alphabetized seems to help.
+repo[hub]="Hub"
+repo[rip]="Rip"
+export repo
+template() {
+    cat <<EOF
+{{#repo}}
+  <b>{{@key}} - {{.}}</b>
+{{/repo}}
+EOF
+}
+expected() {
+    cat <<EOF
+  <b>hub - Hub</b>
+  <b>rip - Rip</b>
+EOF
+}
+
+runTest

vendor/git.knownelement.com/ExternalVendorCode/mo/tests/comment

@@ -0,0 +1,8 @@
+#!/usr/bin/env bash
+cd "${0%/*}" || exit 1
+. ../run-tests
+
+export template="Wor{{!comment}}ks"
+export expected="Works"
+
+runTest

vendor/git.knownelement.com/ExternalVendorCode/mo/tests/comment-newline

@@ -0,0 +1,15 @@
+#!/usr/bin/env bash
+cd "${0%/*}" || exit 1
+. ../run-tests
+
+template() {
+    cat <<EOF
+<h1>Today{{! ignore me
+and this can
+run through multiple
+lines}}.</h1>
+EOF
+}
+export expected=$'<h1>Today.</h1>\n'
+
+runTest

vendor/git.knownelement.com/ExternalVendorCode/mo/tests/comment-with-spaces

@@ -0,0 +1,8 @@
+#!/usr/bin/env bash
+cd "${0%/*}" || exit 1
+. ../run-tests
+
+export template="Wor{{! comment }}ks"
+export expected="Works"
+
+runTest

vendor/git.knownelement.com/ExternalVendorCode/mo/tests/concatenated-variables

@@ -0,0 +1,10 @@
+#!/usr/bin/env bash
+cd "${0%/*}" || exit 1
+. ../run-tests
+
+export thing="Wor"
+export thing2="ks"
+export template="{{thing thing2}}"
+export expected="Works"
+
+runTest

vendor/git.knownelement.com/ExternalVendorCode/mo/tests/delimiters

@@ -0,0 +1,9 @@
+#!/usr/bin/env bash
+cd "${0%/*}" || exit 1
+. ../run-tests
+
+export thing="Works"
+export template="{{=| |=}}|thing|"
+export expected="Works"
+
+runTest

vendor/git.knownelement.com/ExternalVendorCode/mo/tests/double-hyphen

@@ -0,0 +1,10 @@
+#!/usr/bin/env bash
+cd "${0%/*}" || exit 1
+. ../run-tests
+
+export arguments=(--fail-on-file -- --help)
+export returnCode=1
+export template=""
+export expected=$'ERROR: No such file: --help\n'
+
+runTest

vendor/git.knownelement.com/ExternalVendorCode/mo/tests/double-quote

@@ -0,0 +1,8 @@
+#!/usr/bin/env bash
+cd "${0%/*}" || exit 1
+. ../run-tests
+
+export template='{{"Works"}}'
+export expected="Works"
+
+runTest

vendor/git.knownelement.com/ExternalVendorCode/mo/tests/fail-not-set

@@ -0,0 +1,20 @@
+#!/usr/bin/env bash
+cd "${0%/*}" || exit 1
+. ../run-tests
+
+unset __NO_SUCH_VAR
+export POPULATED="words"
+export EMPTY=""
+export arguments=(--fail-not-set)
+export returnCode=1
+
+template() {
+    cat <<EOF
+Populated: {{POPULATED}};
+Empty: {{EMPTY}};
+Unset: {{__NO_SUCH_VAR}};
+EOF
+}
+export expected=$'ERROR: Environment variable not set: __NO_SUCH_VAR\n'
+
+runTest

vendor/git.knownelement.com/ExternalVendorCode/mo/tests/fail-on-function

@@ -0,0 +1,13 @@
+#!/usr/bin/env bash
+cd "${0%/*}" || exit 1
+. ../run-tests
+
+failFunction() {
+    false
+}
+export arguments=(--fail-on-function)
+export returnCode=1
+export template="Fail on function? {{failFunction}}"
+export expected=$'ERROR: Function failed with status code 1: "failFunction"\n'
+
+runTest

vendor/git.knownelement.com/ExternalVendorCode/mo/tests/false-is-empty-arg

@@ -0,0 +1,18 @@
+#!/usr/bin/env bash
+cd "${0%/*}" || exit 1
+. ../run-tests
+
+export USER=j.doe
+export ADMIN=false
+export arguments=(--false)
+template() {
+    cat <<EOF
+The user {{USER}} exists.
+{{#ADMIN}}
+WRONG - should not be an admin.
+{{/ADMIN}}
+EOF
+}
+export expected=$'The user j.doe exists.\n'
+
+runTest

vendor/git.knownelement.com/ExternalVendorCode/mo/tests/false-is-empty-env

@@ -0,0 +1,18 @@
+#!/usr/bin/env bash
+cd "${0%/*}" || exit 1
+. ../run-tests
+
+export USER=j.doe
+export ADMIN=false
+MO_FALSE_IS_EMPTY=yeppers
+template() {
+    cat <<EOF
+The user {{USER}} exists.
+{{#ADMIN}}
+WRONG - should not be an admin.
+{{/ADMIN}}
+EOF
+}
+export expected=$'The user j.doe exists.\n'
+
+runTest

vendor/git.knownelement.com/ExternalVendorCode/mo/tests/false-list

@@ -0,0 +1,16 @@
+#!/usr/bin/env bash
+cd "${0%/*}" || exit 1
+. ../run-tests
+
+export person=""
+template() {
+    cat <<EOF
+Shown.
+{{#person}}
+  Never shown!
+{{/person}}
+EOF
+}
+export expected=$'Shown.\n'
+
+runTest

vendor/git.knownelement.com/ExternalVendorCode/mo/tests/fixtures/indented-partials.partial

@@ -0,0 +1,2 @@
+first line
+second line

vendor/git.knownelement.com/ExternalVendorCode/mo/tests/fixtures/inline-indentation

@@ -0,0 +1,2 @@
+>
+>

vendor/git.knownelement.com/ExternalVendorCode/mo/tests/fixtures/multi-line-partial.partial

@@ -0,0 +1 @@
+{{multilineData}}

vendor/git.knownelement.com/ExternalVendorCode/mo/tests/fixtures/partial.partial

@@ -0,0 +1 @@
+<strong>{{.}}</strong>

vendor/git.knownelement.com/ExternalVendorCode/mo/tests/fixtures/source-multiple-1.vars

@@ -0,0 +1,2 @@
+export A=from1
+export B=from1

vendor/git.knownelement.com/ExternalVendorCode/mo/tests/fixtures/source-multiple-2.vars

@@ -0,0 +1,2 @@
+export B=from2
+export C=from2

vendor/git.knownelement.com/ExternalVendorCode/mo/tests/fixtures/source.vars

@@ -0,0 +1,5 @@
+export VAR=value
+export ARR=(1 2 3)
+declare -A ASSOC_ARR
+# Can not export associative arrays, otherwise they turn into indexed arrays
+ASSOC_ARR=([a]=AAA [b]=BBB)

vendor/git.knownelement.com/ExternalVendorCode/mo/tests/fixtures/standalone-indentation.partial

@@ -0,0 +1,3 @@
+|
+{{content}}
+|