moving toward proper vendoring

ca77429 fantastic. a great day of coding and learning!
6a43a11 .
d53b71d removed debugging bits
7f0a8a3 and now with a properly templatized candidate info sheet
77a9156 .
3da01fd Add "markdown-resume" from "https://git.knownelement.com/ExternalVendorCode/markdown-resume@master"
ca8e16b Squashed 'vendor/git.knownelement.com/ExternalVendorCode/markdown-resume/' content from commit 7a8fdff
4673128 proper docs even.

git-subtree-dir: vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline
git-subtree-split: ca77429b0f3b2fe3e2e612b337ac5ae83cbcc3e0

README.md

@@ -1,3 +1,7 @@
 # MarkdownResume-ReachableCEO
 
-An example implementation of the MarkdownResume pipeline with the @ReachableCEO production resume. 
+An example implementation of the MarkdownResume pipeline with the @ReachableCEO production resume.
+
+See [upstream repo](https://git.knownelement.com/reachableceo/MarkdownResume-Pipeline) for the build scripts/templates
+
+See this directory: ./vendor/git.knownelement.com/reachableceo/MarkdownResume/ for my production resume that has the pipeline vendored in.

local/Templates/JobHistoryDetails/3M.md

@@ -0,0 +1,4 @@
+- Supported Vendavo on RedHat Linux, managed releases, and provided day-to-day developer support.
+- Created a homegrown YAML configuration management system, utilizing bash scripting and YAML templates with a CSV-based key/value store to efficiently manage and regenerate environment-specific variables for a line-of-business application across multiple development, testing, staging, and production environments.
+
+\pagebreak

local/Templates/JobHistoryDetails/Apple Computer.md

@@ -0,0 +1 @@
+- Day to day server operations scheduling downtime etc

local/Templates/JobHistoryDetails/CDK Global.md

@@ -0,0 +1,2 @@
+- Security Compliance : worked with risk management/audit to remediate insecure configurations
+- Created Alma9 Packer image from scratch

local/Templates/JobHistoryDetails/Electronic Clearing House.md

@@ -0,0 +1,4 @@
+- Linux systems engineer in a 24x7 transaction processing/ecommerce/flnancial services environment, collaborating with network administration and infrastructure design teams.
+ - Ensured continuous uptime for high-impact environments, including a 1TB MySQL database, 300TB Oracle database, 1.5TB Oracle Data Warehouse, and a 4,000-store LAMP-based ecommerce system (MerchantAmerica.com).
+ - Successfully deployed an enterprise-wide Linux backup system, featuring encrypted backups stored on a central server with ISCSI attached network storage, utilizing GNUPG and tar over SSH. Regular backups and restores were tested weekly.
+ - Led the deployment of Oracle database infrastructure, implementing two Oracle RAC clusters with Dell 6850 servers, Qual Dual Core Xeon processors, and 32GB of RAM each. The clusters ran on RedHat Enterprise Linux 4.0 64bit edition, serving Data Warehouse, Transaction Processing Software, and Credit Card Clearing applications.

local/Templates/JobHistoryDetails/GSI Commerce.md

@@ -0,0 +1,3 @@
+- Contributed to disaster recovery from an Informix Database failure.
+- Streamlined FTP server conflguration and deployed open-source remote control software.
+-  Upgraded network infrastructure from hubs to managed switches.

local/Templates/JobHistoryDetails/HostGator.com.md

@@ -0,0 +1,2 @@
+- Provided senior-level Linux and web application support globally.
+- Developed standardized reply language and scripts, reducing errors in Level I Linux administrator department.

local/Templates/JobHistoryDetails/ReachableCEO Enterprises.md

@@ -0,0 +1,6 @@
+- Deployed,configured,supported Cloudron and Coolify PAAS and a full IT/SRE/Devops and engineering software stack for a stealth aerospace startup. 
+- Provided technician support to a team of electrical engineers building the power system for the radar of FrakenSAM in Ukraine. Handled high / low voltage wiring and plumbing and documentation of those systems. 
+- Provided root cause analysis and remediation for a security breach at a defense contractor.
+- Developed a rapidly field deployable mesh networking system for a variety of use cases.
+- Developed a secure global video conferencing system using only 3mbps for a major defense contractor.
+- Advised on backend infrastructure for broadcasting news and information via radio and internet into hostile powers. 

local/Templates/JobHistoryDetails/RippleTV.md

@@ -0,0 +1,2 @@
+- Provided system engineering expertise for customer-facing advertising platform (AdSpot) and internal fleet management tool (CPanel).
+- Utilized Nginx, Mongrel, Thin, Rails, Merb, Rack, MySQL, memcached, and F5 LTM.

local/Templates/JobHistoryDetails/SHEIN.md

@@ -0,0 +1,5 @@
+- Streamlined engineer onboarding by documenting and overhauling the process, consolidating disparate guides into a comprehensive modular set of documents.
+- Established a taxonomy for team documentation in the wiki, implementing Confluence best practices for a proper knowledge base.
+- Served as the SRE Liaison for cybersecurity functions, ensuring compliance with data locality/partition requirements and pending federal data privacy legislation.
+- Focused on fostering a culture of automation and skill development within the SRE team, emphasizing code review, infrastructure as code, versioning, testing, and effective ticket management.
+- Contributed to Linux server administration both internally and externally, aiding colleagues with scripting/automation and assisting in the migration from AWS to Azure with zero customer-facing system impact. Additionally, provided day-to-day support for AWS and Azure activities and troubleshooting.

local/Templates/JobHistoryDetails/TippingPoint.md

@@ -0,0 +1,5 @@
+- Conducted code and design reviews for internal/external team projects and actively participated in broad enterprise collaboration, focusing on large-scale fleet management.
+- Managed user account administration, manual/semi-automated server provisioning, trouble tickets, security vulnerability remediation, and system/network auditing.
+- Led various projects, including migrating fleet systems from Centos 6 to Centos 7, implementing LXC/ LXD container versions for increased system utilization, and creating an on-premise deployment system (GUMPS) for automated provisioning.
+- Deployed network monitoring systems (Zenoss, observium/librenms), utilized librenms as a Conflguration Management Database (CMDB), and implemented a fleet orchestration system (Rundeck).
+- Executed extensive vulnerability remediation, OS/application/kernel patching, NIC customization/ optimization, and data migrations while developing and maintaining custom scripts for tasks such as LDAP management and SSL scenarios. Automated processes like re-imaging and ensured continuous distribution of a 40GB dataset of packet captures across a global fleet.

local/Templates/JobHistoryDetails/Walt Disney Internet Group.md

@@ -0,0 +1,9 @@
+-  Engaged in dynamic work environment focusing on popular web/ecommerce sites, including disneyworld.com and disneyland.com.
+- Provided design, architecture, and day-to-day administration for Disney park property sites generating $2 billion annually.
+- Provided system engineering and PCI compliance expertise for Disneyland.com, Disneyworld.com, DisneyCruiseLines.com, and 23 related properties.
+- Utilized Jboss instances on RHEL3/4 for business logic and employed Windows 2003 with Tomcat/IIS for frontend application serving.
+- Automated routine system administration tasks through the creation of batch and VBScript programs for Windows administration.
+- Led an Active Directory project for WDIG, designing and implementing a nationwide, highly available system across 3 data centers.
+- Managed the migration from Windows NT to Windows 2003 Active Directory domain controllers, including experience with Windows 2008, Centrify, and Samba/Winbind/LDAP/Kerberos.
+
+\pagebreak

local/Templates/SkillsAndProjects/Projects.md

@@ -0,0 +1,11 @@
+- Developed and implemented a process to switch thousands of desktops providing digital signage functionality from Fedora to Debian in a completely automated fashion using a custom initrd.
+- Developed and implemented an internal private cloud orchestration and provisioning system for a hardware development engineering team that handled the entire provisioning lifecycle for physical and virtual systems.
+- Developed and implemented standardized language and procedures and incident investigation automation for a large technical support organization with high turnover.
+- Developed and implemented an automated order status and payment handling interactive voice response application using Angel.ccm with a backend web service returning Voice XML. This allows call center personnel to focus on revenue generating opportunities instead of administrative matters.
+- Provided technician support to a team of electrical engineers building the power system for the radar of FrankenSAM in Ukraine. Handled high / low voltage wiring and plumbing and documentation of those systems.
+- Provided root cause analysis , mitigation and remediation of security breaches by advanced persistent threat actors at high value targets.
+- Project managed a successful brand new data center build from bare dirt to serving content in 86 days. Oversaw 8 billion dollars of capital deployment.
+- Led and consulted tier 1 payment compliance industry (PCI) implementations for some of the worlds largest brands (including at a payment processor).
+- Rolled out centralized Active Directory authentication, deployed Dell OpenManage, and upgraded network equipment.
+- Deployed password vault, Active Directory PKI, and implemented a ground-up network redesign.
+- Designed VmWare NSX network.

local/Templates/SkillsAndProjects/Skills.csv

@@ -0,0 +1,20 @@
+Linux|22 years|RHEL,Debian,Ubuntu,kickstart,PXE,  LDAP,SSSD,RPM/Deb package creation,  quotas,extended permissions, clustering,NFS,Samba
+Unix|5 years|HPUX/Solaris
+Windows|22 years|Server (2008  2016),Windows client automated deployment (7,8,10,11),Active Directory,Group Policy,WSUS,Certificate Services,AD DNS,AD DHCP,complex multiple forest and domain setups 
+Free/Libre/Open Source software|22 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
+Databases|22 years| MySQL,PostgreSQL,  Dbeaver,PHPMyAdmin,PostGIS
+Cyber Security|22 years|PCI Compliance (tier 1 implementations),OpenVAS<,Lynis,security hardening,audits,breach response and mitigation, patch and vulnerability management. AppArmor, SeLinux, Centrify, Tripwire, Integrit, OSSEC 
+Virtualization|22 years|VmWare,Parallels,HyperV,KVM,Xen
+Networking|22 years|Linux Virtual Server(LVS),HAProxy,Ubiquiti Unifi,Opnsense,Pfsense,DNS,DHCP,IPAM,PXE,IPS,IDS,GRE,IPSEC.Wireguard,OpenVPN,Nebula,Tailscale,RADIUS. Mostly layer2 data center/campus/access some WAN,firewall,layer3 
+Monitoring|22 years|Uptime Kuma,Librenms,Zabbix,Zenoss,Nagios,Elasticsearch,Logstash,Kibana(ELK)
+Storage|22 years|Netapp,EMC,EqualLogic,3par,MSA,TrueNAS/ZFS,iscsi,S3,Azure Storage
+Cloud|5 years|AWS,Azure,Kubernetes,Helm,Docker
+Containerization|15 years|LXC,Docker,OpenVZ
+Configuration management/InfrastructureAsCode(IAC)|22 years|FetchApply,Terraform/OpenTOfU,Ansible,AWX,Hashicorp Packer/Vault
+Ticket / incident / project management| 22 years| Jira,ServiceNow,Redmine,RT
+Git|15 years|Branching,merging,multiple teams,external vendors,submodules 
+SRE|5 years| Grafana,Prometheus,Signoz,Wazuh
+LLM|2 years|OpenWebUI,QA/validation,RAG,data cleaning/prep
+Programming|5 years|J2ME,PHP,Ruby,TCL/TK,Java,C,C++
+Automation|22 years|Bash,YAML,TOML,PowerShell,Perl
+Embedded development|5 years|Raspberry pi,arduino,seeduino,Lego Mindstorms

local/Templates/WorkHistory/WorkHistory.csv

@@ -0,0 +1,11 @@
+CDK Global,Senior System Engineer,July 2024 - October 2024
+Apple Computer,Senior System Administrator,March 2024 - July 2024
+SHEIN,Staff Site Reliability Engineer,December 2022 - August 2023
+3M,Senior Site Reliability Engineer,March 2020 - November 2022
+TippingPoint,Staff System Architect,March 2012 - June 2019
+HostGator.com,Automation and Escalation Engineer,March 2011 - May 2012
+RippleTV,System Engineer,October 2008 - January 2010
+Walt Disney Internet Group,Site Reliability Engineer,August 2006 - September 2007
+Electronic Clearing House,Senior System Administrator,April 2005 - July 2006
+GSI Commerce,System Administrator,March 2002 -  February 2005
+ReachableCEO Enterprises,Freelancer,January 2001 - December 2024

local/build-temp/CandidateInfoSheet.yml

@@ -0,0 +1,14 @@
+title: "Charles N Wyble Candidate Information Sheet"
+titlepage: true
+titlepage-logo: "D:\tsys\@ReachableCEO\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: "Tenacity. Velocity. Focus."
+footer-right: "[Source code](https://git.knownelement.com/reachableceo/MarkdownResume-Pipeline)"
+urlcolor: blue
+page-background: "../vendor/git.knownelement.com/ExternalVendorCode/pandoc-latex-template/examples/page-background/backgrounds/background3.pdf"

local/build-temp/ClientSubmission.yml

@@ -0,0 +1,7 @@
+title: "Charles N Wyble Resume"
+header-left: "\\hspace{1cm}"
+header-center: "\\leftmark"
+header-right: "Page \\thepage"
+footer-left: "Charles N Wyble"
+urlcolor: blue
+page-background: "../vendor/git.knownelement.com/ExternalVendorCode/pandoc-latex-template/examples/page-background/backgrounds/background3.pdf"

local/build-temp/ClientSubmit-Resume.md

@@ -0,0 +1,117 @@
+ 
+## Career Highlights
+- Developed and implemented a process to switch thousands of desktops providing digital signage functionality from Fedora to Debian in a completely automated fashion using a custom initrd.
+- Developed and implemented an internal private cloud orchestration and provisioning system for a hardware development engineering team that handled the entire provisioning lifecycle for physical and virtual systems.
+- Developed and implemented standardized language and procedures and incident investigation automation for a large technical support organization with high turnover.
+- Developed and implemented an automated order status and payment handling interactive voice response application using Angel.ccm with a backend web service returning Voice XML. This allows call center personnel to focus on revenue generating opportunities instead of administrative matters.
+- Provided technician support to a team of electrical engineers building the power system for the radar of FrankenSAM in Ukraine. Handled high / low voltage wiring and plumbing and documentation of those systems.
+- Provided root cause analysis , mitigation and remediation of security breaches by advanced persistent threat actors at high value targets.
+- Project managed a successful brand new data center build from bare dirt to serving content in 86 days. Oversaw 8 billion dollars of capital deployment.
+- Led and consulted tier 1 payment compliance industry (PCI) implementations for some of the worlds largest brands (including at a payment processor).
+- Rolled out centralized Active Directory authentication, deployed Dell OpenManage, and upgraded network equipment.
+- Deployed password vault, Active Directory PKI, and implemented a ground-up network redesign.
+- Designed VmWare NSX network.
+\pagebreak
+ 
+## Employment History
+ 
+**CDK Global | Senior System Engineer | July 2024 - October 2024**
+ 
+- Security Compliance : worked with risk management/audit to remediate insecure configurations
+- Created Alma9 Packer image from scratch
+ 
+**Apple Computer | Senior System Administrator | March 2024 - July 2024**
+ 
+- Day to day server operations scheduling downtime etc
+ 
+**SHEIN | Staff Site Reliability Engineer | December 2022 - August 2023**
+ 
+- Streamlined engineer onboarding by documenting and overhauling the process, consolidating disparate guides into a comprehensive modular set of documents.
+- Established a taxonomy for team documentation in the wiki, implementing Confluence best practices for a proper knowledge base.
+- Served as the SRE Liaison for cybersecurity functions, ensuring compliance with data locality/partition requirements and pending federal data privacy legislation.
+- Focused on fostering a culture of automation and skill development within the SRE team, emphasizing code review, infrastructure as code, versioning, testing, and effective ticket management.
+- Contributed to Linux server administration both internally and externally, aiding colleagues with scripting/automation and assisting in the migration from AWS to Azure with zero customer-facing system impact. Additionally, provided day-to-day support for AWS and Azure activities and troubleshooting.
+ 
+**3M | Senior Site Reliability Engineer | March 2020 - November 2022**
+ 
+- Supported Vendavo on RedHat Linux, managed releases, and provided day-to-day developer support.
+- Created a homegrown YAML configuration management system, utilizing bash scripting and YAML templates with a CSV-based key/value store to efficiently manage and regenerate environment-specific variables for a line-of-business application across multiple development, testing, staging, and production environments.
+
+\pagebreak 
+**TippingPoint | Staff System Architect | March 2012 - June 2019**
+ 
+- Conducted code and design reviews for internal/external team projects and actively participated in broad enterprise collaboration, focusing on large-scale fleet management.
+- Managed user account administration, manual/semi-automated server provisioning, trouble tickets, security vulnerability remediation, and system/network auditing.
+- Led various projects, including migrating fleet systems from Centos 6 to Centos 7, implementing LXC/ LXD container versions for increased system utilization, and creating an on-premise deployment system (GUMPS) for automated provisioning.
+- Deployed network monitoring systems (Zenoss, observium/librenms), utilized librenms as a Conflguration Management Database (CMDB), and implemented a fleet orchestration system (Rundeck).
+- Executed extensive vulnerability remediation, OS/application/kernel patching, NIC customization/ optimization, and data migrations while developing and maintaining custom scripts for tasks such as LDAP management and SSL scenarios. Automated processes like re-imaging and ensured continuous distribution of a 40GB dataset of packet captures across a global fleet.
+ 
+**HostGator.com | Automation and Escalation Engineer | March 2011 - May 2012**
+ 
+- Provided senior-level Linux and web application support globally.
+- Developed standardized reply language and scripts, reducing errors in Level I Linux administrator department.
+ 
+**RippleTV | System Engineer | October 2008 - January 2010**
+ 
+- Provided system engineering expertise for customer-facing advertising platform (AdSpot) and internal fleet management tool (CPanel).
+- Utilized Nginx, Mongrel, Thin, Rails, Merb, Rack, MySQL, memcached, and F5 LTM.
+ 
+**Walt Disney Internet Group | Site Reliability Engineer | August 2006 - September 2007**
+ 
+-  Engaged in dynamic work environment focusing on popular web/ecommerce sites, including disneyworld.com and disneyland.com.
+- Provided design, architecture, and day-to-day administration for Disney park property sites generating $2 billion annually.
+- Provided system engineering and PCI compliance expertise for Disneyland.com, Disneyworld.com, DisneyCruiseLines.com, and 23 related properties.
+- Utilized Jboss instances on RHEL3/4 for business logic and employed Windows 2003 with Tomcat/IIS for frontend application serving.
+- Automated routine system administration tasks through the creation of batch and VBScript programs for Windows administration.
+- Led an Active Directory project for WDIG, designing and implementing a nationwide, highly available system across 3 data centers.
+- Managed the migration from Windows NT to Windows 2003 Active Directory domain controllers, including experience with Windows 2008, Centrify, and Samba/Winbind/LDAP/Kerberos.
+
+\pagebreak 
+**Electronic Clearing House | Senior System Administrator | April 2005 - July 2006**
+ 
+- Linux systems engineer in a 24x7 transaction processing/ecommerce/flnancial services environment, collaborating with network administration and infrastructure design teams.
+ - Ensured continuous uptime for high-impact environments, including a 1TB MySQL database, 300TB Oracle database, 1.5TB Oracle Data Warehouse, and a 4,000-store LAMP-based ecommerce system (MerchantAmerica.com).
+ - Successfully deployed an enterprise-wide Linux backup system, featuring encrypted backups stored on a central server with ISCSI attached network storage, utilizing GNUPG and tar over SSH. Regular backups and restores were tested weekly.
+ - Led the deployment of Oracle database infrastructure, implementing two Oracle RAC clusters with Dell 6850 servers, Qual Dual Core Xeon processors, and 32GB of RAM each. The clusters ran on RedHat Enterprise Linux 4.0 64bit edition, serving Data Warehouse, Transaction Processing Software, and Credit Card Clearing applications.
+ 
+**GSI Commerce | System Administrator | March 2002 -  February 2005**
+ 
+- Contributed to disaster recovery from an Informix Database failure.
+- Streamlined FTP server conflguration and deployed open-source remote control software.
+-  Upgraded network infrastructure from hubs to managed switches.
+ 
+**ReachableCEO Enterprises | Freelancer | January 2001 - December 2024**
+ 
+- Deployed,configured,supported Cloudron and Coolify PAAS and a full IT/SRE/Devops and engineering software stack for a stealth aerospace startup. 
+- Provided technician support to a team of electrical engineers building the power system for the radar of FrakenSAM in Ukraine. Handled high / low voltage wiring and plumbing and documentation of those systems. 
+- Provided root cause analysis and remediation for a security breach at a defense contractor.
+- Developed a rapidly field deployable mesh networking system for a variety of use cases.
+- Developed a secure global video conferencing system using only 3mbps for a major defense contractor.
+- Advised on backend infrastructure for broadcasting news and information via radio and internet into hostile powers. 
+ 
+\pagebreak
+ 
+## Skills
+ 
+|Skill|Experience|Skill Details|
+|---|---|---|
+|**Linux**|22 years|RHEL,Debian,Ubuntu,kickstart,PXE,  LDAP,SSSD,RPM/Deb package creation,  quotas,extended permissions, clustering,NFS,Samba|
+|**Unix**|5 years|HPUX/Solaris|
+|**Windows**|22 years|Server (2008  2016),Windows client automated deployment (7,8,10,11),Active Directory,Group Policy,WSUS,Certificate Services,AD DNS,AD DHCP,complex multiple forest and domain setups |
+|**Free/Libre/Open Source software**|22 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|
+|**Databases**|22 years| MySQL,PostgreSQL,  Dbeaver,PHPMyAdmin,PostGIS|
+|**Cyber Security**|22 years|PCI Compliance (tier 1 implementations),OpenVAS<,Lynis,security hardening,audits,breach response and mitigation, patch and vulnerability management. AppArmor, SeLinux, Centrify, Tripwire, Integrit, OSSEC |
+|**Virtualization**|22 years|VmWare,Parallels,HyperV,KVM,Xen|
+|**Networking**|22 years|Linux Virtual Server(LVS),HAProxy,Ubiquiti Unifi,Opnsense,Pfsense,DNS,DHCP,IPAM,PXE,IPS,IDS,GRE,IPSEC.Wireguard,OpenVPN,Nebula,Tailscale,RADIUS. Mostly layer2 data center/campus/access some WAN,firewall,layer3 |
+|**Monitoring**|22 years|Uptime Kuma,Librenms,Zabbix,Zenoss,Nagios,Elasticsearch,Logstash,Kibana(ELK)|
+|**Storage**|22 years|Netapp,EMC,EqualLogic,3par,MSA,TrueNAS/ZFS,iscsi,S3,Azure Storage|
+|**Cloud**|5 years|AWS,Azure,Kubernetes,Helm,Docker|
+|**Containerization**|15 years|LXC,Docker,OpenVZ|
+|**Configuration management/InfrastructureAsCode(IAC)**|22 years|FetchApply,Terraform/OpenTOfU,Ansible,AWX,Hashicorp Packer/Vault|
+|**Ticket / incident / project management**| 22 years| Jira,ServiceNow,Redmine,RT|
+|**Git**|15 years|Branching,merging,multiple teams,external vendors,submodules |
+|**SRE**|5 years| Grafana,Prometheus,Signoz,Wazuh|
+|**LLM**|2 years|OpenWebUI,QA/validation,RAG,data cleaning/prep|
+|**Programming**|5 years|J2ME,PHP,Ruby,TCL/TK,Java,C,C++|
+|**Automation**|22 years|Bash,YAML,TOML,PowerShell,Perl|
+|**Embedded development**|5 years|Raspberry pi,arduino,seeduino,Lego Mindstorms|

local/build-temp/JobBoard-Resume.md

@@ -0,0 +1,139 @@
+ 
+## Career Highlights
+- Developed and implemented a process to switch thousands of desktops providing digital signage functionality from Fedora to Debian in a completely automated fashion using a custom initrd.
+- Developed and implemented an internal private cloud orchestration and provisioning system for a hardware development engineering team that handled the entire provisioning lifecycle for physical and virtual systems.
+- Developed and implemented standardized language and procedures and incident investigation automation for a large technical support organization with high turnover.
+- Developed and implemented an automated order status and payment handling interactive voice response application using Angel.ccm with a backend web service returning Voice XML. This allows call center personnel to focus on revenue generating opportunities instead of administrative matters.
+- Provided technician support to a team of electrical engineers building the power system for the radar of FrankenSAM in Ukraine. Handled high / low voltage wiring and plumbing and documentation of those systems.
+- Provided root cause analysis , mitigation and remediation of security breaches by advanced persistent threat actors at high value targets.
+- Project managed a successful brand new data center build from bare dirt to serving content in 86 days. Oversaw 8 billion dollars of capital deployment.
+- Led and consulted tier 1 payment compliance industry (PCI) implementations for some of the worlds largest brands (including at a payment processor).
+- Rolled out centralized Active Directory authentication, deployed Dell OpenManage, and upgraded network equipment.
+- Deployed password vault, Active Directory PKI, and implemented a ground-up network redesign.
+- Designed VmWare NSX network.
+\pagebreak
+ 
+## Employment History
+ 
+ 
+**CDK Global | Senior System Engineer | July 2024 - October 2024**
+ 
+ 
+- Security Compliance : worked with risk management/audit to remediate insecure configurations
+- Created Alma9 Packer image from scratch
+ 
+ 
+**Apple Computer | Senior System Administrator | March 2024 - July 2024**
+ 
+ 
+- Day to day server operations scheduling downtime etc
+ 
+ 
+**SHEIN | Staff Site Reliability Engineer | December 2022 - August 2023**
+ 
+ 
+- Streamlined engineer onboarding by documenting and overhauling the process, consolidating disparate guides into a comprehensive modular set of documents.
+- Established a taxonomy for team documentation in the wiki, implementing Confluence best practices for a proper knowledge base.
+- Served as the SRE Liaison for cybersecurity functions, ensuring compliance with data locality/partition requirements and pending federal data privacy legislation.
+- Focused on fostering a culture of automation and skill development within the SRE team, emphasizing code review, infrastructure as code, versioning, testing, and effective ticket management.
+- Contributed to Linux server administration both internally and externally, aiding colleagues with scripting/automation and assisting in the migration from AWS to Azure with zero customer-facing system impact. Additionally, provided day-to-day support for AWS and Azure activities and troubleshooting.
+ 
+ 
+**3M | Senior Site Reliability Engineer | March 2020 - November 2022**
+ 
+ 
+- Supported Vendavo on RedHat Linux, managed releases, and provided day-to-day developer support.
+- Created a homegrown YAML configuration management system, utilizing bash scripting and YAML templates with a CSV-based key/value store to efficiently manage and regenerate environment-specific variables for a line-of-business application across multiple development, testing, staging, and production environments.
+
+\pagebreak 
+ 
+**TippingPoint | Staff System Architect | March 2012 - June 2019**
+ 
+ 
+- Conducted code and design reviews for internal/external team projects and actively participated in broad enterprise collaboration, focusing on large-scale fleet management.
+- Managed user account administration, manual/semi-automated server provisioning, trouble tickets, security vulnerability remediation, and system/network auditing.
+- Led various projects, including migrating fleet systems from Centos 6 to Centos 7, implementing LXC/ LXD container versions for increased system utilization, and creating an on-premise deployment system (GUMPS) for automated provisioning.
+- Deployed network monitoring systems (Zenoss, observium/librenms), utilized librenms as a Conflguration Management Database (CMDB), and implemented a fleet orchestration system (Rundeck).
+- Executed extensive vulnerability remediation, OS/application/kernel patching, NIC customization/ optimization, and data migrations while developing and maintaining custom scripts for tasks such as LDAP management and SSL scenarios. Automated processes like re-imaging and ensured continuous distribution of a 40GB dataset of packet captures across a global fleet.
+ 
+ 
+**HostGator.com | Automation and Escalation Engineer | March 2011 - May 2012**
+ 
+ 
+- Provided senior-level Linux and web application support globally.
+- Developed standardized reply language and scripts, reducing errors in Level I Linux administrator department.
+ 
+ 
+**RippleTV | System Engineer | October 2008 - January 2010**
+ 
+ 
+- Provided system engineering expertise for customer-facing advertising platform (AdSpot) and internal fleet management tool (CPanel).
+- Utilized Nginx, Mongrel, Thin, Rails, Merb, Rack, MySQL, memcached, and F5 LTM.
+ 
+ 
+**Walt Disney Internet Group | Site Reliability Engineer | August 2006 - September 2007**
+ 
+ 
+-  Engaged in dynamic work environment focusing on popular web/ecommerce sites, including disneyworld.com and disneyland.com.
+- Provided design, architecture, and day-to-day administration for Disney park property sites generating $2 billion annually.
+- Provided system engineering and PCI compliance expertise for Disneyland.com, Disneyworld.com, DisneyCruiseLines.com, and 23 related properties.
+- Utilized Jboss instances on RHEL3/4 for business logic and employed Windows 2003 with Tomcat/IIS for frontend application serving.
+- Automated routine system administration tasks through the creation of batch and VBScript programs for Windows administration.
+- Led an Active Directory project for WDIG, designing and implementing a nationwide, highly available system across 3 data centers.
+- Managed the migration from Windows NT to Windows 2003 Active Directory domain controllers, including experience with Windows 2008, Centrify, and Samba/Winbind/LDAP/Kerberos.
+
+\pagebreak 
+ 
+**Electronic Clearing House | Senior System Administrator | April 2005 - July 2006**
+ 
+ 
+- Linux systems engineer in a 24x7 transaction processing/ecommerce/flnancial services environment, collaborating with network administration and infrastructure design teams.
+ - Ensured continuous uptime for high-impact environments, including a 1TB MySQL database, 300TB Oracle database, 1.5TB Oracle Data Warehouse, and a 4,000-store LAMP-based ecommerce system (MerchantAmerica.com).
+ - Successfully deployed an enterprise-wide Linux backup system, featuring encrypted backups stored on a central server with ISCSI attached network storage, utilizing GNUPG and tar over SSH. Regular backups and restores were tested weekly.
+ - Led the deployment of Oracle database infrastructure, implementing two Oracle RAC clusters with Dell 6850 servers, Qual Dual Core Xeon processors, and 32GB of RAM each. The clusters ran on RedHat Enterprise Linux 4.0 64bit edition, serving Data Warehouse, Transaction Processing Software, and Credit Card Clearing applications.
+ 
+ 
+**GSI Commerce | System Administrator | March 2002 -  February 2005**
+ 
+ 
+- Contributed to disaster recovery from an Informix Database failure.
+- Streamlined FTP server conflguration and deployed open-source remote control software.
+-  Upgraded network infrastructure from hubs to managed switches.
+ 
+ 
+**ReachableCEO Enterprises | Freelancer | January 2001 - December 2024**
+ 
+ 
+- Deployed,configured,supported Cloudron and Coolify PAAS and a full IT/SRE/Devops and engineering software stack for a stealth aerospace startup. 
+- Provided technician support to a team of electrical engineers building the power system for the radar of FrakenSAM in Ukraine. Handled high / low voltage wiring and plumbing and documentation of those systems. 
+- Provided root cause analysis and remediation for a security breach at a defense contractor.
+- Developed a rapidly field deployable mesh networking system for a variety of use cases.
+- Developed a secure global video conferencing system using only 3mbps for a major defense contractor.
+- Advised on backend infrastructure for broadcasting news and information via radio and internet into hostile powers. 
+ 
+\pagebreak
+ 
+## Skills
+ 
+|Skill|Experience|Skill Details|
+|---|---|---|
+|**Linux**|22 years|RHEL,Debian,Ubuntu,kickstart,PXE,  LDAP,SSSD,RPM/Deb package creation,  quotas,extended permissions, clustering,NFS,Samba|
+|**Unix**|5 years|HPUX/Solaris|
+|**Windows**|22 years|Server (2008  2016),Windows client automated deployment (7,8,10,11),Active Directory,Group Policy,WSUS,Certificate Services,AD DNS,AD DHCP,complex multiple forest and domain setups |
+|**Free/Libre/Open Source software**|22 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|
+|**Databases**|22 years| MySQL,PostgreSQL,  Dbeaver,PHPMyAdmin,PostGIS|
+|**Cyber Security**|22 years|PCI Compliance (tier 1 implementations),OpenVAS<,Lynis,security hardening,audits,breach response and mitigation, patch and vulnerability management. AppArmor, SeLinux, Centrify, Tripwire, Integrit, OSSEC |
+|**Virtualization**|22 years|VmWare,Parallels,HyperV,KVM,Xen|
+|**Networking**|22 years|Linux Virtual Server(LVS),HAProxy,Ubiquiti Unifi,Opnsense,Pfsense,DNS,DHCP,IPAM,PXE,IPS,IDS,GRE,IPSEC.Wireguard,OpenVPN,Nebula,Tailscale,RADIUS. Mostly layer2 data center/campus/access some WAN,firewall,layer3 |
+|**Monitoring**|22 years|Uptime Kuma,Librenms,Zabbix,Zenoss,Nagios,Elasticsearch,Logstash,Kibana(ELK)|
+|**Storage**|22 years|Netapp,EMC,EqualLogic,3par,MSA,TrueNAS/ZFS,iscsi,S3,Azure Storage|
+|**Cloud**|5 years|AWS,Azure,Kubernetes,Helm,Docker|
+|**Containerization**|15 years|LXC,Docker,OpenVZ|
+|**Configuration management/InfrastructureAsCode(IAC)**|22 years|FetchApply,Terraform/OpenTOfU,Ansible,AWX,Hashicorp Packer/Vault|
+|**Ticket / incident / project management**| 22 years| Jira,ServiceNow,Redmine,RT|
+|**Git**|15 years|Branching,merging,multiple teams,external vendors,submodules |
+|**SRE**|5 years| Grafana,Prometheus,Signoz,Wazuh|
+|**LLM**|2 years|OpenWebUI,QA/validation,RAG,data cleaning/prep|
+|**Programming**|5 years|J2ME,PHP,Ruby,TCL/TK,Java,C,C++|
+|**Automation**|22 years|Bash,YAML,TOML,PowerShell,Perl|
+|**Embedded development**|5 years|Raspberry pi,arduino,seeduino,Lego Mindstorms|

local/build-temp/JobBoard.yml

@@ -0,0 +1,12 @@
+title: "Charles N Wyble Resume"
+titlepage: true
+titlepage-logo: "D:\tsys\@ReachableCEO\ReachableCEO.png"
+date: \today
+header-left: "\\hspace{1cm}"
+header-center: "\\leftmark"
+header-right: "Page \\thepage"
+footer-left: "Charles N Wyble"
+footer-center: "Tenacity. Velocity. Focus."
+footer-right: "[Source code](https://git.knownelement.com/reachableceo/MarkdownResume-Pipeline)"
+urlcolor: blue
+page-background: "../vendor/git.knownelement.com/ExternalVendorCode/pandoc-latex-template/examples/page-background/backgrounds/background3.pdf"

local/build-temp/Resume.md

@@ -0,0 +1,102 @@
+ 
+## Career Highlights
+- Developed and implemented a process to switch thousands of desktops providing digital signage functionality from Fedora to Debian in a completely automated fashion using a custom initrd.
+- Developed and implemented an internal private cloud orchestration and provisioning system for a hardware development engineering team that handled the entire provisioning lifecycle for physical and virtual systems.
+- Developed and implemented standardized language and procedures and incident investigation automation for a large technical support organization with high turnover.
+- Developed and implemented an automated order status and payment handling interactive voice response application using Angel.ccm with a backend web service returning Voice XML. This allows call center personnel to focus on revenue generating opportunities instead of administrative matters.
+- Provided technician support to a team of electrical engineers building the power system for the radar of FrankenSAM in Ukraine. Handled high / low voltage wiring and plumbing and documentation of those systems.
+- Provided root cause analysis , mitigation and remediation of security breaches by advanced persistent threat actors at high value targets.
+- Project managed a successful brand new data center build from bare dirt to serving content in 86 days. Oversaw 8 billion dollars of capital deployment.
+- Led and consulted tier 1 payment compliance industry (PCI) implementations for some of the worlds largest brands (including at a payment processor).
+- Rolled out centralized Active Directory authentication, deployed Dell OpenManage, and upgraded network equipment.
+- Deployed password vault, Active Directory PKI, and implemented a ground-up network redesign.
+- Designed VmWare NSX network.
+\pagebreak
+ 
+## Employment History
+ 
+**CDK Global | Senior System Engineer | July 2024 - October 2024**
+ 
+- Security Compliance : worked with risk management/audit to remediate insecure configurations
+- Created Alma9 Packer image from scratch
+ 
+**Apple Computer | Senior System Administrator | March 2024 - July 2024**
+ 
+- Day to day server operations scheduling downtime etc
+ 
+**SHEIN | Staff Site Reliability Engineer | December 2022 - August 2023**
+ 
+- Streamlined engineer onboarding by documenting and overhauling the process, consolidating disparate guides into a comprehensive modular set of documents.
+- Established a taxonomy for team documentation in the wiki, implementing Confluence best practices for a proper knowledge base.
+- Served as the SRE Liaison for cybersecurity functions, ensuring compliance with data locality/partition requirements and pending federal data privacy legislation.
+- Focused on fostering a culture of automation and skill development within the SRE team, emphasizing code review, infrastructure as code, versioning, testing, and effective ticket management.
+- Contributed to Linux server administration both internally and externally, aiding colleagues with scripting/automation and assisting in the migration from AWS to Azure with zero customer-facing system impact. Additionally, provided day-to-day support for AWS and Azure activities and troubleshooting.
+ 
+**3M | Senior Site Reliability Engineer | March 2020 - November 2022**
+ 
+- Supported Vendavo on RedHat Linux, managed releases, and provided day-to-day developer support.
+- Created a homegrown YAML configuration management system, utilizing bash scripting and YAML templates with a CSV-based key/value store to efficiently manage and regenerate environment-specific variables for a line-of-business application across multiple development, testing, staging, and production environments.
+
+\pagebreak 
+**TippingPoint | Staff System Architect | March 2012 - June 2019**
+ 
+- Conducted code and design reviews for internal/external team projects and actively participated in broad enterprise collaboration, focusing on large-scale fleet management.
+- Managed user account administration, manual/semi-automated server provisioning, trouble tickets, security vulnerability remediation, and system/network auditing.
+- Led various projects, including migrating fleet systems from Centos 6 to Centos 7, implementing LXC/ LXD container versions for increased system utilization, and creating an on-premise deployment system (GUMPS) for automated provisioning.
+- Deployed network monitoring systems (Zenoss, observium/librenms), utilized librenms as a Conflguration Management Database (CMDB), and implemented a fleet orchestration system (Rundeck).
+- Executed extensive vulnerability remediation, OS/application/kernel patching, NIC customization/ optimization, and data migrations while developing and maintaining custom scripts for tasks such as LDAP management and SSL scenarios. Automated processes like re-imaging and ensured continuous distribution of a 40GB dataset of packet captures across a global fleet.
+ 
+**HostGator.com | Automation and Escalation Engineer | March 2011 - May 2012**
+ 
+- Provided senior-level Linux and web application support globally.
+- Developed standardized reply language and scripts, reducing errors in Level I Linux administrator department.
+ 
+**RippleTV | System Engineer | October 2008 - January 2010**
+ 
+- Provided system engineering expertise for customer-facing advertising platform (AdSpot) and internal fleet management tool (CPanel).
+- Utilized Nginx, Mongrel, Thin, Rails, Merb, Rack, MySQL, memcached, and F5 LTM.
+ 
+**Walt Disney Internet Group | Site Reliability Engineer | August 2006 - September 2007**
+ 
+-  Engaged in dynamic work environment focusing on popular web/ecommerce sites, including disneyworld.com and disneyland.com.
+- Provided design, architecture, and day-to-day administration for Disney park property sites generating $2 billion annually.
+- Provided system engineering and PCI compliance expertise for Disneyland.com, Disneyworld.com, DisneyCruiseLines.com, and 23 related properties.
+- Utilized Jboss instances on RHEL3/4 for business logic and employed Windows 2003 with Tomcat/IIS for frontend application serving.
+- Automated routine system administration tasks through the creation of batch and VBScript programs for Windows administration.
+- Led an Active Directory project for WDIG, designing and implementing a nationwide, highly available system across 3 data centers.
+- Managed the migration from Windows NT to Windows 2003 Active Directory domain controllers, including experience with Windows 2008, Centrify, and Samba/Winbind/LDAP/Kerberos.
+
+\pagebreak 
+**Electronic Clearing House | Senior System Administrator | April 2005 - July 2006**
+ 
+- Linux systems engineer in a 24x7 transaction processing/ecommerce/flnancial services environment, collaborating with network administration and infrastructure design teams.
+ - Ensured continuous uptime for high-impact environments, including a 1TB MySQL database, 300TB Oracle database, 1.5TB Oracle Data Warehouse, and a 4,000-store LAMP-based ecommerce system (MerchantAmerica.com).
+ - Successfully deployed an enterprise-wide Linux backup system, featuring encrypted backups stored on a central server with ISCSI attached network storage, utilizing GNUPG and tar over SSH. Regular backups and restores were tested weekly.
+ - Led the deployment of Oracle database infrastructure, implementing two Oracle RAC clusters with Dell 6850 servers, Qual Dual Core Xeon processors, and 32GB of RAM each. The clusters ran on RedHat Enterprise Linux 4.0 64bit edition, serving Data Warehouse, Transaction Processing Software, and Credit Card Clearing applications.
+ 
+**GSI Commerce | System Administrator | March 2002 -  February 2005**
+ 
+- Contributed to disaster recovery from an Informix Database failure.
+- Streamlined FTP server conflguration and deployed open-source remote control software.
+-  Upgraded network infrastructure from hubs to managed switches.
+ 
+**ReachableCEO Enterprises | Freelancer | January 2001 - December 2024**
+ 
+- Deployed,configured,supported Cloudron and Coolify PAAS and a full IT/SRE/Devops and engineering software stack for a stealth aerospace startup. 
+- Provided technician support to a team of electrical engineers building the power system for the radar of FrakenSAM in Ukraine. Handled high / low voltage wiring and plumbing and documentation of those systems. 
+- Provided root cause analysis and remediation for a security breach at a defense contractor.
+- Developed a rapidly field deployable mesh networking system for a variety of use cases.
+- Developed a secure global video conferencing system using only 3mbps for a major defense contractor.
+- Advised on backend infrastructure for broadcasting news and information via radio and internet into hostile powers. 
+ 
+\pagebreak
+ 
+## Skills
+ 
+|Skill|Experience|Skill Details|
+|---|---|---|
+|**Linux**|22 years|RHEL,Debian,Ubuntu,kickstart,PXE,  LDAP,SSSD,RPM/Deb package creation,  quotas,extended permissions, clustering,NFS,Samba|
+|**Unix**|5 years|HPUX/Solaris|
+|**Windows**|22 years|Server (2008  2016),Windows client automated deployment (7,8,10,11),Active Directory,Group Policy,WSUS,Certificate Services,AD DNS,AD DHCP,complex multiple forest and domain setups |
+|**Free/Libre/Open Source software**|22 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|
+|**Databases**|22 years| MySQL,PostgreSQL,  Dbeaver,PHPMyAdmin,PostGIS|

local/build/BuildTemplate-CandidateInfoSheet.yml

@@ -0,0 +1,14 @@
+title: "{{CandidateName}} Candidate Information Sheet"
+titlepage: true
+titlepage-logo: "{{CandidateLogo}}"
+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-right: "[Source code]({{SourceCode}})"
+urlcolor: {{URLCOLOR}}
+page-background: "{{PAGEBACKGROUND}}"

local/build/BuildTemplate-ClientSubmission.yml

@@ -0,0 +1,7 @@
+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-JobBoard.yml

@@ -0,0 +1,12 @@
+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/build.sh

@@ -0,0 +1,262 @@
+#!/usr/bin/env bash
+
+
+###################################################
+# Modify these values to suit
+###################################################
+
+
+########################
+# Contact info
+########################
+
+export CandidateName="Charles N Wyble"
+export CandidatePhone="1 818 280 7059"
+export CandidateLocation="Austin TX / Raleigh NC / Remote"
+export CandidateEmail="reachableceo@reachableceo.com"
+
+########################
+# Profile information
+########################
+
+export CandidateOneLineSummary="Super awesome and stuff."
+export CandidateLinkedin="https://www.linkedin.com/"
+export CandidateGithub="https://www.github.com/reachableceo"
+export CandidateTagline="Tenacity. Velocity. Focus."
+
+########################
+# Formatting options
+########################
+
+export CandidateLogo="D:\tsys\@ReachableCEO\ReachableCEO.png"
+export SourceCode="https://git.knownelement.com/reachableceo/MarkdownResume-Pipeline"
+export URLCOLOR="blue"
+export PAGEBACKGROUND="../vendor/git.knownelement.com/ExternalVendorCode/pandoc-latex-template/examples/page-background/backgrounds/background3.pdf"
+
+##########################
+# Candidate info sheet
+##########################
+
+export CandidatePreferredContactMethod="Email will get the fastest response."
+export CandidateWorkAuthorization="US Citizen"
+export CandidateEmploymentStatus="Not currently employed"
+export CandidateCurrentLocation="Austin, TX"
+export CandidateCurrentTimezone="CST"
+export CandidateWorkableTimezones="PST/CST/EST"
+export CandidateInterviewAvailability="Immediate"
+export CandidateStartAvailability="Two weeks"
+export CandidateHighestEducation="High School"
+export CandidateGraduationYear="2002"
+export CandidateSchoolName="Osborne Christian School"
+export CandidateSchoolLocation="Los Angeles, CA"
+export CandidateLastProject="CDK Global October 2024"
+export CandidateDOB="09/14"
+export CandidateTotalExperience="22 years"
+
+
+########################
+#Compensation targets
+########################
+
+export CandidateRelocationNetMinimumAmount="5,000.00"
+
+export CandidateRateSheetRemoteW2HourlyMinimum="\$60.00"
+export CandidateRateSheetRemoteW2AnnualMinimum="\$120,000.00"
+export CandidateRateSheetRemote1099HourlyMinimum="\$75.00"
+
+export CandidateRateSheetRemoteW2HourlyPrefer="\$70.00"
+export CandidateRateSheetRemoteW2AnnualPrefer="\$140,000.00"
+export CandidateRateSheetRemote1099HourlyPrefer="\$85.00"
+
+####################################################
+#DO NOT CHANGE ANYTHING BELOW THIS LINE
+####################################################
+
+############################################################
+# Setup globals
+############################################################
+
+readonly MO_PATH="bash ../../vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/mo/mo"
+readonly BUILD_OUTPUT_DIR="D:/tsys/@ReachableCEO/resume.reachableceo.com/"
+readonly BUILD_TEMP_DIR="../build-temp"
+readonly BUILDYAML_JOBBOARD="$BUILD_TEMP_DIR/JobBoard.yml"
+readonly BUILDYAML_CLIENTSUBMISSION="$BUILD_TEMP_DIR/ClientSubmission.yml"
+readonly BUILDYAML_CANDIDATEINFOSHEET="$BUILD_TEMP_DIR/CandidateInfoSheet.yml"
+
+CandidateInfoSheetMarkdownOutputFile="$BUILD_TEMP_DIR/CandidateInfoSheet.md"
+CandidateInfoSheetPDFOutputFIle="$BUILD_OUTPUT_DIR/recruiter/CandidateInfoSheet.pdf"
+
+JobBoardMarkdownOutputFile="$BUILD_TEMP_DIR/JobBoard-Resume.md"
+JobBoardPDFOutputFile="$BUILD_OUTPUT_DIR/job-board/CharlesNWyble-Resume.pdf"
+JobBoardMSWordOutputFile="$BUILD_OUTPUT_DIR/job-board/CharlesNWyble-Resume.doc"
+
+ClientSubmissionMarkdownOutputFile="$BUILD_TEMP_DIR/ClientSubmit-Resume.md"
+ClientSubmissionPDFOutputFile="$BUILD_OUTPUT_DIR/client-submit/CharlesNWyble-Resume.pdf"
+ClientSubmissionMSWordOutputFile="$BUILD_OUTPUT_DIR/client-submit/CharlesNWyble-Resume.doc"
+
+echo "Cleaning up from previous runs..."
+
+rm $BUILDYAML_CANDIDATEINFOSHEET
+rm $CandidateInfoSheetMarkdownOutputFile
+rm $CandidateInfoSheetPDFOutputFIle
+
+rm $BUILDYAML_JOBBOARD
+rm $JobBoardMarkdownOutputFile
+rm $JobBoardPDFOutputFile
+rm $JobBoardMSWordOutputFile
+
+rm $BUILDYAML_CLIENTSUBMISSION
+rm $ClientSubmissionMarkdownOutputFile
+rm $ClientSubmissionPDFOutputFile
+rm $ClientSubmissionMSWordOutputFile
+
+# Expand variables into rendered YAML files. These will be used by pandoc to create the output artifacts
+
+$MO_PATH ./BuildTemplate-CandidateInfoSheet.yml > $BUILDYAML_CANDIDATEINFOSHEET
+$MO_PATH ./BuildTemplate-JobBoard.yml > $BUILDYAML_JOBBOARD
+$MO_PATH ./BuildTemplate-ClientSubmission.yml > $BUILDYAML_CLIENTSUBMISSION
+
+echo "Creating candidate info sheet..."
+
+$MO_PATH ../Templates/CandidateInfoSheet/CandidateInfoSheet.md > $CandidateInfoSheetMarkdownOutputFile
+
+pandoc \
+"$CandidateInfoSheetMarkdownOutputFile" \
+--template eisvogel \
+--metadata-file="../build-temp/CandidateInfoSheet.yml" \
+--from markdown \
+--to=pdf \
+--output $CandidateInfoSheetPDFOutputFIle
+
+echo "Combining markdown files into single input file for pandoc..."
+
+# Create contact info md file
+$MO_PATH ../Templates/ContactInfo/ContactInfo-JobBoard.md > $BUILD_TEMP_DIR/ContactInfo-JobBoard.md
+$MO_PATH ../Templates/ContactInfo/ContactInfo-ClientSubmit.md > $BUILD_TEMP_DIR/ContactInfo-ClientSubmit.md
+
+#Pull in contact info
+cat $BUILD_TEMP_DIR/ContactInfo-JobBoard.md >> $JobBoardMarkdownOutputFile
+echo " " >> $JobBoardMarkdownOutputFile
+
+cat $BUILD_TEMP_DIR/ContactInfo-ClientSubmit.md >> $ClientSubmissionMarkdownOutputFile
+echo " " >> $ClientSubmissionMarkdownOutputFile
+
+echo "## Career Highlights" >> $JobBoardMarkdownOutputFile
+echo "## Career Highlights" >> $ClientSubmissionMarkdownOutputFile
+
+cat ../Templates/SkillsAndProjects/Projects.md >> $JobBoardMarkdownOutputFile
+echo "\pagebreak" >> $JobBoardMarkdownOutputFile
+
+cat ../Templates/SkillsAndProjects/Projects.md >> $ClientSubmissionMarkdownOutputFile
+echo "\pagebreak" >> $ClientSubmissionMarkdownOutputFile
+
+echo " " >> $JobBoardMarkdownOutputFile
+echo "## Employment History" >> $JobBoardMarkdownOutputFile
+echo " " >> $JobBoardMarkdownOutputFile
+
+echo " " >> $ClientSubmissionMarkdownOutputFile
+echo "## Employment History" >> $ClientSubmissionMarkdownOutputFile
+echo " " >> $ClientSubmissionMarkdownOutputFile
+
+#And here we do some magic...
+#Pull in :
+
+# employer
+# title
+# start/end dates of employment 
+# long form position summary data from each position
+
+IFS=$'\n\t'
+for position in \
+$(cat ../Templates/WorkHistory/WorkHistory.csv); do
+
+COMPANY="$(echo $position|awk -F ',' '{print $1}')"
+TITLE="$(echo $position|awk -F ',' '{print $2}')"
+DATEOFEMPLOY="$(echo $position|awk -F ',' '{print $3}')"
+
+echo " " >> "$JobBoardMarkdownOutputFile"
+echo "**$COMPANY | $TITLE | $DATEOFEMPLOY**" >> $JobBoardMarkdownOutputFile
+echo " " >> "$JobBoardMarkdownOutputFile"
+
+echo "**$COMPANY | $TITLE | $DATEOFEMPLOY**" >> $ClientSubmissionMarkdownOutputFile
+echo " " >> "$ClientSubmissionMarkdownOutputFile"
+
+echo " " >> "$JobBoardMarkdownOutputFile"
+cat ../Templates/JobHistoryDetails/$COMPANY.md >> "$JobBoardMarkdownOutputFile"
+echo " " >> "$JobBoardMarkdownOutputFile"
+
+cat ../Templates/JobHistoryDetails/$COMPANY.md >> "$ClientSubmissionMarkdownOutputFile"
+echo " " >> "$ClientSubmissionMarkdownOutputFile"
+done
+
+#Pull in my skills and generate a beautiful table.
+
+echo "\pagebreak" >> $JobBoardMarkdownOutputFile
+echo " " >> "$JobBoardMarkdownOutputFile"
+echo "## Skills" >> "$JobBoardMarkdownOutputFile"
+echo " " >> "$JobBoardMarkdownOutputFile"
+
+echo "\pagebreak" >> $ClientSubmissionMarkdownOutputFile
+echo " " >> "$ClientSubmissionMarkdownOutputFile"
+echo "## Skills" >> "$ClientSubmissionMarkdownOutputFile"
+echo " " >> "$ClientSubmissionMarkdownOutputFile"
+
+#Table heading
+echo "|Skill|Experience|Skill Details|" >> $JobBoardMarkdownOutputFile
+echo "|---|---|---|" >> $JobBoardMarkdownOutputFile
+
+echo "|Skill|Experience|Skill Details|" >> $ClientSubmissionMarkdownOutputFile
+echo "|---|---|---|" >> $ClientSubmissionMarkdownOutputFile
+
+#Table rows
+IFS=$'\n\t'
+for skill in \
+$(cat ../Templates/SkillsAndProjects/Skills.csv); do
+SKILL_NAME="$(echo $skill|awk -F '|' '{print $1}')"
+SKILL_YEARS="$(echo $skill|awk -F '|' '{print $2}')"
+SKILL_DETAIL="$(echo $skill|awk -F '|' '{print $3}')"
+echo "|**$SKILL_NAME**|$SKILL_YEARS|$SKILL_DETAIL|" >> $JobBoardMarkdownOutputFile
+echo "|**$SKILL_NAME**|$SKILL_YEARS|$SKILL_DETAIL|" >> $ClientSubmissionMarkdownOutputFile
+
+done
+unset IFS
+
+echo "Generating PDF output for job board version..."
+
+pandoc \
+"$JobBoardMarkdownOutputFile" \
+--template eisvogel \
+--metadata-file="../build-temp/JobBoard.yml" \
+--from markdown \
+--to=pdf \
+--output $JobBoardPDFOutputFile
+
+echo "Generating MSWord output for job board version..."
+
+pandoc \
+"$JobBoardMarkdownOutputFile" \
+--metadata-file="../build-temp/JobBoard.yml" \
+--from markdown \
+--to=docx \
+--reference-doc=resume-docx-reference.docx \
+--output $JobBoardMSWordOutputFile
+
+echo "Generating PDF output for client submission version..."
+
+pandoc \
+"$ClientSubmissionMarkdownOutputFile" \
+--template eisvogel \
+--metadata-file="../build-temp/ClientSubmission.yml" \
+--from markdown \
+--to=pdf \
+--output $ClientSubmissionPDFOutputFile
+
+echo "Generating MSWord output for client submission version..."
+
+pandoc \
+"$ClientSubmissionMarkdownOutputFile" \
+--metadata-file="../build-temp/ClientSubmission.yml" \
+--from markdown \
+--to=docx \
+--reference-doc=resume-docx-reference.docx \
+--output $ClientSubmissionMSWordOutputFile

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/.gitignore

@@ -0,0 +1,4 @@
+build-temp/client-submission/*.md
+build-temp/job-board/*.md
+build-temp/*.yml
+build-temp/*.md

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/LICENSE

@@ -0,0 +1,235 @@
+GNU AFFERO GENERAL PUBLIC LICENSE
+Version 3, 19 November 2007
+
+Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
+
+Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
+
+                            Preamble
+
+The GNU Affero General Public License is a free, copyleft license for software and other kinds of works, specifically designed to ensure cooperation with the community in the case of network server software.
+
+The licenses for most software and other practical works are designed to take away your freedom to share and change the works.  By contrast, our General Public Licenses are intended to guarantee your freedom to share and change all versions of a program--to make sure it remains free software for all its users.
+
+When we speak of free software, we are referring to freedom, not price.  Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things.
+
+Developers that use our General Public Licenses protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License which gives you legal permission to copy, distribute and/or modify the software.
+
+A secondary benefit of defending all users' freedom is that improvements made in alternate versions of the program, if they receive widespread use, become available for other developers to incorporate.  Many developers of free software are heartened and encouraged by the resulting cooperation.  However, in the case of software used on network servers, this result may fail to come about. The GNU General Public License permits making a modified version and letting the public access it on a server without ever releasing its source code to the public.
+
+The GNU Affero General Public License is designed specifically to ensure that, in such cases, the modified source code becomes available to the community.  It requires the operator of a network server to provide the source code of the modified version running there to the users of that server.  Therefore, public use of a modified version, on a publicly accessible server, gives the public access to the source code of the modified version.
+
+An older license, called the Affero General Public License and published by Affero, was designed to accomplish similar goals.  This is a different license, not a version of the Affero GPL, but Affero has released a new version of the Affero GPL which permits relicensing under this license.
+
+The precise terms and conditions for copying, distribution and modification follow.
+
+                       TERMS AND CONDITIONS
+
+0. Definitions.
+
+"This License" refers to version 3 of the GNU Affero General Public License.
+
+"Copyright" also means copyright-like laws that apply to other kinds of works, such as semiconductor masks.
+
+"The Program" refers to any copyrightable work licensed under this License.  Each licensee is addressed as "you".  "Licensees" and "recipients" may be individuals or organizations.
+
+To "modify" a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy.  The resulting work is called a "modified version" of the earlier work or a work "based on" the earlier work.
+
+A "covered work" means either the unmodified Program or a work based on the Program.
+
+To "propagate" a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy.  Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well.
+
+To "convey" a work means any kind of propagation that enables other parties to make or receive copies.  Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying.
+
+An interactive user interface displays "Appropriate Legal Notices" to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License.  If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion.
+
+1. Source Code.
+The "source code" for a work means the preferred form of the work for making modifications to it.  "Object code" means any non-source form of a work.
+
+A "Standard Interface" means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language.
+
+The "System Libraries" of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form.  A "Major Component", in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it.
+
+The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities.  However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work.  For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
+
+The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source.
+
+The Corresponding Source for a work in source code form is that same work.
+
+2. Basic Permissions.
+All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met.  This License explicitly affirms your unlimited permission to run the unmodified Program.  The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work.  This License acknowledges your rights of fair use or other equivalent, as provided by copyright law.
+
+You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force.  You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright.  Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you.
+
+Conveying under any other circumstances is permitted solely under the conditions stated below.  Sublicensing is not allowed; section 10 makes it unnecessary.
+
+3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures.
+
+When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures.
+
+4. Conveying Verbatim Copies.
+You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program.
+
+You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee.
+
+5. Conveying Modified Source Versions.
+You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions:
+
+    a) The work must carry prominent notices stating that you modified it, and giving a relevant date.
+
+    b) The work must carry prominent notices stating that it is released under this License and any conditions added under section 7.  This requirement modifies the requirement in section 4 to "keep intact all notices".
+
+    c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy.  This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged.  This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it.
+
+    d) If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so.
+
+A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an "aggregate" if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit.  Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate.
+
+6. Conveying Non-Source Forms.
+You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways:
+
+    a) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange.
+
+    b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge.
+
+    c) Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source.  This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b.
+
+    d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge.  You need not require recipients to copy the Corresponding Source along with the object code.  If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source.  Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements.
+
+    e) Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d.
+
+A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work.
+
+A "User Product" is either (1) a "consumer product", which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling.  In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage.  For a particular product received by a particular user, "normally used" refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product.  A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product.
+
+"Installation Information" for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source.  The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made.
+
+If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information.  But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM).
+
+The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed.  Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network.
+
+Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying.
+
+7. Additional Terms.
+"Additional permissions" are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law.  If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions.
+
+When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it.  (Additional permissions may be written to require their own removal in certain cases when you modify the work.)  You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission.
+
+Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms:
+
+    a) Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or
+
+    b) Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or
+
+    c) Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or
+
+    d) Limiting the use for publicity purposes of names of licensors or authors of the material; or
+
+    e) Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or
+
+    f) Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors.
+
+All other non-permissive additional terms are considered "further restrictions" within the meaning of section 10.  If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term.  If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying.
+
+If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms.
+
+Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way.
+
+8. Termination.
+
+You may not propagate or modify a covered work except as expressly provided under this License.  Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11).
+
+However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation.
+
+Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice.
+
+Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License.  If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10.
+
+9. Acceptance Not Required for Having Copies.
+
+You are not required to accept this License in order to receive or run a copy of the Program.  Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance.  However, nothing other than this License grants you permission to propagate or modify any covered work.  These actions infringe copyright if you do not accept this License.  Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so.
+
+10. Automatic Licensing of Downstream Recipients.
+
+Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License.  You are not responsible for enforcing compliance by third parties with this License.
+
+An "entity transaction" is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations.  If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts.
+
+You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License.  For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it.
+
+11. Patents.
+
+A "contributor" is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based.  The work thus licensed is called the contributor's "contributor version".
+
+A contributor's "essential patent claims" are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version.  For purposes of this definition, "control" includes the right to grant patent sublicenses in a manner consistent with the requirements of this License.
+
+Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version.
+
+In the following three paragraphs, a "patent license" is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement).  To "grant" such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party.
+
+If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent
+license to downstream recipients.  "Knowingly relying" means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient's use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid.
+
+If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it.
+
+A patent license is "discriminatory" if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License.  You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007.
+
+Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law.
+
+12. No Surrender of Others' Freedom.
+
+If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License.  If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may
+not convey it at all.  For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program.
+
+13. Remote Network Interaction; Use with the GNU General Public License.
+
+Notwithstanding any other provision of this License, if you modify the Program, your modified version must prominently offer all users interacting with it remotely through a computer network (if your version supports such interaction) an opportunity to receive the Corresponding Source of your version by providing access to the Corresponding Source from a network server at no charge, through some standard or customary means of facilitating copying of software.  This Corresponding Source shall include the Corresponding Source for any work covered by version 3 of the GNU General Public License that is incorporated pursuant to the following paragraph.
+
+Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU General Public License into a single combined work, and to convey the resulting work.  The terms of this License will continue to apply to the part which is the covered work, but the work with which it is combined will remain governed by version 3 of the GNU General Public License.
+
+14. Revised Versions of this License.
+
+The Free Software Foundation may publish revised and/or new versions of the GNU Affero General Public License from time to time.  Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number.  If the Program specifies that a certain numbered version of the GNU Affero General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation.  If the Program does not specify a version number of the GNU Affero General Public License, you may choose any version ever published by the Free Software Foundation.
+
+If the Program specifies that a proxy can decide which future versions of the GNU Affero General Public License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Program.
+
+Later license versions may give you additional or different permissions.  However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version.
+
+15. Disclaimer of Warranty.
+
+THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+16. Limitation of Liability.
+
+IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
+
+17. Interpretation of Sections 15 and 16.
+
+If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee.
+
+END OF TERMS AND CONDITIONS
+
+            How to Apply These Terms to Your New Programs
+
+If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.
+
+To do so, attach the following notices to the program.  It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found.
+
+     MarkdownResume-Pipeline
+     Copyright (C) 2024  reachableceo
+
+     This program is free software: you can redistribute it and/or modify it under the terms of the GNU Affero General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
+
+     This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU Affero General Public License for more details.
+
+     You should have received a copy of the GNU Affero General Public License along with this program.  If not, see <http://www.gnu.org/licenses/>.
+
+Also add information on how to contact you by electronic and paper mail.
+
+If your software can interact with users remotely through a computer network, you should also make sure that it provides a way for users to get its source.  For example, if your program is a web application, its interface could display a "Source" link that leads users to an archive of the code.  There are many ways you could offer source, and different solutions will be better for different programs; see section 13 for the specific requirements.
+
+You should also get your employer (if you work as a programmer) or school, if any, to sign a "copyright disclaimer" for the program, if necessary. For more information on this, and how to apply and follow the GNU AGPL, see <http://www.gnu.org/licenses/>.

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/README.md

@@ -0,0 +1,63 @@
+# MarkdownResume-Pipeline
+
+- [MarkdownResume-Pipeline](#markdownresume-pipeline)
+  - [Introduction](#introduction)
+  - [Quickstart](#quickstart)
+  - [Directory Overview](#directory-overview)
+  - [Build pipeline](#build-pipeline)
+    - [Outputs](#outputs)
+  - [Production Use](#production-use)
+
+## Introduction
+
+Resume formatting/publication/management is difficult, tedious, annoying etc. The @ReachableCEO has hacked the process and made it easy!
+
+## Quickstart
+
+I recommend doing these steps in order for efficency.
+
+- Edit build/build.sh and alter the top section to refelct your information.
+- Edit Templates/WorkHistory/WorkHistory.csv
+- Create Templates/JobHistoryDetails/<position>.md to match the value in the first field of WorkHistory.csv
+- Edit SkillsAndProjects/Projects.md
+- Edit SkillsAndProjects/Skills.csv
+- Edit Templates/CandidateInfoSheet.md
+- cd to the build directory and bash build.sh
+
+## Directory Overview
+
+- build: build script and associated support files.
+- build-output: markdown file for pandoc gets placed here. If you want to make formatting changes before conversion to PDF/Word, you can do so.
+- build-temp: working directory for the build process. In case you need to debug an intermediate step.
+- Templates
+  - CandidateInfoSHeet: contains the markdown/yaml template files for a candidate information sheet. This allows you to produce a standardized reply to recruiters to eliminate an average of 6 emails/phone calls per inbound lead. It has a rate sheet and all the standard "matrix" tables they need to fill out for submission to an end client (or, in reality, to the US based recruiting team who interfaces with the client).
+  - ContactInfo: contact info (one version for the recruiter facing resume, one version for client facing).
+  - JobHistoryDetails: details for each position listed in WorkHistory/WorkHistory.csv.
+  - SkillsAndProjects: This contains what the name says. Holds a skills.csv file that gets turned into a skills table and a projects file that gets placed at beginning of resume as a career highlights section.
+  - WorkHistory: contains the WorkHistory.csv file used by the build script to generate Employment History section.
+
+## Build pipeline
+
+In the build directory:
+
+- build.sh - Builds three assets:
+  - PDF/Word for submitting to job portals
+  - PDF/Word for submitting to end clients (strips cover sheet/contact info)
+  - PDF of the candidate information sheet.
+- BuildTemplate-* : Templatized YAML metadata files that get rendered during the build process to be used by Pandoc.
+- resume-docx-reference.docx: Template "style" file for Word output.
+
+### Outputs
+
+- Word format output is a best effort . The style file was sourced from : <https://sdsawtelle.github.io/blog/output/simple-markdown-resume-with-pandoc-and-wkhtmltopdf.html> (vendored in vendor/git.knownelement.com/ExternalVendorCode/markdown-resume just in case)
+- PDF output considered production. Please see: <https://github.com/Wandmalfarbe/pandoc-latex-template> (vendored in vendor/git.knownelement.com/ExternalVendorCode/pandoc-latex-template ) and <https://github.com/ReachableCEO/rcdoc-pipeline> if you want to re-create/modify the build pipeline for your own markdown project.
+
+## Production Use
+
+This system is in production use by the @ReachableCEO:
+
+- [MarkdownResume-ReachableCEO](https://git.knownelement.com/reachableceo/MarkdownResume-ReachableCEO)
+- [ReachableCEO Career Site](https://resume.reachableceo.com)
+- uploaded to all major job portals
+
+This was a labor of love by the @ReachableCEO in the hopes others can massively optimize the job hunt process.

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/Templates/CandidateInfoSheet/CandidateInfoSheet.md

@@ -0,0 +1,121 @@
+# {{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                                  |

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/Templates/ContactInfo/ContactInfo-ClientSubmit.md

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

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/Templates/ContactInfo/ContactInfo-JobBoard.md

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

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/build-temp/CandidateInfoSheet.md

@@ -0,0 +1,121 @@
+# First Middle Last 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 **Place 1/Place 2** 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 1,987.11** 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):
+
+- **$12.34** per hour(w2)
+- **$123,456.00** annually
+- **$56.78** per hour (1099/corp to corp)
+
+I have a strong preference for roles that are :
+
+- **$34.56** per hour(w2) or more
+- **$321,987.00** annually or more
+- **$78.90** per hour (1099/corp to corp) or more
+
+### On-site/hybrid roles
+
+- **$34.56** per hour(w2) or more
+- **$321,987.00** annually or more
+- **$78.90** 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                             | First Middle Last                   |
+| E-mail address                        |                    |
+| Phone number                          | 1 123 456 7890                  |
+| Preferred form of contact             | Email will get the fastest response. |
+| Work authorization                    | US Citizen      |
+| Are you employed presently?           | Not currently employed       |
+| Current location                      | City,State,Country etc        |
+| Current timezone                      | Timezone        |
+| Timezones I can work in               | Timezones      |
+| Availability to interview             | Sometime  |
+| Availability to start                 | Sometime      |
+| Highest Education                     | Some education level       |
+| Graduated Year                        | Graduation year         |
+| Name of school                        | School name             |
+| Location of school                    | School location         |
+| Linkedin Profile                      | (https://www.linkedin.com/)             |
+| Github Profile                        | (https://www.github.com/)               |
+| Last project                          | Last project            |
+| DOB                                   | MM/DD                    |
+| Total IT/career experience            | epoch        |
+| Open to in-office/hybrid/remote       | Yes                                 |
+| Any trips planned in next six months? | No                                  |

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/build-temp/client-submission/ignore-this-dir

@@ -0,0 +1 @@
+This directory is used by the build process. Ignore it.

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/build-temp/ignore-this-dir

@@ -0,0 +1 @@
+Working directory for the pipeline. Don't use.

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/build-temp/job-board/ignore-this-dir

@@ -0,0 +1 @@
+This directory is used by the build process. Ignore it.

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/build/BuildTemplate-CandidateInfoSheet.yml

@@ -0,0 +1,14 @@
+title: "{{CandidateName}} Candidate Information Sheet"
+titlepage: true
+titlepage-logo: "{{CandidateLogo}}"
+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-right: "[Source code]({{SourceCode}})"
+urlcolor: {{URLCOLOR}}
+page-background: "{{PAGEBACKGROUND}}"

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/build/BuildTemplate-ClientSubmission.yml

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

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/build/BuildTemplate-JobBoard.yml

@@ -0,0 +1,12 @@
+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}}"

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/build/build.sh

@@ -0,0 +1,262 @@
+#!/usr/bin/env bash
+
+
+###################################################
+# Modify these values to suit
+###################################################
+
+
+########################
+# Contact info
+########################
+
+export CandidateName="First Middle Last"
+export CandidatePhone="1 123 456 7890"
+export CandidateLocation="Place 1/Place 2"
+export CandidateEmail="candidate@domain.com"
+
+########################
+# Profile information
+########################
+
+export CandidateOneLineSummary="Super awesome and stuff."
+export CandidateLinkedin="https://www.linkedin.com/"
+export CandidateGithub="https://www.github.com/"
+export CandidateTagline="Your.Tagline.Here."
+
+########################
+# Formatting options
+########################
+
+export CandidateLogo=""
+export SourceCode="https://git.knownelement.com/reachableceo/MarkdownResume-Pipeline"
+export URLCOLOR="blue"
+export PAGEBACKGROUND="../vendor/git.knownelement.com/ExternalVendorCode/pandoc-latex-template/examples/page-background/backgrounds/background3.pdf"
+
+##########################
+# 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"
+
+####################################################
+#DO NOT CHANGE ANYTHING BELOW THIS LINE
+####################################################
+
+############################################################
+# Setup globals
+############################################################
+
+readonly MO_PATH="bash ../vendor/git.knownelement.com/ExternalVendorCode/mo/mo"
+readonly BUILD_OUTPUT_DIR="../build-output"
+readonly BUILD_TEMP_DIR="../build-temp"
+readonly BUILDYAML_JOBBOARD="$BUILD_TEMP_DIR/JobBoard.yml"
+readonly BUILDYAML_CLIENTSUBMISSION="$BUILD_TEMP_DIR/ClientSubmission.yml"
+readonly BUILDYAML_CANDIDATEINFOSHEET="$BUILD_TEMP_DIR/CandidateInfoSheet.yml"
+
+CandidateInfoSheetMarkdownOutputFile="$BUILD_OUTPUT_DIR/CandidateInfoSheet.md"
+CandidateInfoSheetPDFOutputFIle="$BUILD_OUTPUT_DIR/CandidateInfoSheet.pdf"
+
+JobBoardMarkdownOutputFile="$BUILD_OUTPUT_DIR/job-board/Resume.md"
+JobBoardPDFOutputFile="$BUILD_OUTPUT_DIR/job-board/Resume.pdf"
+JobBoardMSWordOutputFile="$BUILD_OUTPUT_DIR/job-board/Resume.doc"
+
+ClientSubmissionMarkdownOutputFile="$BUILD_OUTPUT_DIR/client-submission/Resume.md"
+ClientSubmissionPDFOutputFile="$BUILD_OUTPUT_DIR/client-submission//Resume.pdf"
+ClientSubmissionMSWordOutputFile="$BUILD_OUTPUT_DIR/client-submission/Resume.doc"
+
+echo "Cleaning up from previous runs..."
+
+rm $BUILDYAML_CANDIDATEINFOSHEET
+rm $CandidateInfoSheetMarkdownOutputFile
+rm $CandidateInfoSheetPDFOutputFIle
+
+rm $BUILDYAML_JOBBOARD
+rm $JobBoardMarkdownOutputFile
+rm $JobBoardPDFOutputFile
+rm $JobBoardMSWordOutputFile
+
+rm $BUILDYAML_CLIENTSUBMISSION
+rm $ClientSubmissionMarkdownOutputFile
+rm $ClientSubmissionPDFOutputFile
+rm $ClientSubmissionMSWordOutputFile
+
+# Expand variables into rendered YAML files. These will be used by pandoc to create the output artifacts
+
+$MO_PATH ./BuildTemplate-CandidateInfoSheet.yml > $BUILDYAML_CANDIDATEINFOSHEET
+$MO_PATH ./BuildTemplate-JobBoard.yml > $BUILDYAML_JOBBOARD
+$MO_PATH ./BuildTemplate-ClientSubmission.yml > $BUILDYAML_CLIENTSUBMISSION
+
+echo "Creating candidate info sheet..."
+
+$MO_PATH ../Templates/CandidateInfoSheet/CandidateInfoSheet.md > $CandidateInfoSheetMarkdownOutputFile
+
+pandoc \
+"$CandidateInfoSheetMarkdownOutputFile" \
+--template eisvogel \
+--metadata-file="../build-temp/CandidateInfoSheet.yml" \
+--from markdown \
+--to=pdf \
+--output $CandidateInfoSheetPDFOutputFIle
+
+echo "Combining markdown files into single input file for pandoc..."
+
+# Create contact info md file
+$MO_PATH ../Templates/ContactInfo/ContactInfo-JobBoard.md > $BUILD_TEMP_DIR/ContactInfo-JobBoard.md
+$MO_PATH ../Templates/ContactInfo/ContactInfo-ClientSubmit.md > $BUILD_TEMP_DIR/ContactInfo-ClientSubmit.md
+
+#Pull in contact info
+cat $BUILD_TEMP_DIR/ContactInfo-JobBoard.md >> $JobBoardMarkdownOutputFile
+echo " " >> $JobBoardMarkdownOutputFile
+
+cat $BUILD_TEMP_DIR/ContactInfo-ClientSubmit.md >> $ClientSubmissionMarkdownOutputFile
+echo " " >> $ClientSubmissionMarkdownOutputFile
+
+echo "## Career Highlights" >> $JobBoardMarkdownOutputFile
+echo "## Career Highlights" >> $ClientSubmissionMarkdownOutputFile
+
+cat ../Templates/SkillsAndProjects/Projects.md >> $JobBoardMarkdownOutputFile
+echo "\pagebreak" >> $JobBoardMarkdownOutputFile
+
+cat ../Templates/SkillsAndProjects/Projects.md >> $ClientSubmissionMarkdownOutputFile
+echo "\pagebreak" >> $ClientSubmissionMarkdownOutputFile
+
+echo " " >> $JobBoardMarkdownOutputFile
+echo "## Employment History" >> $JobBoardMarkdownOutputFile
+echo " " >> $JobBoardMarkdownOutputFile
+
+echo " " >> $ClientSubmissionMarkdownOutputFile
+echo "## Employment History" >> $ClientSubmissionMarkdownOutputFile
+echo " " >> $ClientSubmissionMarkdownOutputFile
+
+#And here we do some magic...
+#Pull in :
+
+# employer
+# title
+# start/end dates of employment 
+# long form position summary data from each position
+
+IFS=$'\n\t'
+for position in \
+$(cat ../Templates/WorkHistory/WorkHistory.csv); do
+
+COMPANY="$(echo $position|awk -F ',' '{print $1}')"
+TITLE="$(echo $position|awk -F ',' '{print $2}')"
+DATEOFEMPLOY="$(echo $position|awk -F ',' '{print $3}')"
+
+echo " " >> "$JobBoardMarkdownOutputFile"
+echo "**$COMPANY | $TITLE | $DATEOFEMPLOY**" >> $JobBoardMarkdownOutputFile
+echo " " >> "$JobBoardMarkdownOutputFile"
+
+echo "**$COMPANY | $TITLE | $DATEOFEMPLOY**" >> $ClientSubmissionMarkdownOutputFile
+echo " " >> "$ClientSubmissionMarkdownOutputFile"
+
+echo " " >> "$JobBoardMarkdownOutputFile"
+cat ../Templates/JobHistoryDetails/$COMPANY.md >> "$JobBoardMarkdownOutputFile"
+echo " " >> "$JobBoardMarkdownOutputFile"
+
+cat ../Templates/JobHistoryDetails/$COMPANY.md >> "$ClientSubmissionMarkdownOutputFile"
+echo " " >> "$ClientSubmissionMarkdownOutputFile"
+done
+
+#Pull in my skills and generate a beautiful table.
+
+echo "\pagebreak" >> $JobBoardMarkdownOutputFile
+echo " " >> "$JobBoardMarkdownOutputFile"
+echo "## Skills" >> "$JobBoardMarkdownOutputFile"
+echo " " >> "$JobBoardMarkdownOutputFile"
+
+echo "\pagebreak" >> $ClientSubmissionMarkdownOutputFile
+echo " " >> "$ClientSubmissionMarkdownOutputFile"
+echo "## Skills" >> "$ClientSubmissionMarkdownOutputFile"
+echo " " >> "$ClientSubmissionMarkdownOutputFile"
+
+#Table heading
+echo "|Skill|Experience|Skill Details|" >> $JobBoardMarkdownOutputFile
+echo "|---|---|---|" >> $JobBoardMarkdownOutputFile
+
+echo "|Skill|Experience|Skill Details|" >> $ClientSubmissionMarkdownOutputFile
+echo "|---|---|---|" >> $ClientSubmissionMarkdownOutputFile
+
+#Table rows
+IFS=$'\n\t'
+for skill in \
+$(cat ../Templates/SkillsAndProjects/Skills.csv); do
+SKILL_NAME="$(echo $skill|awk -F '|' '{print $1}')"
+SKILL_YEARS="$(echo $skill|awk -F '|' '{print $2}')"
+SKILL_DETAIL="$(echo $skill|awk -F '|' '{print $3}')"
+echo "|**$SKILL_NAME**|$SKILL_YEARS|$SKILL_DETAIL|" >> $JobBoardMarkdownOutputFile
+echo "|**$SKILL_NAME**|$SKILL_YEARS|$SKILL_DETAIL|" >> $ClientSubmissionMarkdownOutputFile
+
+done
+unset IFS
+
+echo "Generating PDF output for job board version..."
+
+pandoc \
+"$JobBoardMarkdownOutputFile" \
+--template eisvogel \
+--metadata-file="../build-temp/JobBoard.yml" \
+--from markdown \
+--to=pdf \
+--output $JobBoardPDFOutputFile
+
+echo "Generating MSWord output for job board version..."
+
+pandoc \
+"$JobBoardMarkdownOutputFile" \
+--metadata-file="../build-temp/JobBoard.yml" \
+--from markdown \
+--to=docx \
+--reference-doc=resume-docx-reference.docx \
+--output $JobBoardMSWordOutputFile
+
+echo "Generating PDF output for client submission version..."
+
+pandoc \
+"$ClientSubmissionMarkdownOutputFile" \
+--template eisvogel \
+--metadata-file="../build-temp/ClientSubmission.yml" \
+--from markdown \
+--to=pdf \
+--output $ClientSubmissionPDFOutputFile
+
+echo "Generating MSWord output for client submission version..."
+
+pandoc \
+"$ClientSubmissionMarkdownOutputFile" \
+--metadata-file="../build-temp/ClientSubmission.yml" \
+--from markdown \
+--to=docx \
+--reference-doc=resume-docx-reference.docx \
+--output $ClientSubmissionMSWordOutputFile

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,7 @@
+Thanks for contributing to b3bp! As part of your PR, have you:
+
+- [ ] Added an item in [CHANGELOG.md](https://github.com/kvz/bash3boilerplate/blob/HEAD/CHANGELOG.md) with attribution?
+- [ ] Added your name to the [README.md](https://github.com/kvz/bash3boilerplate/blob/HEAD/README.md#authors)
+- [ ] Linted your code? (`make test` should do the trick)
+
+If so, great! Feel free to replace this message with a description of your work and hit submit!

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/.github/dependabot.yml

@@ -0,0 +1,5 @@
+groups:
+  production-dependencies:
+    dependency-type: 'production'
+  development-dependencies:
+    dependency-type: 'development'

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/.github/workflows/ci.yml

@@ -0,0 +1,30 @@
+name: b3bp CI
+on:
+  push:
+    branches:
+      - main
+  pull_request:
+    types:
+      - opened
+      - synchronize
+jobs:
+  ci:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+        with:
+          fetch-depth: 1
+      - uses: actions/setup-node@v1
+        with:
+          node-version: 18.x
+      - name: Install
+        run: |
+          corepack yarn
+      - name: Lint
+        env:
+          SHELLCHECK_SEVERITY: warning
+        run: |
+          corepack yarn lint
+      - name: Test
+        run: |
+          corepack yarn test

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/.gitignore

@@ -0,0 +1,5 @@
+.yarn
+assets/build
+env.sh
+node_modules
+npm-debug.log

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/.shellcheckrc

@@ -0,0 +1,3 @@
+external-sources=true
+shell=bash
+color=always

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/.vscode/bash3boilerplate.code-workspace

@@ -0,0 +1,8 @@
+{
+	"folders": [
+		{
+			"path": ".."
+		}
+	],
+	"settings": {}
+}

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/.yarnrc.yml

@@ -0,0 +1 @@
+nodeLinker: node-modules

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/CHANGELOG.md

@@ -0,0 +1,175 @@
+# Changelog
+
+Here's is a combined todo/done list. You can see what todos are planned for the upcoming release, as well as ideas that may/may not make into a release in `Ideas`.
+
+## Ideas
+
+Unplanned.
+
+- [ ] Better style guide checking (#84)
+
+## main
+
+Released: TBA.
+[Diff](https://github.com/kvz/bash3boilerplate/compare/2.7.2...main).
+
+- [ ]
+
+## 2.7.2
+
+Released: 2023-08-29
+[Diff](https://github.com/kvz/bash3boilerplate/compare/v2.4.1...2.7.2).
+
+- [x] Upgrade and cleanup node dependencies
+- [x] Remove lanyon-based website in favor of simple redirect to github for bash3boilerplate.sh
+- [x] Make tests pass again
+- [x] Make linting and style checking separate actions
+- [x] Add feature to edit/update comments in ini file (#132, @rfuehrer)
+- [x] Upgrade to `lanyon@0.1.16`
+- [x] Capture correct error_code in err_report (#124, @eval)
+- [x] Enhanced ini file handling: create new file, create new sections, handle default section, read key from given section (@rfuehrer)
+
+## v2.4.2
+
+Released: 2019-11-07.
+[Diff](https://github.com/kvz/bash3boilerplate/compare/v2.4.1...v2.4.2).
+
+- [x] Upgrade to `lanyon@0.1.16`
+- [x] Capture correct error_code in err_report (#124, @eval)
+- [x] Enhanced ini file handling: create new file, create new sections, handle default section, read key from given section (@rfuehrer)
+
+## v2.4.1
+
+Released: 2019-11-07.
+[Diff](https://github.com/kvz/bash3boilerplate/compare/v2.3.0...v2.4.1).
+
+- [x] Upgrade to `lanyon@0.1.7`
+- [x] Allow counting how many times an argument is used (@genesiscloud)
+- [x] Fix typos in megamount (thanks @gsaponaro)
+- [x] Enable color in screen or tmux (#92, @gmasse)
+- [x] Change `egrep` to `grep -E` in test and lib scripts to comply with ShellCheck (#92, @gmasse)
+- [x] Fix typo in FAQ (#92, @gmasse)
+- [x] Fix Travis CI failure on src/templater.sh (@gmasse)
+- [x] Add magic variable which contains full command invocation
+- [x] More contrasted alert and emergency colors (#111 @gmeral)
+- [x] Add support for repeatable arguments (@genesiscloud)
+- [x] Fix remaining warnings with shellcheck v0.7.0 (#107, @genesiscloud)
+
+## v2.4.0
+
+Released: 2016-12-21.
+[Diff](https://github.com/kvz/bash3boilerplate/compare/v2.3.0...v2.4.0).
+
+- [x] Upgrade to `lanyon@0.0.143`
+
+## v2.3.0
+
+Released: 2016-12-21.
+[Diff](https://github.com/kvz/bash3boilerplate/compare/v2.2.0...v2.3.0).
+
+- [x] Add magic variable `__i_am_main_script` to distinguish if b3bp is being sourced or called directly (#45, @zbeekman)
+- [x] Add style checks for tab characters and trailing whitespace (@zbeekman)
+- [x] Add backtracing to help localize errors (#44, @zbeekman)
+- [x] Additional FAQ entries (#47, suggested by @gdevenyi, implemented by @zbeekman)
+- [x] Ensure that shifting over `--` doesn't throw an errexit error (#21, @zbeekman)
+- [x] Add Pull Request template (#83)
+
+## v2.2.0
+
+Released: 2016-12-21.
+[Diff](https://github.com/kvz/bash3boilerplate/compare/v2.1.0...v2.2.0).
+
+- [x] README and FAQ improvements (#66, @mstreuhofer)
+- [x] Add support for sourcing b3bp (#61, @mstreuhofer)
+- [x] Upgrade all Node.js dependencies for development (#78)
+- [x] Switch to http://lanyon.io for static site building, add a new logo
+- [x] Cleanup environment variables (#58, @mstreuhofer)
+- [x] Support multi-line logs (#57, @mstreuhofer)
+- [x] Run shellcheck as part of the acceptance test (#79, @mstreuhofer)
+- [x] Brace all variables, used `[[` instead of `[` (#33, #76, @mstreuhofer)
+- [x] Add automatic usage validation for required args (#22, #65, @mstreuhofer)
+- [x] Remove all usage of eval (@mstreuhofer)
+- [x] Get rid of awk, sed & egrep usage (#71, @mstreuhofer)
+- [x] Fix auto-color-off code (#69, #70, @mstreuhofer)
+- [x] Use shellcheck to find and fix unclean code (#68, #80, @mstreuhofer)
+- [x] Allow for multiline opt description in `__usage` (#7, @mstreuhofer)
+- [x] Allow `__usage` and `__helptext` to be defined before sourcing `main.sh` thus makeing b3bp behave like a library (@mstreuhofer)
+- [x] Add the same License text to each script header (@mstreuhofer)
+
+## v2.1.0
+
+Released: 2016-11-08.
+[Diff](https://github.com/kvz/bash3boilerplate/compare/v2.0.0...v2.1.0).
+
+- [x] Cleanup b3bp variables (adds prefixes across the board) (thanks @mstreuhofer)
+- [x] Add multi-line logging support (thanks @mstreuhofer)
+- [x] Mangle long-option names to allow dashes (thanks @zbeekman)
+- [x] Remove OS detection altogether (#38, thx @zbeekman)
+- [x] Offer the main template for download as http://bash3boilerplate.sh/main.sh
+- [x] Better OS detection (#38, thx @moviuro)
+- [x] Improve README copy (#34, thx galaktos)
+- [x] Fix unquoted variable access within (#34 thx galaktos)
+- [x] For delete-key-friendliness, bundle the commandline definition block along with its parser
+- [x] Less verbose header comments
+- [x] For delete-key-friendliness, don't crash on undeclared help vars
+- [x] Introduce `errtrace`, which is on by default (BREAKING)
+- [x] Add a configurable `helptext` that is left alone by the parses and allows you to have a richer help
+- [x] Add a simple documentation website
+- [x] Add best practice of using `__double_underscore_prefixed_vars` to indicate global variables that are solely controlled inside your script
+- [x] Make license more permissive by not requiring distribution of the LICENSE file if the copyright & attribution comments are left intact
+- [x] Respect `--no-color` by setting the `NO_COLOR` flag in `main.sh` (#25, thx @gdevenyi)
+- [x] Split out changelog into separate file
+- [x] Added a [FAQ](./FAQ.md) (#15, #14, thanks @rouson)
+- [x] Fix Travis OSX testing (before, it would silently pass failures) (#10)
+- [x] Enable dashes in long, GNU style options, as well as numbers (thanks @zbeekman)
+
+## v2.0.0
+
+Released: 2016-02-17.
+[Diff](https://github.com/kvz/bash3boilerplate/compare/v1.2.1...v2.0.0).
+
+- [x] Add tests for `templater` and follow Library export best practices
+- [x] Add tests for `ini_val` and follow Library export best practices
+- [x] Add tests for `parse_url` and follow Library export best practices
+- [x] Add tests for `megamount` and follow Library export best practices
+- [x] Remove `bump` from `src` (BREAKING)
+- [x] Remove `semver` from `src` (BREAKING)
+
+## v1.2.1
+
+Released: 2016-02-17.
+[Diff](https://github.com/kvz/bash3boilerplate/compare/v1.2.0...v1.2.1).
+
+- [x] Add Travis CI automated testing for OSX (thanks @zbeekman)
+
+## v1.2.0
+
+Released: 2016-02-16.
+[Diff](https://github.com/kvz/bash3boilerplate/compare/v1.1.0...v1.2.0).
+
+- [x] Allow disabling colors via `NO_COLOR` environment variable
+- [x] Enable `errexit`, `nounset` and `pipefail` options at the top of the script already
+- [x] More refined colors (thanks @arathai)
+- [x] Add a changelog to the README
+- [x] Add `__os` magic var (limited to discovering OSX and defaulting to Linux for now)
+- [x] Add `__base` magic var (`main`, if the source script is `main.sh`)
+- [x] Enable long, GNU style options (thanks @zbeekman)
+- [x] Add Travis CI automated testing for Linux
+
+## v1.1.0
+
+Released: 2015-06-29.
+[Diff](https://github.com/kvz/bash3boilerplate/compare/v1.0.3...v1.1.0).
+
+- [x] Add `ALLOW_REMAINDERS` configuration to templater
+- [x] Fix typo: 'debugmdoe' to 'debugmode' (thanks @jokajak)
+- [x] Use `${BASH_SOURCE[0]}` for `__file` instead of `${0}`
+
+## v1.0.3
+
+Released: 2014-11-02.
+[Diff](https://github.com/kvz/bash3boilerplate/compare/5db569125319a89b9561b434db84e4d91faefb63...v1.0.3).
+
+- [x] Add `ini_val`, `megamount`, `parse_url`
+- [x] Add re-usable libraries in `./src`
+- [x] Use npm as an additional distribution channel

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/FAQ.md

@@ -0,0 +1,171 @@
+[This document is formatted with GitHub-Flavored Markdown. ]: #
+[For better viewing, including hyperlinks, read it online at ]: #
+[https://github.com/kvz/bash3boilerplate/blob/HEAD/FAQ.md ]: #
+
+## Contents
+
+- [What is a CLI](#what-is-a-cli)?
+- [How do I incorporate BASH3 Boilerplate into my own project](#how-do-i-incorporate-bash3-boilerplate-into-my-own-project)?
+- [How do I add a command-line flag](#how-do-i-add-a-command-line-flag)?
+- [How do I access the value of a command-line argument](#how-do-i-access-the-value-of-a-command-line-argument)?
+- [What is a magic variable](#what-is-a-magic-variable)?
+- [How do I submit an issue report](#how-do-i-submit-an-issue-report)?
+- [How can I contribute to this project](#how-can-i-contribute-to-this-project)?
+- [Why are you typing BASH in all caps](#why-are-you-typing-bash-in-all-caps)?
+- [You are saying you are portable, but why won't b3bp code run in dash / busybox / posh / ksh / mksh / zsh](#you-are-saying-you-are-portable-but-why-wont-b3bp-code-run-in-dash--busybox--posh--ksh--mksh--zsh)?
+- [How do I do Operating System detection](#how-do-i-do-operating-system-detection)?
+- [How do I access a potentially unset (environment) variable](#how-do-i-access-a-potentially-unset-environment-variable)?
+- [How can I detect or trap CTRL-C and other signals](#how-can-i-detect-or-trap-ctrl-c-and-other-signals)?
+- [How can I get the PID of my running script](how-can-i-get-the-pid-of-my-running-script)?
+
+<!--more-->
+
+# Frequently Asked Questions
+
+## What is a CLI?
+
+A "CLI" is a [command-line interface](https://en.wikipedia.org/wiki/Command-line_interface).
+
+## How do I incorporate BASH3 Boilerplate into my own project?
+
+You can incorporate BASH3 Boilerplate into your project in one of two ways:
+
+1. Copy the desired portions of [`main.sh`](http://bash3boilerplate.sh/main.sh) into your own script.
+1. Download [`main.sh`](http://bash3boilerplate.sh/main.sh) and start pressing the delete-key to remove unwanted things
+
+Once the `main.sh` has been tailor-made for your project, you can either append your own script in the same file, or source it in the following ways:
+
+1. Copy [`main.sh`](http://bash3boilerplate.sh/main.sh) into the same directory as your script and then edit and embed it into your script using Bash's `source` include feature, e.g.:
+
+```bash
+#!/usr/bin/env bash
+source main.sh
+```
+
+1. Source [`main.sh`](http://bash3boilerplate.sh/main.sh) in your script or at the command line:
+
+```bash
+#!/usr/bin/env bash
+source main.sh
+```
+
+## How do I add a command-line flag?
+
+1. Copy the line from the `main.sh` [read block](https://github.com/kvz/bash3boilerplate/blob/v2.1.0/main.sh#L109-L115) that most resembles the desired behavior and paste the line into the same block.
+1. Edit the single-character (e.g., `-d`) and, if present, the multi-character (e.g., `--debug`) versions of the flag in the copied line.
+1. Omit the `[arg]` text in the copied line, if the desired flag takes no arguments.
+1. Omit or edit the text after `Default=` to set or not set default values, respectively.
+1. Omit the `Required.` text, if the flag is optional.
+
+## How do I access the value of a command-line argument?
+
+To find out the value of an argument, append the corresponding single-character flag to the text `$arg_`. For example, if the [read block]
+contains the line
+
+```bash
+   -t --temp  [arg] Location of tempfile. Default="/tmp/bar"
+```
+
+then you can evaluate the corresponding argument and assign it to a variable as follows:
+
+```bash
+__temp_file_name="${arg_t}"
+```
+
+## What is a magic variable?
+
+The [magic variables](https://github.com/kvz/bash3boilerplate/blob/v2.1.0/main.sh#L26-L28) in `main.sh` are special in that they have a different value, depending on your environment. You can use `${__file}` to get a reference to your current script, and `${__dir}` to get a reference to the directory it lives in. This is not to be confused with the location of the calling script that might be sourcing the `${__file}`, which is accessible via `${0}`, or the current directory of the administrator running the script, accessible via `$(pwd)`.
+
+## How do I submit an issue report?
+
+Please visit our [Issues](https://github.com/kvz/bash3boilerplate/issues) page.
+
+## How can I contribute to this project?
+
+Please fork this repository. After that, create a branch containing your suggested changes and submit a pull request based on the main branch
+of <https://github.com/kvz/bash3boilerplate/>. We are always more than happy to accept your contributions!
+
+## Why are you typing BASH in all caps?
+
+As an acronym, Bash stands for Bourne-again shell, and is usually written with one uppercase.
+This project's name, however, is "BASH3 Boilerplate". It is a reference to
+"[HTML5 Boilerplate](https://html5boilerplate.com/)", which was founded to serve a similar purpose,
+only for crafting webpages.
+Somewhat inconsistent – but true to Unix ancestry – the abbreviation for our project is "b3bp".
+
+## You are saying you are portable, but why won't b3bp code run in dash / busybox / posh / ksh / mksh / zsh?
+
+When we say _portable_, we mean across Bash versions. Bash is widespread and most systems
+offer at least version 3 of it. Make sure you have that available and b3bp will work for you.
+
+We run automated tests to make sure that it will. Here is some proof for the following platforms:
+
+- [Linux](https://travis-ci.org/kvz/bash3boilerplate/jobs/109804166#L91-L94) `GNU bash, version 4.2.25(1)-release (x86_64-pc-linux-gnu)`
+- [OSX](https://travis-ci.org/kvz/bash3boilerplate/jobs/109804167#L2453-L2455) `GNU bash, version 3.2.51(1)-release (x86_64-apple-darwin13)`
+
+This portability, however, does not mean that we try to be compatible with
+KornShell, Zsh, posh, yash, dash, or other shells. We allow syntax that would explode if
+you pasted it in anything but Bash 3 and up.
+
+## How do I do Operating System detection?
+
+We used to offer a magic `__os` variable, but we quickly [discovered](https://github.com/kvz/bash3boilerplate/issues/38) that it would be hard
+to create a satisfactory abstraction that is not only correct, but also covers enough use-cases,
+while still having a relatively small footprint in `main.sh`.
+
+For simple OS detection, we recommend using the `${OSTYPE}` variable available in Bash as
+is demoed in [this stackoverflow post](http://stackoverflow.com/a/8597411/151666):
+
+```bash
+if [[ "${OSTYPE}" = "linux-gnu" ]]; then
+  echo "GNU Linux"
+elif [[ "${OSTYPE}" = "darwin"* ]]; then
+  echo "Mac OSX"
+elif [[ "${OSTYPE}" = "cygwin" ]]; then
+  echo "POSIX compatibility layer and Linux environment emulation for Windows"
+elif [[ "${OSTYPE}" = "msys" ]]; then
+  echo "Lightweight shell and GNU utilities compiled for Windows (part of MinGW)"
+elif [[ "${OSTYPE}" = "win32" ]]; then
+  echo "I'm not sure this can happen."
+elif [[ "${OSTYPE}" = "freebsd"* ]]; then
+  echo "..."
+else
+  echo "Unknown."
+fi
+```
+
+## How do I access a potentially unset (environment) variable?
+
+The set -o nounset line in `main.sh` causes error termination when an unset environment variables is detected as unbound. There are multiple ways to avoid this.
+
+Some code to illustrate:
+
+```bash
+# method 1
+echo ${NAME1:-Damian} # echos Damian, $NAME1 is still unset
+# method 2
+echo ${NAME2:=Damian} # echos Damian, $NAME2 is set to Damian
+# method 3
+NAME3=${NAME3:-Damian}; echo ${NAME3} # echos Damian, $NAME3 is set to Damian
+```
+
+This subject is briefly touched on as well in the [Safety and Portability section under point 5](README.md#safety-and-portability). b3bp currently uses [method 1](https://github.com/kvz/bash3boilerplate/blob/v2.1.0/main.sh#L252) when we want to access a variable that could be undeclared, and [method 3](https://github.com/kvz/bash3boilerplate/blob/v2.1.0/main.sh#L31) when we also want to set a default to an undeclared variable, because we feel it is more readable than method 2. We feel `:=` is easily overlooked, and not very beginner friendly. Method 3 seems more explicit in that regard in our humble opinion.
+
+## How can I detect or trap Ctrl-C and other signals?
+
+You can trap [Unix signals](https://en.wikipedia.org/wiki/Unix_signal) like [Ctrl-C](https://en.wikipedia.org/wiki/Control-C) with code similar to:
+
+```bash
+# trap ctrl-c and call ctrl_c()
+trap ctrl_c INT
+
+function ctrl_c() {
+        echo "** Trapped CTRL-C"
+}
+```
+
+See http://mywiki.wooledge.org/SignalTrap for a list of signals, examples, and an in depth discussion.
+
+## How can I get the PID of my running script?
+
+The PID of a running script is contained in the `${$}` variable. This is _not_ the pid of any subshells. With Bash 4 you can get the PID of your subshell with `${BASHPID}`. For a comprehensive list of Bash built in variables see, e.g., http://www.tldp.org/LDP/abs/html/internalvariables.html

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/LICENSE

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2013 Kevin van Zonneveld and contributors
+
+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 above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+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.

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/Makefile

@@ -0,0 +1,59 @@
+# Licensed under MIT.
+# Copyright (2016) by Kevin van Zonneveld https://twitter.com/kvz
+#
+# https://www.npmjs.com/package/fakefile
+#
+# Please do not edit this file directly, but propose changed upstream instead:
+# https://github.com/kvz/fakefile/blob/main/Makefile
+#
+# This Makefile offers convience shortcuts into any Node.js project that utilizes npm scripts.
+# It functions as a wrapper around the actual listed in `package.json`
+# So instead of typing:
+#
+#  $ npm script build:assets
+#
+# you could also type:
+#
+#  $ make build-assets
+#
+# Notice that colons (:) are replaced by dashes for Makefile compatibility.
+#
+# The benefits of this wrapper are:
+#
+# - You get to keep the the scripts package.json, which is more portable
+#   (Makefiles & Windows are harder to mix)
+# - Offer a polite way into the project for developers coming from different
+#   languages (npm scripts is obviously very Node centric)
+# - Profit from better autocomplete (make <TAB><TAB>) than npm currently offers.
+#   OSX users will have to install bash-completion
+#   (http://davidalger.com/development/bash-completion-on-os-x-with-brew/)
+
+ifeq ($(shell test -e ./yarn.lock && echo -n yes),yes)
+	RUNNER=yarn
+	INSTALLER=yarn install
+else
+	RUNNER=npm run
+	INSTALLER=npm install
+endif
+
+define npm_script_targets
+TARGETS := $(shell \
+	node -e 'for (var k in require("./package.json").scripts) {console.log(k.replace(/:/g, "-"));}'
+		| grep -v -E "^install$$"
+)
+$$(TARGETS):
+	$(RUNNER) $(shell \
+							node -e 'for (var k in require("./package.json").scripts) {console.log(k.replace(/:/g, "-"), k);}'
+								| grep -E "^$(MAKECMDGOALS)\s"
+								| head -n1
+								| awk '{print $$2}'
+							)
+
+.PHONY: $$(TARGETS)
+endef
+
+$(eval $(call npm_script_targets))
+
+# These npm run scripts are available, without needing to be mentioned in `package.json`
+install:
+	$(INSTALLER)

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/README.md

@@ -0,0 +1,175 @@
+[This document is formatted with GitHub-Flavored Markdown. ]: #
+[For better viewing, including hyperlinks, read it online at ]: #
+[https://github.com/kvz/bash3boilerplate/blob/HEAD/README.md]: #
+
+- [Overview](#overview)
+- [Goals](#goals)
+- [Features](#features)
+- [Installation](#installation)
+- [Changelog](#changelog)
+- [Frequently Asked Questions](#frequently-asked-questions)
+- [Best Practices](#best-practices)
+- [Who uses b3bp](#who-uses-b3bp)
+- [Authors](#authors)
+- [License](#license)
+
+## Overview
+
+<!--more-->
+
+When hacking up Bash scripts, there are often things such as logging or command-line argument parsing that:
+
+- You need every time
+- Come with a number of pitfalls you want to avoid
+- Keep you from your actual work
+
+Here's an attempt to bundle those things in a generalized way so that
+they are reusable as-is in most scripts.
+
+We call it "BASH3 Boilerplate" or b3bp for short.
+
+## Goals
+
+Delete-Key-**Friendly**. Instead of introducing packages, includes, compilers, etc., we propose using [`main.sh`](https://bash3boilerplate.sh/main.sh) as a base and removing the parts you don't need.
+While this may feel a bit archaic at first, it is exactly the strength of Bash scripts that we should want to embrace.
+
+**Portable**. We are targeting Bash 3 (OSX still ships
+with 3, for instance). If you are going to ask people to install
+Bash 4 first, you might as well pick a more advanced language as a
+dependency.
+
+## Features
+
+- Conventions that will make sure that all your scripts follow the same, battle-tested structure
+- Safe by default (break on error, pipefail, etc.)
+- Configuration by environment variables
+- Simple command-line argument parsing that requires no external dependencies. Definitions are parsed from help info, ensuring there will be no duplication
+- Helpful magic variables like `__file` and `__dir`
+- Logging that supports colors and is compatible with [Syslog Severity levels](https://en.wikipedia.org/wiki/Syslog#Severity_levels), as well as the [twelve-factor](https://12factor.net/) guidelines
+
+## Installation
+
+There are three different ways to install b3bp:
+
+### Option 1: Download the main template
+
+Use curl or wget to download the source and save it as your script. Then you can start deleting the unwanted bits, and adding your own logic.
+
+```bash
+wget https://bash3boilerplate.sh/main.sh
+vim main.sh
+```
+
+### Option 2: Clone the entire project
+
+Besides `main.sh`, this will also get you the entire b3bp repository. This includes a few extra functions that we keep in the `./src` directory.
+
+```bash
+git clone git@github.com:kvz/bash3boilerplate.git
+```
+
+### Option 3: Require via npm
+
+As of `v1.0.3`, b3bp can also be installed as a Node module, meaning you can define it as a dependency in `package.json` via:
+
+```bash
+npm init
+npm install --save --save-exact bash3boilerplate
+```
+
+Even though this option introduces a Node.js dependency, it does allow for easy version pinning and distribution in environments that already have this prerequisite. This is, however, entirely optional and nothing prevents you from ignoring this possibility.
+
+## Changelog
+
+Please see the [CHANGELOG.md](./CHANGELOG.md) file.
+
+## Frequently Asked Questions
+
+Please see the [FAQ.md](./FAQ.md) file.
+
+## Best practices
+
+As of `v1.0.3`, b3bp offers some nice re-usable libraries in `./src`. In order to make the snippets in `./src` more useful, we recommend the following guidelines.
+
+### Function packaging
+
+It is nice to have a Bash package that can not only be used in the terminal, but also invoked as a command line function. In order to achieve this, the exporting of your functionality _should_ follow this pattern:
+
+```bash
+if [[ "${BASH_SOURCE[0]}" = "${0}" ]]; then
+  my_script "${@}"
+  exit $?
+fi
+export -f my_script
+```
+
+This allows a user to `source` your script or invoke it as a script.
+
+```bash
+# Running as a script
+$ ./my_script.sh some args --blah
+# Sourcing the script
+$ source my_script.sh
+$ my_script some more args --blah
+```
+
+(taken from the [bpkg](https://raw.githubusercontent.com/bpkg/bpkg/HEAD/README.md) project)
+
+### Scoping
+
+1. In functions, use `local` before every variable declaration.
+1. Use `UPPERCASE_VARS` to indicate environment variables that can be controlled outside your script.
+1. Use `__double_underscore_prefixed_vars` to indicate global variables that are solely controlled inside your script, with the exception of arguments that are already prefixed with `arg_`, as well as functions, over which b3bp poses no restrictions.
+
+### Coding style
+
+1. Use two spaces for tabs, do not use tab characters.
+1. Do not introduce whitespace at the end of lines or on blank lines as they obfuscate version control diffs.
+1. Use long options (`logger --priority` vs `logger -p`). If you are on the CLI, abbreviations make sense for efficiency. Nevertheless, when you are writing reusable scripts, a few extra keystrokes will pay off in readability and avoid ventures into man pages in the future, either by you or your collaborators. Similarly, we prefer `set -o nounset` over `set -u`.
+1. Use a single equal sign when checking `if [[ "${NAME}" = "Kevin" ]]`; double or triple signs are not needed.
+1. Use the new bash builtin test operator (`[[ ... ]]`) rather than the old single square bracket test operator or explicit call to `test`.
+
+### Safety and Portability
+
+1. Use `{}` to enclose your variables. Otherwise, Bash will try to access the `$ENVIRONMENT_app` variable in `/srv/$ENVIRONMENT_app`, whereas you probably intended `/srv/${ENVIRONMENT}_app`. Since it is easy to miss cases like this, we recommend that you make enclosing a habit.
+1. Use `set`, rather than relying on a shebang like `#!/usr/bin/env bash -e`, since that is neutralized when someone runs your script as `bash yourscript.sh`.
+1. Use `#!/usr/bin/env bash`, as it is more portable than `#!/bin/bash`.
+1. Use `${BASH_SOURCE[0]}` if you refer to current file, even if it is sourced by a parent script. In other cases, use `${0}`.
+1. Use `:-` if you want to test variables that could be undeclared. For instance, with `if [[ "${NAME:-}" = "Kevin" ]]`, `$NAME` will evaluate to `Kevin` if the variable is empty. The variable itself will remain unchanged. The syntax to assign a default value is `${NAME:=Kevin}`.
+
+## Who uses b3bp?
+
+- [Transloadit](https://transloadit.com)
+- [OpenCoarrays](https://www.opencoarrays.org)
+- [Sourcery Institute](https://www.sourceryinstitute.org)
+- [Computational Brain Anatomy Laboratory](https://cobralab.ca/)
+- [Genesis Cloud](https://genesiscloud.com/)
+
+We are looking for endorsements! Are you also using b3bp? [Let us know](https://github.com/kvz/bash3boilerplate/issues/new?title=I%20use%20b3bp) and get listed.
+
+## Authors
+
+- [Kevin van Zonneveld](https://kvz.io)
+- [Izaak Beekman](https://izaakbeekman.com/)
+- [Manuel Streuhofer](https://github.com/mstreuhofer)
+- [Alexander Rathai](mailto:Alexander.Rathai@gmail.com)
+- [Dr. Damian Rouson](https://www.sourceryinstitute.org/) (documentation, feedback)
+- [@jokajak](https://github.com/jokajak) (documentation)
+- [Gabriel A. Devenyi](https://staticwave.ca/) (feedback)
+- [@bravo-kernel](https://github.com/bravo-kernel) (feedback)
+- [@skanga](https://github.com/skanga) (feedback)
+- [galaktos](https://www.reddit.com/user/galaktos) (feedback)
+- [@moviuro](https://github.com/moviuro) (feedback)
+- [Giovanni Saponaro](https://github.com/gsaponaro) (feedback)
+- [Germain Masse](https://github.com/gmasse)
+- [A. G. Madi](https://github.com/warpengineer)
+- [Lukas Stockner](mailto:oss@genesiscloud.com)
+- [Gert Goet](https://github.com/eval)
+- [@rfuehrer](https://github.com/rfuehrer)
+
+## License
+
+Copyright (c) 2013 Kevin van Zonneveld and [contributors](https://github.com/kvz/bash3boilerplate#authors).
+Licensed under [MIT](https://raw.githubusercontent.com/kvz/bash3boilerplate/HEAD/LICENSE).
+You are not obligated to bundle the LICENSE file with your b3bp projects as long
+as you leave these references intact in the header comments of your source files.

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/docs/CNAME

@@ -0,0 +1 @@
+bash3boilerplate.sh

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/docs/index.html

@@ -0,0 +1,15 @@
+<!DOCTYPE html>
+<html lang="en">
+  <head>
+    <meta charset="UTF-8" />
+    <meta
+      http-equiv="refresh"
+      content="0;url=https://github.com/kvz/bash3boilerplate"
+    />
+    <title>Redirecting...</title>
+  </head>
+  <body>
+    If you are not redirected,
+    <a href="https://github.com/kvz/bash3boilerplate">click here</a>.
+  </body>
+</html>

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/example.sh

@@ -0,0 +1,147 @@
+#!/usr/bin/env bash
+# This file:
+#
+#  - Demos BASH3 Boilerplate (change this for your script)
+#
+# Usage:
+#
+#  LOG_LEVEL=7 ./example.sh -f /tmp/x -d (change this for your script)
+#
+# Based on a template by BASH3 Boilerplate v2.3.0
+# http://bash3boilerplate.sh/#authors
+#
+# The MIT License (MIT)
+# Copyright (c) 2013 Kevin van Zonneveld and contributors
+# You are not obligated to bundle the LICENSE file with your b3bp projects as long
+# as you leave these references intact in the header comments of your source files.
+
+
+### BASH3 Boilerplate (b3bp) Header
+##############################################################################
+
+# Commandline options. This defines the usage page, and is used to parse cli
+# opts & defaults from. The parsing is unforgiving so be precise in your syntax
+# - A short option must be preset for every long option; but every short option
+#   need not have a long option
+# - `--` is respected as the separator between options and arguments
+# - We do not bash-expand defaults, so setting '~/app' as a default will not resolve to ${HOME}.
+#   you can use bash variables to work around this (so use ${HOME} instead)
+
+# shellcheck disable=SC2034
+read -r -d '' __usage <<-'EOF' || true # exits non-zero when EOF encountered
+  -f --file  [arg] Filename to process. Required.
+  -t --temp  [arg] Location of tempfile. Default="/tmp/bar"
+  -v               Enable verbose mode, print script as it is executed
+  -d --debug       Enables debug mode
+  -h --help        This page
+  -n --no-color    Disable color output
+  -1 --one         Do just one thing
+  -i --input [arg] File to process. Can be repeated.
+  -x               Specify a flag. Can be repeated.
+EOF
+
+# shellcheck disable=SC2034
+read -r -d '' __helptext <<-'EOF' || true # exits non-zero when EOF encountered
+ This is Bash3 Boilerplate's help text. Feel free to add any description of your
+ program or elaborate more on command-line arguments. This section is not
+ parsed and will be added as-is to the help.
+EOF
+
+# shellcheck source=main.sh
+source "$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)/main.sh"
+
+
+### Signal trapping and backtracing
+##############################################################################
+
+function __b3bp_cleanup_before_exit () {
+  info "Cleaning up. Done"
+}
+trap __b3bp_cleanup_before_exit EXIT
+
+# requires `set -o errtrace`
+__b3bp_err_report() {
+    local error_code=${?}
+    # shellcheck disable=SC2154
+    error "Error in ${__file} in function ${1} on line ${2}"
+    exit ${error_code}
+}
+# Uncomment the following line for always providing an error backtrace
+# trap '__b3bp_err_report "${FUNCNAME:-.}" ${LINENO}' ERR
+
+
+### Command-line argument switches (like -d for debugmode, -h for showing helppage)
+##############################################################################
+
+# debug mode
+if [[ "${arg_d:?}" = "1" ]]; then
+  set -o xtrace
+  PS4='+(${BASH_SOURCE}:${LINENO}): ${FUNCNAME[0]:+${FUNCNAME[0]}(): }'
+  LOG_LEVEL="7"
+  # Enable error backtracing
+  trap '__b3bp_err_report "${FUNCNAME:-.}" ${LINENO}' ERR
+fi
+
+# verbose mode
+if [[ "${arg_v:?}" = "1" ]]; then
+  set -o verbose
+fi
+
+# no color mode
+if [[ "${arg_n:?}" = "1" ]]; then
+  NO_COLOR="true"
+fi
+
+# help mode
+if [[ "${arg_h:?}" = "1" ]]; then
+  # Help exists with code 1
+  help "Help using ${0}"
+fi
+
+
+### Validation. Error out if the things required for your script are not present
+##############################################################################
+
+[[ "${arg_f:-}" ]]     || help      "Setting a filename with -f or --file is required"
+[[ "${LOG_LEVEL:-}" ]] || emergency "Cannot continue without LOG_LEVEL. "
+
+
+### Runtime
+##############################################################################
+
+# shellcheck disable=SC2154
+info "__i_am_main_script: ${__i_am_main_script}"
+# shellcheck disable=SC2154
+info "__file: ${__file}"
+# shellcheck disable=SC2154
+info "__dir: ${__dir}"
+# shellcheck disable=SC2154
+info "__base: ${__base}"
+info "OSTYPE: ${OSTYPE}"
+
+info "arg_f: ${arg_f}"
+info "arg_d: ${arg_d}"
+info "arg_v: ${arg_v}"
+info "arg_h: ${arg_h}"
+if [[ -n "${arg_i:-}" ]]; then
+  info "arg_i: ${#arg_i[@]}"
+  for input_file in "${arg_i[@]}"; do
+    info " - ${input_file}"
+  done
+else
+  info "arg_i: 0"
+fi
+# shellcheck disable=SC2015
+[[ -n "${arg_x:-}" ]] && info "arg_x: ${#arg_x[@]}" || info "arg_x: 0"
+
+info "$(echo -e "multiple lines example - line #1\\nmultiple lines example - line #2\\nimagine logging the output of 'ls -al /path/'")"
+
+# All of these go to STDERR, so you can use STDOUT for piping machine readable information to other software
+debug "Info useful to developers for debugging the application, not useful during operations."
+info "Normal operational messages - may be harvested for reporting, measuring throughput, etc. - no action required."
+notice "Events that are unusual but not error conditions - might be summarized in an email to developers or admins to spot potential problems - no immediate action required."
+warning "Warning messages, not an error, but indication that an error will occur if action is not taken, e.g. file system 85% full - each item must be resolved within a given time."
+error "Non-urgent failures, these should be relayed to developers or admins; each item must be resolved within a given time."
+critical "Should be corrected immediately, but indicates failure in a primary system, an example is a loss of a backup ISP connection."
+alert "Should be corrected immediately, therefore notify staff who can fix the problem. An example would be the loss of a primary ISP connection."
+emergency "A \"panic\" condition usually affecting multiple apps/servers/sites. At this level it would usually notify all tech staff on call."

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/main.sh

@@ -0,0 +1,453 @@
+#!/usr/bin/env bash
+# This file:
+#
+#  - Demos BASH3 Boilerplate (change this for your script)
+#
+# Usage:
+#
+#  LOG_LEVEL=7 ./main.sh -f /tmp/x -d (change this for your script)
+#
+# Based on a template by BASH3 Boilerplate vv2.7.2
+# http://bash3boilerplate.sh/#authors
+#
+# The MIT License (MIT)
+# Copyright (c) 2013 Kevin van Zonneveld and contributors
+# You are not obligated to bundle the LICENSE file with your b3bp projects as long
+# as you leave these references intact in the header comments of your source files.
+
+# Exit on error. Append "|| true" if you expect an error.
+set -o errexit
+# Exit on error inside any functions or subshells.
+set -o errtrace
+# Do not allow use of undefined vars. Use ${VAR:-} to use an undefined VAR
+set -o nounset
+# Catch the error in case mysqldump fails (but gzip succeeds) in `mysqldump |gzip`
+set -o pipefail
+# Turn on traces, useful while debugging but commented out by default
+# set -o xtrace
+
+if [[ "${BASH_SOURCE[0]}" != "${0}" ]]; then
+  __i_am_main_script="0" # false
+
+  if [[ "${__usage+x}" ]]; then
+    if [[ "${BASH_SOURCE[1]}" = "${0}" ]]; then
+      __i_am_main_script="1" # true
+    fi
+
+    __b3bp_external_usage="true"
+    __b3bp_tmp_source_idx=1
+  fi
+else
+  __i_am_main_script="1" # true
+  [[ "${__usage+x}" ]] && unset -v __usage
+  [[ "${__helptext+x}" ]] && unset -v __helptext
+fi
+
+# Set magic variables for current file, directory, os, etc.
+__dir="$(cd "$(dirname "${BASH_SOURCE[${__b3bp_tmp_source_idx:-0}]}")" && pwd)"
+__file="${__dir}/$(basename "${BASH_SOURCE[${__b3bp_tmp_source_idx:-0}]}")"
+__base="$(basename "${__file}" .sh)"
+# shellcheck disable=SC2034,SC2015
+__invocation="$(printf %q "${__file}")$( (($#)) && printf ' %q' "$@" || true)"
+
+# Define the environment variables (and their defaults) that this script depends on
+LOG_LEVEL="${LOG_LEVEL:-6}" # 7 = debug -> 0 = emergency
+NO_COLOR="${NO_COLOR:-}"    # true = disable color. otherwise autodetected
+
+
+### Functions
+##############################################################################
+
+function __b3bp_log () {
+  local log_level="${1}"
+  shift
+
+  # shellcheck disable=SC2034
+  local color_debug="\\x1b[35m"
+  # shellcheck disable=SC2034
+  local color_info="\\x1b[32m"
+  # shellcheck disable=SC2034
+  local color_notice="\\x1b[34m"
+  # shellcheck disable=SC2034
+  local color_warning="\\x1b[33m"
+  # shellcheck disable=SC2034
+  local color_error="\\x1b[31m"
+  # shellcheck disable=SC2034
+  local color_critical="\\x1b[1;31m"
+  # shellcheck disable=SC2034
+  local color_alert="\\x1b[1;37;41m"
+  # shellcheck disable=SC2034
+  local color_emergency="\\x1b[1;4;5;37;41m"
+
+  local colorvar="color_${log_level}"
+
+  local color="${!colorvar:-${color_error}}"
+  local color_reset="\\x1b[0m"
+
+  if [[ "${NO_COLOR:-}" = "true" ]] || { [[ "${TERM:-}" != "xterm"* ]] && [[ "${TERM:-}" != "screen"* ]]; } || [[ ! -t 2 ]]; then
+    if [[ "${NO_COLOR:-}" != "false" ]]; then
+      # Don't use colors on pipes or non-recognized terminals
+      color=""; color_reset=""
+    fi
+  fi
+
+  # all remaining arguments are to be printed
+  local log_line=""
+
+  while IFS=$'\n' read -r log_line; do
+    echo -e "$(date -u +"%Y-%m-%d %H:%M:%S UTC") ${color}$(printf "[%9s]" "${log_level}")${color_reset} ${log_line}" 1>&2
+  done <<< "${@:-}"
+}
+
+function emergency () {                                __b3bp_log emergency "${@}"; exit 1; }
+function alert ()     { [[ "${LOG_LEVEL:-0}" -ge 1 ]] && __b3bp_log alert "${@}"; true; }
+function critical ()  { [[ "${LOG_LEVEL:-0}" -ge 2 ]] && __b3bp_log critical "${@}"; true; }
+function error ()     { [[ "${LOG_LEVEL:-0}" -ge 3 ]] && __b3bp_log error "${@}"; true; }
+function warning ()   { [[ "${LOG_LEVEL:-0}" -ge 4 ]] && __b3bp_log warning "${@}"; true; }
+function notice ()    { [[ "${LOG_LEVEL:-0}" -ge 5 ]] && __b3bp_log notice "${@}"; true; }
+function info ()      { [[ "${LOG_LEVEL:-0}" -ge 6 ]] && __b3bp_log info "${@}"; true; }
+function debug ()     { [[ "${LOG_LEVEL:-0}" -ge 7 ]] && __b3bp_log debug "${@}"; true; }
+
+function help () {
+  echo "" 1>&2
+  echo " ${*}" 1>&2
+  echo "" 1>&2
+  echo "  ${__usage:-No usage available}" 1>&2
+  echo "" 1>&2
+
+  if [[ "${__helptext:-}" ]]; then
+    echo " ${__helptext}" 1>&2
+    echo "" 1>&2
+  fi
+
+  exit 1
+}
+
+
+### Parse commandline options
+##############################################################################
+
+# Commandline options. This defines the usage page, and is used to parse cli
+# opts & defaults from. The parsing is unforgiving so be precise in your syntax
+# - A short option must be preset for every long option; but every short option
+#   need not have a long option
+# - `--` is respected as the separator between options and arguments
+# - We do not bash-expand defaults, so setting '~/app' as a default will not resolve to ${HOME}.
+#   you can use bash variables to work around this (so use ${HOME} instead)
+
+# shellcheck disable=SC2015
+[[ "${__usage+x}" ]] || read -r -d '' __usage <<-'EOF' || true # exits non-zero when EOF encountered
+  -f --file  [arg] Filename to process. Required.
+  -t --temp  [arg] Location of tempfile. Default="/tmp/bar"
+  -v               Enable verbose mode, print script as it is executed
+  -d --debug       Enables debug mode
+  -h --help        This page
+  -n --no-color    Disable color output
+  -1 --one         Do just one thing
+  -i --input [arg] File to process. Can be repeated.
+  -x               Specify a flag. Can be repeated.
+EOF
+
+# shellcheck disable=SC2015
+[[ "${__helptext+x}" ]] || read -r -d '' __helptext <<-'EOF' || true # exits non-zero when EOF encountered
+ This is Bash3 Boilerplate's help text. Feel free to add any description of your
+ program or elaborate more on command-line arguments. This section is not
+ parsed and will be added as-is to the help.
+EOF
+
+# Translate usage string -> getopts arguments, and set $arg_<flag> defaults
+while read -r __b3bp_tmp_line; do
+  if [[ "${__b3bp_tmp_line}" =~ ^- ]]; then
+    # fetch single character version of option string
+    __b3bp_tmp_opt="${__b3bp_tmp_line%% *}"
+    __b3bp_tmp_opt="${__b3bp_tmp_opt:1}"
+
+    # fetch long version if present
+    __b3bp_tmp_long_opt=""
+
+    if [[ "${__b3bp_tmp_line}" = *"--"* ]]; then
+      __b3bp_tmp_long_opt="${__b3bp_tmp_line#*--}"
+      __b3bp_tmp_long_opt="${__b3bp_tmp_long_opt%% *}"
+    fi
+
+    # map opt long name to+from opt short name
+    printf -v "__b3bp_tmp_opt_long2short_${__b3bp_tmp_long_opt//-/_}" '%s' "${__b3bp_tmp_opt}"
+    printf -v "__b3bp_tmp_opt_short2long_${__b3bp_tmp_opt}" '%s' "${__b3bp_tmp_long_opt//-/_}"
+
+    # check if option takes an argument
+    if [[ "${__b3bp_tmp_line}" =~ \[.*\] ]]; then
+      __b3bp_tmp_opt="${__b3bp_tmp_opt}:" # add : if opt has arg
+      __b3bp_tmp_init=""  # it has an arg. init with ""
+      printf -v "__b3bp_tmp_has_arg_${__b3bp_tmp_opt:0:1}" '%s' "1"
+    elif [[ "${__b3bp_tmp_line}" =~ \{.*\} ]]; then
+      __b3bp_tmp_opt="${__b3bp_tmp_opt}:" # add : if opt has arg
+      __b3bp_tmp_init=""  # it has an arg. init with ""
+      # remember that this option requires an argument
+      printf -v "__b3bp_tmp_has_arg_${__b3bp_tmp_opt:0:1}" '%s' "2"
+    else
+      __b3bp_tmp_init="0" # it's a flag. init with 0
+      printf -v "__b3bp_tmp_has_arg_${__b3bp_tmp_opt:0:1}" '%s' "0"
+    fi
+    __b3bp_tmp_opts="${__b3bp_tmp_opts:-}${__b3bp_tmp_opt}"
+
+    if [[ "${__b3bp_tmp_line}" =~ ^Can\ be\ repeated\. ]] || [[ "${__b3bp_tmp_line}" =~ \.\ *Can\ be\ repeated\. ]]; then
+      # remember that this option can be repeated
+      printf -v "__b3bp_tmp_is_array_${__b3bp_tmp_opt:0:1}" '%s' "1"
+    else
+      printf -v "__b3bp_tmp_is_array_${__b3bp_tmp_opt:0:1}" '%s' "0"
+    fi
+  fi
+
+  [[ "${__b3bp_tmp_opt:-}" ]] || continue
+
+  if [[ "${__b3bp_tmp_line}" =~ ^Default= ]] || [[ "${__b3bp_tmp_line}" =~ \.\ *Default= ]]; then
+    # ignore default value if option does not have an argument
+    __b3bp_tmp_varname="__b3bp_tmp_has_arg_${__b3bp_tmp_opt:0:1}"
+    if [[ "${!__b3bp_tmp_varname}" != "0" ]]; then
+      # take default
+      __b3bp_tmp_init="${__b3bp_tmp_line##*Default=}"
+      # strip double quotes from default argument
+      __b3bp_tmp_re='^"(.*)"$'
+      if [[ "${__b3bp_tmp_init}" =~ ${__b3bp_tmp_re} ]]; then
+        __b3bp_tmp_init="${BASH_REMATCH[1]}"
+      else
+        # strip single quotes from default argument
+        __b3bp_tmp_re="^'(.*)'$"
+        if [[ "${__b3bp_tmp_init}" =~ ${__b3bp_tmp_re} ]]; then
+          __b3bp_tmp_init="${BASH_REMATCH[1]}"
+        fi
+      fi
+    fi
+  fi
+
+  if [[ "${__b3bp_tmp_line}" =~ ^Required\. ]] || [[ "${__b3bp_tmp_line}" =~ \.\ *Required\. ]]; then
+    # remember that this option requires an argument
+    printf -v "__b3bp_tmp_has_arg_${__b3bp_tmp_opt:0:1}" '%s' "2"
+  fi
+
+  # Init var with value unless it is an array / a repeatable
+  __b3bp_tmp_varname="__b3bp_tmp_is_array_${__b3bp_tmp_opt:0:1}"
+  [[ "${!__b3bp_tmp_varname}" = "0" ]] && printf -v "arg_${__b3bp_tmp_opt:0:1}" '%s' "${__b3bp_tmp_init}"
+done <<< "${__usage:-}"
+
+# run getopts only if options were specified in __usage
+if [[ "${__b3bp_tmp_opts:-}" ]]; then
+  # Allow long options like --this
+  __b3bp_tmp_opts="${__b3bp_tmp_opts}-:"
+
+  # Reset in case getopts has been used previously in the shell.
+  OPTIND=1
+
+  # start parsing command line
+  set +o nounset # unexpected arguments will cause unbound variables
+                 # to be dereferenced
+  # Overwrite $arg_<flag> defaults with the actual CLI options
+  while getopts "${__b3bp_tmp_opts}" __b3bp_tmp_opt; do
+    [[ "${__b3bp_tmp_opt}" = "?" ]] && help "Invalid use of script: ${*} "
+
+    if [[ "${__b3bp_tmp_opt}" = "-" ]]; then
+      # OPTARG is long-option-name or long-option=value
+      if [[ "${OPTARG}" =~ .*=.* ]]; then
+        # --key=value format
+        __b3bp_tmp_long_opt=${OPTARG/=*/}
+        # Set opt to the short option corresponding to the long option
+        __b3bp_tmp_varname="__b3bp_tmp_opt_long2short_${__b3bp_tmp_long_opt//-/_}"
+        printf -v "__b3bp_tmp_opt" '%s' "${!__b3bp_tmp_varname}"
+        OPTARG=${OPTARG#*=}
+      else
+        # --key value format
+        # Map long name to short version of option
+        __b3bp_tmp_varname="__b3bp_tmp_opt_long2short_${OPTARG//-/_}"
+        printf -v "__b3bp_tmp_opt" '%s' "${!__b3bp_tmp_varname}"
+        # Only assign OPTARG if option takes an argument
+        __b3bp_tmp_varname="__b3bp_tmp_has_arg_${__b3bp_tmp_opt}"
+        __b3bp_tmp_varvalue="${!__b3bp_tmp_varname}"
+        [[ "${__b3bp_tmp_varvalue}" != "0" ]] && __b3bp_tmp_varvalue="1"
+        printf -v "OPTARG" '%s' "${@:OPTIND:${__b3bp_tmp_varvalue}}"
+        # shift over the argument if argument is expected
+        ((OPTIND+=__b3bp_tmp_varvalue))
+      fi
+      # we have set opt/OPTARG to the short value and the argument as OPTARG if it exists
+    fi
+
+    __b3bp_tmp_value="${OPTARG}"
+
+    __b3bp_tmp_varname="__b3bp_tmp_is_array_${__b3bp_tmp_opt:0:1}"
+    if [[ "${!__b3bp_tmp_varname}" != "0" ]]; then
+      # repeatables
+      # shellcheck disable=SC2016
+      if [[ -z "${OPTARG}" ]]; then
+        # repeatable flags, they increcemnt
+        __b3bp_tmp_varname="arg_${__b3bp_tmp_opt:0:1}"
+        debug "cli arg ${__b3bp_tmp_varname} = (${__b3bp_tmp_default}) -> ${!__b3bp_tmp_varname}"
+          # shellcheck disable=SC2004
+        __b3bp_tmp_value=$((${!__b3bp_tmp_varname} + 1))
+        printf -v "${__b3bp_tmp_varname}" '%s' "${__b3bp_tmp_value}"
+      else
+        # repeatable args, they get appended to an array
+        __b3bp_tmp_varname="arg_${__b3bp_tmp_opt:0:1}[@]"
+        debug "cli arg ${__b3bp_tmp_varname} append ${__b3bp_tmp_value}"
+        declare -a "${__b3bp_tmp_varname}"='("${!__b3bp_tmp_varname}" "${__b3bp_tmp_value}")'
+      fi
+    else
+      # non-repeatables
+      __b3bp_tmp_varname="arg_${__b3bp_tmp_opt:0:1}"
+      __b3bp_tmp_default="${!__b3bp_tmp_varname}"
+
+      if [[ -z "${OPTARG}" ]]; then
+        __b3bp_tmp_value=$((__b3bp_tmp_default + 1))
+      fi
+
+      printf -v "${__b3bp_tmp_varname}" '%s' "${__b3bp_tmp_value}"
+
+      debug "cli arg ${__b3bp_tmp_varname} = (${__b3bp_tmp_default}) -> ${!__b3bp_tmp_varname}"
+    fi
+  done
+  set -o nounset # no more unbound variable references expected
+
+  shift $((OPTIND-1))
+
+  if [[ "${1:-}" = "--" ]] ; then
+    shift
+  fi
+fi
+
+
+### Automatic validation of required option arguments
+##############################################################################
+
+for __b3bp_tmp_varname in ${!__b3bp_tmp_has_arg_*}; do
+  # validate only options which required an argument
+  [[ "${!__b3bp_tmp_varname}" = "2" ]] || continue
+
+  __b3bp_tmp_opt_short="${__b3bp_tmp_varname##*_}"
+  __b3bp_tmp_varname="arg_${__b3bp_tmp_opt_short}"
+  [[ "${!__b3bp_tmp_varname}" ]] && continue
+
+  __b3bp_tmp_varname="__b3bp_tmp_opt_short2long_${__b3bp_tmp_opt_short}"
+  printf -v "__b3bp_tmp_opt_long" '%s' "${!__b3bp_tmp_varname}"
+  [[ "${__b3bp_tmp_opt_long:-}" ]] && __b3bp_tmp_opt_long=" (--${__b3bp_tmp_opt_long//_/-})"
+
+  help "Option -${__b3bp_tmp_opt_short}${__b3bp_tmp_opt_long:-} requires an argument"
+done
+
+
+### Cleanup Environment variables
+##############################################################################
+
+for __tmp_varname in ${!__b3bp_tmp_*}; do
+  unset -v "${__tmp_varname}"
+done
+
+unset -v __tmp_varname
+
+
+### Externally supplied __usage. Nothing else to do here
+##############################################################################
+
+if [[ "${__b3bp_external_usage:-}" = "true" ]]; then
+  unset -v __b3bp_external_usage
+  return
+fi
+
+
+### Signal trapping and backtracing
+##############################################################################
+
+function __b3bp_cleanup_before_exit () {
+  info "Cleaning up. Done"
+}
+trap __b3bp_cleanup_before_exit EXIT
+
+# requires `set -o errtrace`
+__b3bp_err_report() {
+    local error_code=${?}
+    error "Error in ${__file} in function ${1} on line ${2}"
+    exit ${error_code}
+}
+# Uncomment the following line for always providing an error backtrace
+# trap '__b3bp_err_report "${FUNCNAME:-.}" ${LINENO}' ERR
+
+
+### Command-line argument switches (like -d for debugmode, -h for showing helppage)
+##############################################################################
+
+# debug mode
+if [[ "${arg_d:?}" = "1" ]]; then
+  set -o xtrace
+  PS4='+(${BASH_SOURCE}:${LINENO}): ${FUNCNAME[0]:+${FUNCNAME[0]}(): }'
+  LOG_LEVEL="7"
+  # Enable error backtracing
+  trap '__b3bp_err_report "${FUNCNAME:-.}" ${LINENO}' ERR
+fi
+
+# verbose mode
+if [[ "${arg_v:?}" = "1" ]]; then
+  set -o verbose
+fi
+
+# no color mode
+if [[ "${arg_n:?}" = "1" ]]; then
+  NO_COLOR="true"
+fi
+
+# help mode
+if [[ "${arg_h:?}" = "1" ]]; then
+  # Help exists with code 1
+  help "Help using ${0}"
+fi
+
+
+### Validation. Error out if the things required for your script are not present
+##############################################################################
+
+[[ "${arg_f:-}" ]]     || help      "Setting a filename with -f or --file is required"
+[[ "${LOG_LEVEL:-}" ]] || emergency "Cannot continue without LOG_LEVEL. "
+
+
+### Runtime
+##############################################################################
+
+info "__i_am_main_script: ${__i_am_main_script}"
+info "__file: ${__file}"
+info "__dir: ${__dir}"
+info "__base: ${__base}"
+info "OSTYPE: ${OSTYPE}"
+
+info "arg_f: ${arg_f}"
+info "arg_d: ${arg_d}"
+info "arg_v: ${arg_v}"
+info "arg_h: ${arg_h}"
+
+# shellcheck disable=SC2015
+if [[ -n "${arg_i:-}" ]] && declare -p arg_i 2> /dev/null | grep -q '^declare \-a'; then
+  info "arg_i:"
+  for input_file in "${arg_i[@]}"; do
+    info " - ${input_file}"
+  done
+elif [[ -n "${arg_i:-}" ]]; then
+  info "arg_i: ${arg_i}"
+else
+  info "arg_i: 0"
+fi
+
+# shellcheck disable=SC2015
+if [[ -n "${arg_x:-}" ]] && declare -p arg_x 2> /dev/null | grep -q '^declare \-a'; then
+  info "arg_x: ${#arg_x[@]}"
+elif [[ -n "${arg_x:-}" ]]; then
+  info "arg_x: ${arg_x}"
+else
+  info "arg_x: 0"
+fi
+
+info "$(echo -e "multiple lines example - line #1\\nmultiple lines example - line #2\\nimagine logging the output of 'ls -al /path/'")"
+
+# All of these go to STDERR, so you can use STDOUT for piping machine readable information to other software
+debug "Info useful to developers for debugging the application, not useful during operations."
+info "Normal operational messages - may be harvested for reporting, measuring throughput, etc. - no action required."
+notice "Events that are unusual but not error conditions - might be summarized in an email to developers or admins to spot potential problems - no immediate action required."
+warning "Warning messages, not an error, but indication that an error will occur if action is not taken, e.g. file system 85% full - each item must be resolved within a given time."
+error "Non-urgent failures, these should be relayed to developers or admins; each item must be resolved within a given time."
+critical "Should be corrected immediately, but indicates failure in a primary system, an example is a loss of a backup ISP connection."
+alert "Should be corrected immediately, therefore notify staff who can fix the problem. An example would be the loss of a primary ISP connection."
+emergency "A \"panic\" condition usually affecting multiple apps/servers/sites. At this level it would usually notify all tech staff on call."

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/package.json

@@ -0,0 +1,29 @@
+{
+  "name": "bash3boilerplate",
+  "description": "Copypastable templates to write better bash scripts",
+  "version": "2.7.2",
+  "packageManager": "yarn@3.6.0+sha224.19e47520fa56c6146388fdeb438d9dcf6630c3f277a2e1180995c3bb",
+  "engines": {
+    "node": ">= 18",
+    "yarn": "3.6.0"
+  },
+  "scripts": {
+    "lint:shellcheck": "shellcheck --severity=${SHELLCHECK_SEVERITY:-info} $(find . -name '*.sh' -maxdepth 2)",
+    "lint:style": "test/style.pl $(find . -name '*.sh' -maxdepth 2)",
+    "lint": "npm-run-all -l 'lint:**'",
+    "release:major": "env SEMANTIC=major yarn release",
+    "release:minor": "env SEMANTIC=minor yarn release",
+    "release:patch": "env SEMANTIC=patch yarn release",
+    "release": "npm version ${SEMANTIC:-patch} -m \"Release %s\" && yarn version:replace && git commit main.sh src/*.sh -m 'Update version' && git push && git push --tags -f && npm publish",
+    "test:debug:main:repeated": "env LOG_LEVEL=7 test/acceptance.sh main-repeated",
+    "test:update": "env SAVE_FIXTURES=true yarn test",
+    "test": "test/acceptance.sh",
+    "version:current": "node -e 'console.log(require(\"./package.json\").version)'",
+    "version:replace": "replace 'v\\d+\\.\\d+\\.\\d+' \"v$(npm run --silent version:current)\" main.sh src/*.sh"
+  },
+  "devDependencies": {
+    "fakefile": "1.1.0",
+    "npm-run-all": "4.1.5",
+    "replace": "1.2.2"
+  }
+}

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/src/ini_val.sh

@@ -0,0 +1,113 @@
+#!/usr/bin/env bash
+# BASH3 Boilerplate: ini_val
+#
+# This file:
+#
+#  - Can read and write .ini files using pure bash
+#
+# Limitations:
+#
+#  - All keys inside a section of the .ini file must be unique
+#  - Optional comment parameter for the creation of new entries
+#
+# Usage as a function:
+#
+#  source ini_val.sh
+#  ini_val data.ini connection.host 127.0.0.1 "Host name or IP address"
+#
+# Usage as a command:
+#
+#  ini_val.sh data.ini connection.host 127.0.0.1 "Host name or IP address"
+#
+# Based on a template by BASH3 Boilerplate vv2.7.2
+# http://bash3boilerplate.sh/#authors
+#
+# The MIT License (MIT)
+# Copyright (c) 2013 Kevin van Zonneveld and contributors
+# You are not obligated to bundle the LICENSE file with your b3bp projects as long
+# as you leave these references intact in the header comments of your source files.
+
+function ini_val() {
+  local file="${1:-}"
+  local sectionkey="${2:-}"
+  local val="${3:-}"
+  local comment="${4:-}"
+  local delim="="
+  local comment_delim=";"
+  local section=""
+  local key=""
+  local current=""
+  # add default section
+  local section_default="default"
+
+  if [[ ! -f "${file}" ]]; then
+    # touch file if not exists
+    touch "${file}"
+  fi
+
+  # Split on . for section. However, section is optional
+  IFS='.' read -r section key <<< "${sectionkey}"
+  if [[ ! "${key}" ]]; then
+    key="${section}"
+    # default section if not given
+    section="${section_default}"
+  fi
+
+  # get current value (if exists)
+  current=$(sed -En "/^\[/{h;d;};G;s/^${key}([[:blank:]]*)${delim}(.*)\n\[${section}\]$/\2/p" "${file}"|awk '{$1=$1};1')
+  # get current comment (if exists)
+  current_comment=$(sed -En "/^\[${section}\]/,/^\[.*\]/ s|^(${comment_delim}\[${key}\])(.*)|\2|p" "${file}"|awk '{$1=$1};1')
+
+  if ! grep -q "\[${section}\]" "${file}"; then
+    # create section if not exists (empty line to seperate new section for better readability)
+    echo  >> "${file}"
+    echo "[${section}]" >> "${file}"
+  fi
+
+  if [[ ! "${val}" ]]; then
+    # get a value
+    echo "${current}"
+  else
+    # set a value
+    if [[ ! "${section}" ]]; then
+      # if no section is given, propagate the default section
+      section=${section_default}
+    fi
+
+    if [[ ! "${comment}" ]]; then
+      # if no comment given, keep old comment
+      comment="${current_comment}"
+    fi
+    # maintenance area
+    # a) remove comment if new given / respect section
+    sed -i.bak "/^\[${section}\]/,/^\[.*\]/ s|^\(${comment_delim}\[${key}\] \).*$||" "${file}"
+    # b) remove old key / respect section
+    sed -i.bak "/^\[${section}\]/,/^\[.*\]/ s|^\(${key}=\).*$||" "${file}"
+    # c) remove all empty lines in ini file
+    sed -i.bak '/^[[:space:]]*$/d' "${file}"
+    # d) insert line break before every section for better readability
+    sed -i.bak $'s/^\\[/\\\n\\[/g' "${file}"
+
+    # add to section
+    if [[ ! "${comment}" ]]; then
+      # add new key/value _without_ comment
+      RET="/\\[${section}\\]/a\\
+${key}${delim}${val}"
+    else
+      # add new key/value _with_ preceeding comment
+      RET="/\\[${section}\\]/a\\
+${comment_delim}[${key}] ${comment}\\
+${key}${delim}${val}"
+    fi
+    sed -i.bak -e "${RET}" "${file}"
+    # this .bak dance is done for BSD/GNU portability: http://stackoverflow.com/a/22084103/151666
+    rm -f "${file}.bak"
+  fi
+}
+
+if [[ "${BASH_SOURCE[0]}" != "${0}" ]]; then
+  export -f ini_val
+else
+  ini_val "${@}"
+  exit ${?}
+fi

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/src/megamount.sh

@@ -0,0 +1,78 @@
+#!/usr/bin/env bash
+# BASH3 Boilerplate: megamount
+#
+# This file:
+#
+#  - Takes a URL (smb, nfs, afs) and tries to mount it at a given target directory
+#  - Forcefully unmounts any active mount at the target directory first
+#  - Displays the mount's contents for verification
+#
+# Depends on:
+#
+#  - ./parse_url.sh
+#
+# Usage as a function:
+#
+#  source megamount.sh
+#  megamount smb://janedoe:abc123@192.168.0.1/documents /mnt/documents
+#
+# Usage as a command:
+#
+#  megamount.sh smb://janedoe:abc123@192.168.0.1/documents /mnt/documents
+#
+# Based on a template by BASH3 Boilerplate vv2.7.2
+# http://bash3boilerplate.sh/#authors
+#
+# The MIT License (MIT)
+# Copyright (c) 2013 Kevin van Zonneveld and contributors
+# You are not obligated to bundle the LICENSE file with your b3bp projects as long
+# as you leave these references intact in the header comments of your source files.
+
+__dir="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+
+# shellcheck source=src/parse_url.sh
+source "${__dir}/parse_url.sh"
+
+function megamount () {
+  local url="${1}"
+  local target="${2}"
+
+  local proto
+  local user
+  local pass
+  local host
+  local port
+  local path
+
+  proto=$(parse_url "${url}" "proto")
+  user=$(parse_url "${url}" "user")
+  pass=$(parse_url "${url}" "pass")
+  host=$(parse_url "${url}" "host")
+  port=$(parse_url "${url}" "port")
+  path=$(parse_url "${url}" "path")
+
+  (umount -lf "${target}" || umount -f "${target}") > /dev/null 2>&1 || true
+  mkdir -p "${target}"
+  if [[ "${proto}" = "smb://" ]]; then
+    mount -t cifs --verbose -o "username=${user},password=${pass},hard" "//${host}/${path}" "${target}"
+  elif [[ "${proto}" = "afp://" ]]; then
+    # start syslog-ng
+    # afpfsd || echo "Unable to run afpfsd. Does /dev/log exist?" && exit 1
+    mount_afp "${url}" "${target}"
+  elif [[ "${proto}" = "nfs://" ]]; then
+    mount -t nfs --verbose -o "vers=3,nolock,soft,intr,rsize=32768,wsize=32768" "${host}:/${path}" "${target}"
+  else
+    echo "ERR: Unknown protocol: '${proto}'"
+    exit 1
+  fi
+
+  # chmod 777 "${target}"
+  ls -al "${target}/"
+}
+
+if [[ "${BASH_SOURCE[0]}" != "${0}" ]]; then
+  export -f megamount
+else
+  megamount "${@}"
+  exit ${?}
+fi

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/src/parse_url.sh

@@ -0,0 +1,84 @@
+#!/usr/bin/env bash
+# BASH3 Boilerplate: parse_url
+#
+# This file:
+#
+#  - Takes a URL and parses protocol, user, pass, host, port, path.
+#
+# Based on:
+#
+#  - http://stackoverflow.com/a/6174447/151666
+#
+# Usage as a function:
+#
+#  source parse_url.sh
+#  parse_url 'http://johndoe:abc123@example.com:8080/index.html' pass
+#
+# Usage as a command:
+#
+#  parse_url.sh 'http://johndoe:abc123@example.com:8080/index.html'
+#
+# Based on a template by BASH3 Boilerplate vv2.7.2
+# http://bash3boilerplate.sh/#authors
+#
+# The MIT License (MIT)
+# Copyright (c) 2013 Kevin van Zonneveld and contributors
+# You are not obligated to bundle the LICENSE file with your b3bp projects as long
+# as you leave these references intact in the header comments of your source files.
+
+function parse_url() {
+  local parse="${1}"
+  local need="${2:-}"
+
+  local proto
+  local url
+  local userpass
+  local user
+  local pass
+  local hostport
+  local host
+  local port
+  local path
+
+  proto="$(echo "${parse}" | grep :// | sed -e's,^\(.*://\).*,\1,g')"
+  url="${parse/${proto}/}"
+  userpass="$(echo "${url}" | grep @ | cut -d@ -f1)"
+  user="$(echo "${userpass}" | grep : | cut -d: -f1)"
+  pass="$(echo "${userpass}" | grep : | cut -d: -f2)"
+  hostport="$(echo "${url/${userpass}@/}" | cut -d/ -f1)"
+  host="$(echo "${hostport}" | grep : | cut -d: -f1)"
+  port="$(echo "${hostport}" | grep : | cut -d: -f2)"
+  path="$(echo "${url}" | grep / | cut -d/ -f2-)"
+
+  [[ ! "${user}" ]] && user="${userpass}"
+  [[ ! "${host}" ]] && host="${hostport}"
+  if [[ ! "${port}" ]]; then
+    [[ "${proto}" = "http://" ]]  && port="80"
+    [[ "${proto}" = "https://" ]] && port="443"
+    [[ "${proto}" = "mysql://" ]] && port="3306"
+    [[ "${proto}" = "redis://" ]] && port="6379"
+  fi
+
+  if [[ "${need}" ]]; then
+    echo "${!need}"
+  else
+    echo ""
+    echo " Use second argument to return just 1 variable."
+    echo " parse_url() demo: "
+    echo ""
+    echo "   proto: ${proto}"
+    echo "   user:  ${user}"
+    echo "   pass:  ${pass}"
+    echo "   host:  ${host}"
+    echo "   port:  ${port}"
+    echo "   path:  ${path}"
+    echo ""
+  fi
+}
+
+if [[ "${BASH_SOURCE[0]}" != "${0}" ]]; then
+  export -f parse_url
+else
+  parse_url "${@}"
+  exit ${?}
+fi

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/src/templater.sh

@@ -0,0 +1,68 @@
+#!/usr/bin/env bash
+# BASH3 Boilerplate: templater
+#
+# This file:
+#
+#  - takes a source (template) & destination (config) filepath argument
+#  - then replaces placeholders with variables found in the environment
+#
+# Usage as a function:
+#
+#  source templater.sh
+#  export NAME=kevin
+#  templater input.cfg output.cfg
+#
+# Usage as a command:
+#
+#  ALLOW_REMAINDERS=1 templater.sh input.cfg output.cfg
+#
+# Based on a template by BASH3 Boilerplate vv2.7.2
+# http://bash3boilerplate.sh/#authors
+#
+# The MIT License (MIT)
+# Copyright (c) 2013 Kevin van Zonneveld and contributors
+# You are not obligated to bundle the LICENSE file with your b3bp projects as long
+# as you leave these references intact in the header comments of your source files.
+
+function templater() {
+  ALLOW_REMAINDERS="${ALLOW_REMAINDERS:-0}"
+
+  templateSrc="${1:-}"
+  templateDst="${2:-}"
+
+  if [[ ! -f "${templateSrc}" ]]; then
+    echo "ERROR: Template source '${templateSrc}' needs to exist"
+    exit 1
+  fi
+  if [[ ! "${templateDst}" ]]; then
+    echo "ERROR: Template destination '${templateDst}' needs to be specified"
+    exit 1
+  fi
+
+  if [[ "$(command -v perl)" ]]; then
+    perl -p -e 's/\$\{(\w+)\}/(exists $ENV{$1} ? $ENV{$1} : "\${$1}")/eg' < "${templateSrc}" > "${templateDst}"
+  else
+    cp -f "${templateSrc}" "${templateDst}"
+
+    for var in $(env |awk -F= '{print $1}' |grep -E '^(_[A-Z0-9_]+|[A-Z0-9][A-Z0-9_]*)$'); do
+      sed -i.bak -e "s#\${${var}}#${!var//#/\\#/}#g" "${templateDst}"
+      # this .bak dance is done for BSD/GNU portability: http://stackoverflow.com/a/22084103/151666
+      rm -f "${templateDst}.bak"
+    done
+  fi
+
+  # cat "${templateDst}"
+
+  # shellcheck disable=SC2016
+  if grep '${' "${templateDst}" && [[ "${ALLOW_REMAINDERS}" = "0" ]]; then
+    echo "ERROR: Unable to replace the above template vars"
+    exit 1
+  fi
+}
+
+if [[ "${BASH_SOURCE[0]}" != "${0}" ]]; then
+  export -f templater
+else
+  templater "${@}"
+  exit ${?}
+fi

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/acceptance.sh

@@ -0,0 +1,232 @@
+#!/usr/bin/env bash
+# This file:
+#
+#  - Executes one (or all) test scenarios
+#  - Replaces dynamic things like hostnames, IPs, dates, etc
+#  - Optionally saves the results as fixtures, that later runs will be compared against
+#
+# Usage:
+#
+#  ./deploy.sh
+#
+# Based on a template by BASH3 Boilerplate v2.0.0
+# http://bash3boilerplate.sh/#authors
+#
+# The MIT License (MIT)
+# Copyright (c) 2013 Kevin van Zonneveld and contributors
+# You are not obligated to bundle the LICENSE file with your b3bp projects as long
+# as you leave these references intact in the header comments of your source files.
+
+# Exit on error. Append || true if you expect an error.
+set -o errexit
+# Exit on error inside any functions or subshells.
+set -o errtrace
+# Do not allow use of undefined vars. Use ${VAR:-} to use an undefined VAR
+set -o nounset
+# Catch the error in case mysqldump fails (but gzip succeeds) in `mysqldump |gzip`
+set -o pipefail
+# Turn on traces, useful while debugging but commented out by default
+# set -o xtrace
+
+# Set magic variables for current file, directory, os, etc.
+__dir="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+__file="${__dir}/$(basename "${BASH_SOURCE[0]}")"
+__base="$(basename "${__file}" .sh)"
+__root="$(cd "$(dirname "${__dir}")" && pwd)"
+
+__sysTmpDir="${TMPDIR:-/tmp}"
+__sysTmpDir="${__sysTmpDir%/}" # <-- remove trailing slash on macosx
+__accptstTmpDir=$(mktemp -d "${__sysTmpDir}/${__base}.XXXXXX")
+
+function cleanup_before_exit () { rm -r "${__accptstTmpDir:?}"; }
+trap cleanup_before_exit EXIT
+
+cmdSed="sed"
+cmdTimeout="timeout"
+
+if [[ "${OSTYPE}" = "darwin"* ]]; then
+  cmdSed="gsed"
+  cmdTimeout="gtimeout"
+fi
+
+if [[ ! "$(command -v ${cmdSed})" ]]; then
+  echo "Please install ${cmdSed}"
+  exit 1
+fi
+
+if [[ ! "$(command -v ${cmdTimeout})" ]]; then
+  echo "Please install ${cmdTimeout}"
+  exit 1
+fi
+
+__node="$(command -v node)"
+__arch="amd64"
+
+# explicitly setting NO_COLOR to false will make b3bp ignore TERM
+# not being "xterm*" or "screen*" and STDERR not being connected to a terminal
+# it's the opposite of NO_COLOR="true" - it forces color, no matter what
+export NO_COLOR="false"
+
+# Running prepare before other scenarios is important on Travis,
+# so that stdio can diverge - and we can enforce stricter
+# stdio comparison on all other tests.
+while IFS=$'\n' read -r scenario; do
+  scenario="$(dirname "${scenario}")"
+  scenario="${scenario##${__dir}/scenario/}"
+
+  [[ "${scenario}" = "prepare" ]] && continue
+  [[ "${1:-}" ]] && [[ "${scenario}" != "${1}" ]] && continue
+
+  echo "==> Scenario: ${scenario}"
+  pushd "${__dir}/scenario/${scenario}" > /dev/null
+
+    # Run scenario
+    (${cmdTimeout} --kill-after=6m 5m bash ./run.sh \
+      > "${__accptstTmpDir}/${scenario}.stdio" 2>&1; \
+      echo "${?}" > "${__accptstTmpDir}/${scenario}.exitcode" \
+    ) || true
+
+    # Clear out environmental specifics
+    for typ in stdio exitcode; do
+      curFile="${__accptstTmpDir}/${scenario}.${typ}"
+      "${cmdSed}" -i \
+        -e "s@${__node}@{node}@g" "${curFile}" \
+        -e "s@${__root}@{root}@g" "${curFile}" \
+        -e "s@${__sysTmpDir}@{tmpdir}@g" "${curFile}" \
+        -e "s@/tmp@{tmpdir}@g" "${curFile}" \
+        -e "s@${HOME:-/home/travis}@{home}@g" "${curFile}" \
+        -e "s@${USER:-travis}@{user}@g" "${curFile}" \
+        -e "s@travis@{user}@g" "${curFile}" \
+        -e "s@kvz@{user}@g" "${curFile}" \
+        -e "s@{root}/node_modules/\\.bin/node@{node}@g" "${curFile}" \
+        -e "s@{home}/build/{user}/fre{node}@{node}@g" "${curFile}" \
+        -e "s@${HOSTNAME}@{hostname}@g" "${curFile}" \
+        -e "s@${__arch}@{arch}@g" "${curFile}" \
+        -e "s@${OSTYPE}@{OSTYPE}@g" "${curFile}" \
+        -e "s@OSX@{os}@g" "${curFile}" \
+        -e "s@Linux@{os}@g" "${curFile}" \
+      || false
+
+      if grep -q 'ACCPTST:STDIO_REPLACE_IPS' "${curFile}"; then
+        "${cmdSed}" -i \
+          -r 's@[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}@{ip}@g' \
+        "${curFile}"
+
+        # IPs vary in length. Ansible uses padding. {ip} does not vary in length
+        # so kill the padding after it for consistent output
+        "${cmdSed}" -i \
+          -r 's@\{ip\}\s+@{ip} @g' \
+        "${curFile}"
+      fi
+      if grep -q 'ACCPTST:STDIO_REPLACE_UUIDS' "${curFile}"; then
+        "${cmdSed}" -i \
+          -r 's@[0-9a-f\-]{32,40}@{uuid}@g' \
+        "${curFile}"
+      fi
+      if grep -q 'ACCPTST:STDIO_REPLACE_BIGINTS' "${curFile}"; then
+        # Such as: 3811298194
+        "${cmdSed}" -i \
+          -r 's@[0-9]{7,64}@{bigint}@g' \
+        "${curFile}"
+      fi
+      if grep -q 'ACCPTST:STDIO_REPLACE_DATETIMES' "${curFile}"; then
+        # Such as: 2016-02-10 15:38:44.420094
+        "${cmdSed}" -i \
+          -r 's@[0-9]{4}-[0-9]{2}-[0-9]{2} [0-9]{2}:[0-9]{2}:[0-9]{2}@{datetime}@g' \
+        "${curFile}"
+      fi
+      if grep -q 'ACCPTST:STDIO_REPLACE_LONGTIMES' "${curFile}"; then
+        # Such as: 2016-02-10 15:38:44.420094
+        "${cmdSed}" -i \
+          -r 's@[0-9]{4}-[0-9]{2}-[0-9]{2} [0-9]{2}:[0-9]{2}:[0-9]{2}.[0-9]{6}@{longtime}@g' \
+        "${curFile}"
+      fi
+      if grep -q 'ACCPTST:STDIO_REPLACE_DURATIONS' "${curFile}"; then
+        # Such as: 0:00:00.001991
+        "${cmdSed}" -i \
+          -r 's@[0-9]{1,2}:[0-9]{2}:[0-9]{2}.[0-9]{6}@{duration}@g' \
+        "${curFile}"
+      fi
+      if grep -q 'ACCPTST:STDIO_REPLACE_REMOTE_EXEC' "${curFile}"; then
+        grep -Ev 'remote-exec\): [ a-zA-Z]' "${curFile}" > "${__sysTmpDir}/accptst-filtered.txt"
+        mv "${__sysTmpDir}/accptst-filtered.txt" "${curFile}"
+      fi
+    done
+
+    # Save these as new fixtures?
+    if [[ "${SAVE_FIXTURES:-}" = "true" ]]; then
+      for typ in stdio exitcode; do
+        curFile="${__accptstTmpDir}/${scenario}.${typ}"
+        cp -f \
+          "${curFile}" \
+          "${__dir}/fixture/${scenario}.${typ}"
+      done
+    fi
+
+    # Compare
+    for typ in stdio exitcode; do
+      curFile="${__accptstTmpDir}/${scenario}.${typ}"
+
+      echo -n "    comparing ${typ}.. "
+
+      if [[ "${typ}" = "stdio" ]]; then
+        if grep -q 'ACCPTST:STDIO_SKIP_COMPARE' "${curFile}"; then
+          echo "skip"
+          continue
+        fi
+      fi
+
+      if ! diff --strip-trailing-cr "${__dir}/fixture/${scenario}.${typ}" "${curFile}"; then
+        echo -e "\\n\\n==> MISMATCH OF: ${scenario}.${typ} ---^"
+        echo -e "\\n\\n==> EXPECTED STDIO: "
+        cat "${__dir}/fixture/${scenario}.stdio" || true
+        echo -e "\\n\\n==> ACTUAL STDIO: "
+        cat "${__accptstTmpDir}/${scenario}.stdio" || true
+        exit 1
+      fi
+
+      echo "✓"
+    done
+
+  popd > /dev/null
+done <<< "$(find "${__dir}/scenario" -type f -iname 'run.sh')"
+
+[[ "${1:-}" ]] && exit 0
+
+# Ensure correct syntax with all available bashes
+
+# shellcheck disable=SC2230
+# "command -v" is not a substitute for "which -a"
+while IFS=$'\n' read -r bash; do
+  if [[ "${bash:-}" = "" ]]; then
+    continue
+  fi
+  # shellcheck disable=SC2016
+  echo "==> ${bash} -n $(${bash} -c 'echo "(${BASH_VERSION})"')"
+  pushd "${__root}" > /dev/null
+
+  failed="false"
+
+  while IFS=$'\n' read -r file; do
+    [[ "${file}" =~ ^\./node_modules/ ]] && continue
+
+    echo -n "    ${file}.. "
+
+    if ! "${bash}" -n "${file}" 2>> "${__accptstTmpDir}/${bash//\//.}.err"; then
+      echo "✗"
+      failed="true"
+      continue
+    fi
+
+    echo "✓"
+  done <<< "$(find . -type f -iname '*.sh')"
+
+  popd > /dev/null
+
+  if [[ "${failed}" = "true" ]]; then
+    cat "${__accptstTmpDir}/${bash//\//.}.err"
+    exit 1
+  fi
+done <<< "$(which -a bash 2>/dev/null)"
+
+exit 0

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/double-source.exitcode

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

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/double-source.stdio

@@ -0,0 +1,25 @@
+ACCPTST:STDIO_REPLACE_DATETIMES
+{datetime} UTC [    debug] cli arg arg_f = () -> {tmpdir}/x
+{datetime} UTC [     info] __i_am_main_script: 0
+{datetime} UTC [     info] __file: {root}/example.sh
+{datetime} UTC [     info] __dir: {root}
+{datetime} UTC [     info] __base: example
+{datetime} UTC [     info] OSTYPE: {OSTYPE}
+{datetime} UTC [     info] arg_f: {tmpdir}/x
+{datetime} UTC [     info] arg_d: 0
+{datetime} UTC [     info] arg_v: 0
+{datetime} UTC [     info] arg_h: 0
+{datetime} UTC [     info] arg_i: 0
+{datetime} UTC [     info] arg_x: 0
+{datetime} UTC [     info] multiple lines example - line #1
+{datetime} UTC [     info] multiple lines example - line #2
+{datetime} UTC [     info] imagine logging the output of 'ls -al /path/'
+{datetime} UTC [    debug] Info useful to developers for debugging the application, not useful during operations.
+{datetime} UTC [     info] Normal operational messages - may be harvested for reporting, measuring throughput, etc. - no action required.
+{datetime} UTC [   notice] Events that are unusual but not error conditions - might be summarized in an email to developers or admins to spot potential problems - no immediate action required.
+{datetime} UTC [  warning] Warning messages, not an error, but indication that an error will occur if action is not taken, e.g. file system 85% full - each item must be resolved within a given time.
+{datetime} UTC [    error] Non-urgent failures, these should be relayed to developers or admins; each item must be resolved within a given time.
+{datetime} UTC [ critical] Should be corrected immediately, but indicates failure in a primary system, an example is a loss of a backup ISP connection.
+{datetime} UTC [    alert] Should be corrected immediately, therefore notify staff who can fix the problem. An example would be the loss of a primary ISP connection.
+{datetime} UTC [emergency] A "panic" condition usually affecting multiple apps/servers/sites. At this level it would usually notify all tech staff on call.
+{datetime} UTC [     info] Cleaning up. Done

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/ini_val.exitcode

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

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/ini_val.stdio

@@ -0,0 +1,42 @@
+--> command: Read 3 values
+exists
+127.0.0.1
+nginx, nodejs
+
+--> command: Replace three values in-place and show result
+
+[default]
+orphan=no more
+
+[connection]
+host=192.168.0.1
+
+[software]
+packages=vim
+
+[comment]
+;[command] got this new comment
+command=works like a chame
+;[new_command] last addition will be moved downwards again after next command
+new_command=commented too
+--> function: Read 3 values
+exists
+127.0.0.1
+nginx, nodejs
+
+--> function: Replace three values in-place and show result
+
+[default]
+orphan=no more
+
+[connection]
+host=192.168.0.1
+
+[software]
+packages=vim
+
+[comment]
+;[command] got this new comment
+command=works like a chame
+;[new_command] last addition will be moved downwards again after next command
+new_command=commented too

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/main-debug.exitcode

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

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/main-debug.stdio

@@ -0,0 +1,25 @@
+ACCPTST:STDIO_REPLACE_DATETIMES
+{datetime} UTC [    debug] cli arg arg_f = () -> {tmpdir}/x
+{datetime} UTC [     info] __i_am_main_script: 1
+{datetime} UTC [     info] __file: {root}/main.sh
+{datetime} UTC [     info] __dir: {root}
+{datetime} UTC [     info] __base: main
+{datetime} UTC [     info] OSTYPE: {OSTYPE}
+{datetime} UTC [     info] arg_f: {tmpdir}/x
+{datetime} UTC [     info] arg_d: 0
+{datetime} UTC [     info] arg_v: 0
+{datetime} UTC [     info] arg_h: 0
+{datetime} UTC [     info] arg_i: 0
+{datetime} UTC [     info] arg_x: 0
+{datetime} UTC [     info] multiple lines example - line #1
+{datetime} UTC [     info] multiple lines example - line #2
+{datetime} UTC [     info] imagine logging the output of 'ls -al /path/'
+{datetime} UTC [    debug] Info useful to developers for debugging the application, not useful during operations.
+{datetime} UTC [     info] Normal operational messages - may be harvested for reporting, measuring throughput, etc. - no action required.
+{datetime} UTC [   notice] Events that are unusual but not error conditions - might be summarized in an email to developers or admins to spot potential problems - no immediate action required.
+{datetime} UTC [  warning] Warning messages, not an error, but indication that an error will occur if action is not taken, e.g. file system 85% full - each item must be resolved within a given time.
+{datetime} UTC [    error] Non-urgent failures, these should be relayed to developers or admins; each item must be resolved within a given time.
+{datetime} UTC [ critical] Should be corrected immediately, but indicates failure in a primary system, an example is a loss of a backup ISP connection.
+{datetime} UTC [    alert] Should be corrected immediately, therefore notify staff who can fix the problem. An example would be the loss of a primary ISP connection.
+{datetime} UTC [emergency] A "panic" condition usually affecting multiple apps/servers/sites. At this level it would usually notify all tech staff on call.
+{datetime} UTC [     info] Cleaning up. Done

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/main-help.exitcode

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

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/main-help.stdio

@@ -0,0 +1,19 @@
+ACCPTST:STDIO_REPLACE_DATETIMES
+
+ Help using {root}/main.sh
+
+  -f --file  [arg] Filename to process. Required.
+  -t --temp  [arg] Location of tempfile. Default="{tmpdir}/bar"
+  -v               Enable verbose mode, print script as it is executed
+  -d --debug       Enables debug mode
+  -h --help        This page
+  -n --no-color    Disable color output
+  -1 --one         Do just one thing
+  -i --input [arg] File to process. Can be repeated.
+  -x               Specify a flag. Can be repeated.
+
+ This is Bash3 Boilerplate's help text. Feel free to add any description of your
+ program or elaborate more on command-line arguments. This section is not
+ parsed and will be added as-is to the help.
+
+{datetime} UTC [     info] Cleaning up. Done

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/main-longopt.exitcode

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

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/main-longopt.stdio

@@ -0,0 +1,4 @@
+ACCPTST:STDIO_REPLACE_DATETIMES
+{datetime} UTC [     info] arg_f: {tmpdir}/x
+{datetime} UTC [     info] arg_f: {tmpdir}/x
+{datetime} UTC [     info] arg_f: {tmpdir}/x

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/main-nocolor.exitcode

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

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/main-nocolor.stdio

@@ -0,0 +1,25 @@
+ACCPTST:STDIO_REPLACE_DATETIMES
+{datetime} UTC [    debug] cli arg arg_f = () -> {tmpdir}/x
+{datetime} UTC [     info] __i_am_main_script: 1
+{datetime} UTC [     info] __file: {root}/main.sh
+{datetime} UTC [     info] __dir: {root}
+{datetime} UTC [     info] __base: main
+{datetime} UTC [     info] OSTYPE: {OSTYPE}
+{datetime} UTC [     info] arg_f: {tmpdir}/x
+{datetime} UTC [     info] arg_d: 0
+{datetime} UTC [     info] arg_v: 0
+{datetime} UTC [     info] arg_h: 0
+{datetime} UTC [     info] arg_i: 0
+{datetime} UTC [     info] arg_x: 0
+{datetime} UTC [     info] multiple lines example - line #1
+{datetime} UTC [     info] multiple lines example - line #2
+{datetime} UTC [     info] imagine logging the output of 'ls -al /path/'
+{datetime} UTC [    debug] Info useful to developers for debugging the application, not useful during operations.
+{datetime} UTC [     info] Normal operational messages - may be harvested for reporting, measuring throughput, etc. - no action required.
+{datetime} UTC [   notice] Events that are unusual but not error conditions - might be summarized in an email to developers or admins to spot potential problems - no immediate action required.
+{datetime} UTC [  warning] Warning messages, not an error, but indication that an error will occur if action is not taken, e.g. file system 85% full - each item must be resolved within a given time.
+{datetime} UTC [    error] Non-urgent failures, these should be relayed to developers or admins; each item must be resolved within a given time.
+{datetime} UTC [ critical] Should be corrected immediately, but indicates failure in a primary system, an example is a loss of a backup ISP connection.
+{datetime} UTC [    alert] Should be corrected immediately, therefore notify staff who can fix the problem. An example would be the loss of a primary ISP connection.
+{datetime} UTC [emergency] A "panic" condition usually affecting multiple apps/servers/sites. At this level it would usually notify all tech staff on call.
+{datetime} UTC [     info] Cleaning up. Done

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/main-repeated.exitcode

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

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/main-repeated.stdio

@@ -0,0 +1,9 @@
+ACCPTST:STDIO_REPLACE_DATETIMES
+{datetime} UTC [     info] arg_i:
+{datetime} UTC [     info]  - simple_input
+{datetime} UTC [     info]  - input_in_quotes
+{datetime} UTC [     info]  - input with spaces
+{datetime} UTC [     info]  - input with "quotes"
+{datetime} UTC [     info]  - last_input
+{datetime} UTC [     info] arg_x: 3
+{datetime} UTC [     info] arg_x: 4

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/main-usage-defaults.exitcode

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

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/main-usage-defaults.stdio

@@ -0,0 +1,7 @@
+ACCPTST:STDIO_REPLACE_DATETIMES
+{datetime} UTC [     info] arg_1: 0
+{datetime} UTC [     info] arg_2: 0
+{datetime} UTC [     info] arg_3: 'THREE'
+{datetime} UTC [     info] arg_4: "FOUR"
+{datetime} UTC [     info] arg_5: OOOPS
+{datetime} UTC [     info] arg_6: 

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/main-usage-validation.exitcode

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

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/main-usage-validation.stdio

@@ -0,0 +1,169 @@
+ACCPTST:STDIO_REPLACE_DATETIMES
+# complain about -3
+
+ Option -3 (--three) requires an argument
+
+  -0 --zero        Do nothing.
+  -1 --one         Do one thing. Required.
+                   More description.
+  -2 --two         Do two things.
+                   More. Required. Description.
+  -3 --three [arg] Do three things.
+                   Required.
+  -4 --four  {arg} Do four things.
+  -5 --five  {arg} Do five things. Required. Maybe.
+  -6 --six   [arg] Do six things. Not Required.
+                   Required, it is not.
+  -7 --seven [arg] Required. Or bust.
+  -8 --eight [arg] Do eight things.
+                   More.Required.Description.
+  -a         [arg] Do A.   Required.
+                   Default="do-a"
+  -b         {arg} Do B.Default="do-b"
+  -c         [arg] Required.   Default="do-c"
+  -d         {arg} Default="do-d"
+
+ This is Bash3 Boilerplate's help text. Feel free to add any description of your
+ program or elaborate more on command-line arguments. This section is not
+ parsed and will be added as-is to the help.
+
+# complain about -4
+
+ Option -4 (--four) requires an argument
+
+  -0 --zero        Do nothing.
+  -1 --one         Do one thing. Required.
+                   More description.
+  -2 --two         Do two things.
+                   More. Required. Description.
+  -3 --three [arg] Do three things.
+                   Required.
+  -4 --four  {arg} Do four things.
+  -5 --five  {arg} Do five things. Required. Maybe.
+  -6 --six   [arg] Do six things. Not Required.
+                   Required, it is not.
+  -7 --seven [arg] Required. Or bust.
+  -8 --eight [arg] Do eight things.
+                   More.Required.Description.
+  -a         [arg] Do A.   Required.
+                   Default="do-a"
+  -b         {arg} Do B.Default="do-b"
+  -c         [arg] Required.   Default="do-c"
+  -d         {arg} Default="do-d"
+
+ This is Bash3 Boilerplate's help text. Feel free to add any description of your
+ program or elaborate more on command-line arguments. This section is not
+ parsed and will be added as-is to the help.
+
+# complain about -5
+
+ Option -5 (--five) requires an argument
+
+  -0 --zero        Do nothing.
+  -1 --one         Do one thing. Required.
+                   More description.
+  -2 --two         Do two things.
+                   More. Required. Description.
+  -3 --three [arg] Do three things.
+                   Required.
+  -4 --four  {arg} Do four things.
+  -5 --five  {arg} Do five things. Required. Maybe.
+  -6 --six   [arg] Do six things. Not Required.
+                   Required, it is not.
+  -7 --seven [arg] Required. Or bust.
+  -8 --eight [arg] Do eight things.
+                   More.Required.Description.
+  -a         [arg] Do A.   Required.
+                   Default="do-a"
+  -b         {arg} Do B.Default="do-b"
+  -c         [arg] Required.   Default="do-c"
+  -d         {arg} Default="do-d"
+
+ This is Bash3 Boilerplate's help text. Feel free to add any description of your
+ program or elaborate more on command-line arguments. This section is not
+ parsed and will be added as-is to the help.
+
+# complain about -8 (because -7 syntax is not supported)
+
+ Option -8 (--eight) requires an argument
+
+  -0 --zero        Do nothing.
+  -1 --one         Do one thing. Required.
+                   More description.
+  -2 --two         Do two things.
+                   More. Required. Description.
+  -3 --three [arg] Do three things.
+                   Required.
+  -4 --four  {arg} Do four things.
+  -5 --five  {arg} Do five things. Required. Maybe.
+  -6 --six   [arg] Do six things. Not Required.
+                   Required, it is not.
+  -7 --seven [arg] Required. Or bust.
+  -8 --eight [arg] Do eight things.
+                   More.Required.Description.
+  -a         [arg] Do A.   Required.
+                   Default="do-a"
+  -b         {arg} Do B.Default="do-b"
+  -c         [arg] Required.   Default="do-c"
+  -d         {arg} Default="do-d"
+
+ This is Bash3 Boilerplate's help text. Feel free to add any description of your
+ program or elaborate more on command-line arguments. This section is not
+ parsed and will be added as-is to the help.
+
+# complain about -d (because -d syntax is not supported)
+
+ Option -d requires an argument
+
+  -0 --zero        Do nothing.
+  -1 --one         Do one thing. Required.
+                   More description.
+  -2 --two         Do two things.
+                   More. Required. Description.
+  -3 --three [arg] Do three things.
+                   Required.
+  -4 --four  {arg} Do four things.
+  -5 --five  {arg} Do five things. Required. Maybe.
+  -6 --six   [arg] Do six things. Not Required.
+                   Required, it is not.
+  -7 --seven [arg] Required. Or bust.
+  -8 --eight [arg] Do eight things.
+                   More.Required.Description.
+  -a         [arg] Do A.   Required.
+                   Default="do-a"
+  -b         {arg} Do B.Default="do-b"
+  -c         [arg] Required.   Default="do-c"
+  -d         {arg} Default="do-d"
+
+ This is Bash3 Boilerplate's help text. Feel free to add any description of your
+ program or elaborate more on command-line arguments. This section is not
+ parsed and will be added as-is to the help.
+
+# complain about nothing
+{datetime} UTC [     info] arg_0: 0
+{datetime} UTC [     info] arg_1: 0
+{datetime} UTC [     info] arg_2: 0
+{datetime} UTC [     info] arg_3: arg3
+{datetime} UTC [     info] arg_4: arg4
+{datetime} UTC [     info] arg_5: arg5
+{datetime} UTC [     info] arg_6: 
+{datetime} UTC [     info] arg_7: 
+{datetime} UTC [     info] arg_8: arg8
+{datetime} UTC [     info] arg_a: do-a
+{datetime} UTC [     info] arg_b: do-b
+{datetime} UTC [     info] arg_c: do-c
+{datetime} UTC [     info] arg_d: argd
+# test for issue #108
+{datetime} UTC [     info] arg_0: 1
+{datetime} UTC [     info] arg_1: 0
+{datetime} UTC [     info] arg_2: 0
+{datetime} UTC [     info] arg_3: arg3
+{datetime} UTC [     info] arg_4: value
+{datetime} UTC [     info] arg_5: arg5
+{datetime} UTC [     info] arg_6: 
+{datetime} UTC [     info] arg_7: 
+{datetime} UTC [     info] arg_8: arg8
+{datetime} UTC [     info] arg_a: do-a
+{datetime} UTC [     info] arg_b: do-b
+{datetime} UTC [     info] arg_c: do-c
+{datetime} UTC [     info] arg_d: argd

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/megamount.exitcode

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

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/megamount.stdio

@@ -0,0 +1,2 @@
+ERR: Unknown protocol: 'foobarfs://'
+ERR: Unknown protocol: 'foobarfs://'

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/parse_url.exitcode

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

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/parse_url.stdio

@@ -0,0 +1,24 @@
+abc123
+
+ Use second argument to return just 1 variable.
+ parse_url() demo: 
+
+   proto: http://
+   user:  johndoe
+   pass:  abc123
+   host:  example.com
+   port:  8080
+   path:  index.html
+
+abc123
+
+ Use second argument to return just 1 variable.
+ parse_url() demo: 
+
+   proto: http://
+   user:  johndoe
+   pass:  abc123
+   host:  example.com
+   port:  8080
+   path:  index.html
+

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/templater.exitcode

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

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/fixture/templater.stdio

@@ -0,0 +1,14 @@
+--
+[connection]
+host = 127.0.0.1
+--
+[connection]
+host = 127.0.0.1
+--
+port = ${I_DONT_EXIST}
+[connection]
+host = 127.0.0.1
+port = ${I_DONT_EXIST}
+--
+port = ${I_DONT_EXIST}
+ERROR: Unable to replace the above template vars

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/scenario/double-source/run.sh

@@ -0,0 +1,15 @@
+#!/usr/bin/env bash
+set -o pipefail
+set -o errexit
+set -o nounset
+# set -o xtrace
+
+__dir="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+__root="$(cd "$(dirname "$(dirname "$(dirname "${__dir}")")")" && pwd)"
+
+export LOG_LEVEL=7
+
+echo "ACCPTST:STDIO_REPLACE_DATETIMES"
+
+# shellcheck source=example.sh
+source "${__root}/example.sh" -f /tmp/x

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/scenario/ini_val/data.ini

@@ -0,0 +1,8 @@
+[default]
+orphan=exists
+
+[connection]
+host=127.0.0.1
+
+[software]
+packages=nginx, nodejs

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/scenario/ini_val/run.sh

@@ -0,0 +1,54 @@
+#!/usr/bin/env bash
+set -o pipefail
+set -o errexit
+set -o nounset
+# set -o xtrace
+
+# Set magic variables for current FILE & DIR
+__dir="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+__root="$(cd "$(dirname "$(dirname "$(dirname "${__dir}")")")" && pwd)"
+
+# echo "ACCPTST:STDIO_REPLACE_DATETIMES"
+
+
+# Use as standalone:
+cp -f data.ini dummy.ini
+echo "--> command: Read 3 values"
+bash "${__root}/src/ini_val.sh" ./dummy.ini orphan
+bash "${__root}/src/ini_val.sh" ./dummy.ini connection.host
+bash "${__root}/src/ini_val.sh" ./dummy.ini software.packages
+bash "${__root}/src/ini_val.sh" ./dummy.ini comment.command
+
+echo "--> command: Replace three values in-place and show result"
+bash "${__root}/src/ini_val.sh" ./dummy.ini orphan "no more"
+bash "${__root}/src/ini_val.sh" ./dummy.ini connection.host "192.168.0.1"
+bash "${__root}/src/ini_val.sh" ./dummy.ini software.packages "vim"
+
+bash "${__root}/src/ini_val.sh" ./dummy.ini comment.command "commented" "this key is commented"
+bash "${__root}/src/ini_val.sh" ./dummy.ini comment.new_command "commented too" "last addition will be moved downwards again after next command"
+bash "${__root}/src/ini_val.sh" ./dummy.ini comment.command "works like a chame" "got this new comment"
+cat dummy.ini
+rm -f dummy.ini
+
+# Use as include:
+cp -f data.ini dummy.ini
+
+# shellcheck source=main.sh
+source "${__root}/src/ini_val.sh"
+
+echo "--> function: Read 3 values"
+ini_val ./dummy.ini orphan
+ini_val ./dummy.ini connection.host
+ini_val ./dummy.ini software.packages
+ini_val ./dummy.ini comment.command
+
+echo "--> function: Replace three values in-place and show result"
+ini_val ./dummy.ini orphan "no more"
+ini_val ./dummy.ini connection.host "192.168.0.1"
+ini_val ./dummy.ini software.packages "vim"
+
+ini_val ./dummy.ini comment.command "commented" "this key is commited"
+ini_val ./dummy.ini comment.new_command "commented too" "last addition will be moved downwards again after next command"
+ini_val ./dummy.ini comment.command "works like a chame" "got this new comment"
+cat dummy.ini
+rm -f dummy.ini

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/scenario/main-debug/run.sh

@@ -0,0 +1,12 @@
+#!/usr/bin/env bash
+set -o pipefail
+set -o errexit
+set -o nounset
+# set -o xtrace
+
+__dir="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+__root="$(cd "$(dirname "$(dirname "$(dirname "${__dir}")")")" && pwd)"
+
+echo "ACCPTST:STDIO_REPLACE_DATETIMES"
+
+env LOG_LEVEL=7 bash "${__root}/main.sh" -f /tmp/x

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/scenario/main-help/run.sh

@@ -0,0 +1,12 @@
+#!/usr/bin/env bash
+set -o pipefail
+set -o errexit
+set -o nounset
+# set -o xtrace
+
+__dir="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+__root="$(cd "$(dirname "$(dirname "$(dirname "${__dir}")")")" && pwd)"
+
+echo "ACCPTST:STDIO_REPLACE_DATETIMES"
+
+bash "${__root}/main.sh" -f /tmp/x -h

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/scenario/main-longopt/run.sh

@@ -0,0 +1,16 @@
+#!/usr/bin/env bash
+# set -o pipefail
+# set -o errexit
+set -o nounset
+# set -o xtrace
+
+__dir="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+__root="$(cd "$(dirname "$(dirname "$(dirname "${__dir}")")")" && pwd)"
+
+echo "ACCPTST:STDIO_REPLACE_DATETIMES"
+
+(
+  env LOG_LEVEL=6 bash "${__root}/main.sh" --file /tmp/x;
+  env LOG_LEVEL=6 bash "${__root}/main.sh" --file=/tmp/x;
+  env LOG_LEVEL=6 bash "${__root}/main.sh" -f /tmp/x
+) 2>&1 |grep arg_f

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/scenario/main-nocolor/run.sh

@@ -0,0 +1,12 @@
+#!/usr/bin/env bash
+set -o pipefail
+set -o errexit
+set -o nounset
+# set -o xtrace
+
+__dir="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+__root="$(cd "$(dirname "$(dirname "$(dirname "${__dir}")")")" && pwd)"
+
+echo "ACCPTST:STDIO_REPLACE_DATETIMES"
+
+env LOG_LEVEL=7 NO_COLOR=true bash "${__root}/main.sh" -f /tmp/x

vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/vendor/git.knownelement.com/ExternalVendorCode/bash3boilerplate/test/scenario/main-repeated/run.sh

@@ -0,0 +1,19 @@
+#!/usr/bin/env bash
+# set -o pipefail
+# set -o errexit
+set -o nounset
+# set -o xtrace
+
+__dir="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+__root="$(cd "$(dirname "$(dirname "$(dirname "${__dir}")")")" && pwd)"
+
+echo "ACCPTST:STDIO_REPLACE_DATETIMES"
+
+(
+  env LOG_LEVEL="${LOG_LEVEL:-6}" bash "${__root}/main.sh" -f dummy -i simple_input -i "input_in_quotes" -i "input with spaces" -i "input with \"quotes\"" -i last_input
+) 2>&1 |grep arg_i -A 5
+
+(
+  env LOG_LEVEL="${LOG_LEVEL:-6}" bash "${__root}/main.sh" -x -f dummy -x -x
+  env LOG_LEVEL="${LOG_LEVEL:-6}" bash "${__root}/main.sh" -f dummy -xxxx
+) 2>&1 |grep arg_x