102 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
jknapp	87f154cdc8	refactor(litespeed): drop setUIDMode for shared lsphp + cut opcache 128→32M ... OLS runs as the customer user end-to-end (server-level user/group set by create-vhost-litespeed.sh), so lsphp inherits that uid without per-request suEXEC. Eliminates the per-httpd-worker lsphp instance fan-out — one shared lsphp parent now serves all httpd workers via the shared socket. Combined with opcache.memory_consumption 128→32M, brain-jar measured shmem dropped from ~880 MiB → 32 MiB and memory.current from ~1.1 GiB → 67 MiB at the 1.5 GiB cap. No new oom_kills since the change. Safe because cac-litespeed is one-customer-per-container — the container boundary is the privsep boundary. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-06-02 20:06:56 -07:00
jknapp	f463519998	tune(litespeed): bump LSPHP_WORKER_ESTIMATE_MB 115 → 130 ... 115 was set from idle-state per-worker memory. Active workers on heavy WP/Divi grow to ~130-150 MB (shmem + anon + file), and the 115 formula gave brain-jar.com CHILDREN=8 at 1 GiB — which produced 142 OOM-kills overnight because there was zero headroom once page renders started. 130 backs off slightly on the bigger sites: 512 MiB: 3 workers (unchanged) 1 GiB: 7 workers (was 8 — brain-jar's failure point) 1.5 GiB: 11 workers (was 12) 2 GiB: 15 workers (was 17) 4 GiB: 30 workers (was 33) Per-site FPM_MAX_CHILDREN override still wins for sites that need tighter caps regardless of formula default. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-06-02 18:54:28 -07:00
jknapp	03cca745f7	feat(litespeed): wire up dynamic LSAPI tuning + idle reduction ... Two correctness fixes and a tuning improvement. CORRECTNESS: 1. Strip the stock 'extProcessor lsphp' from httpd_config.conf before appending ours. Previously the stock block (hard-coded PHP_LSAPI_CHILDREN=10 regardless of container memory) always won because our APPEND fragment didn't include an extProcessor block. detect-memory-litespeed.sh was computing LSAPI_CHILDREN but never plumbing it anywhere — silent dead code. 2. Bump LSPHP_WORKER_ESTIMATE_MB from 96 → 115 per the 2026-06-02 memory-sizing finding (vantagehealth OOM-spawn loop). Each lsphp carries ~115 MB shmem-rss accounted per worker. 115 MB matches the real per-worker baseline. TUNING (idle reduction, the original ask): - LSAPI_MAX_IDLE_CHILDREN=2 (was CHILDREN/2 = 5 default) - LSAPI_MAX_IDLE=60s (was 300s default) - PHP_LSAPI_MAX_REQUESTS=500 (recycle workers, prevents bloat) - memSoftLimit=1024M / memHardLimit=1500M per worker (RLIMIT_AS; catches runaway scripts at the worker level, cgroup still backstops the container) Effective LSAPI_CHILDREN per container: 2 GiB → ~17 (was 10 — brain-jar was saturating) 1 GiB → ~8 512 MiB → ~3 (cap-marginal per the memory note; bump container if site grows) Dropped LSAPI_MEM_SOFT/HARD computation in detect-memory: AVAILABLE/CHILDREN was conflating VSZ with RSS-budget arithmetic and would have killed legitimate workers. The 1024/1500 hard-coded values in the template comfortably fit typical Divi/WooCommerce VSZ (280-365 MB). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-06-02 16:36:25 -07:00
jknapp	d1c3cfadc0	feat(litespeed): make log paths drop-in compatible with cac:phpNN ... OLS now writes: access -> /home/$user/logs/apache/access_log error -> /home/$user/logs/apache/error_log PHP -> /home/$user/logs/php-fpm/error.log Matches the cac:phpNN bundled image convention exactly, so existing WHP log-gathering code (whp-traffic-aggregator.php, process-log-review.php) works for migrated sites without any panel-side changes. Customer-facing paths are stable across migrations — "where do I find my access log?" gets the same answer regardless of image family. Server-level OLS logs (/usr/local/lsws/logs/) are unchanged — those are internal diagnostics, not customer-relevant. PHP error_log is set via a runtime-rendered tiny ini in lsphp's scan dir (can't be in the static lsphp-overrides.ini because the path is per-customer). Customers on the four whp01 migrations (alphaone, peptides, shadowdao, brain-jar) need a container recreate after CI publishes the new tags. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-06-02 10:53:44 -07:00
jknapp	80fa06592b	perf(litespeed): defer mariadb-server + memcached install to DEV runtime ... Drops these from the build-time apt install in Dockerfile.litespeed; they now install at entrypoint time only when environment=DEV, guarded by 'command -v mysqld' so container restarts skip the apt step. Mirrors the cac:phpNN pattern. The mysql CLI client is already in the litespeedtech/openlitespeed base, so wp-cli + DEV creds-bootstrap still work without a build-time client install. Measured (php83 / OLS 1.8.4): PROD image: 1.64 GB -> 1.20 GB (~440 MB savings) PROD first-200 boot: unchanged at ~1.5s DEV first boot: ~51s (apt install cost — one-time per container) DEV second boot: ~6s (cache hit, same as PROD) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-06-02 08:26:19 -07:00
jknapp	9e13571d61	Drop stale configs/litespeed/vhconf.tpl ... Leftover from v1 direct-virtualHost iteration. Superseded by site-template.tpl when we switched to the vhTemplate + member pattern. Nothing references it in scripts/ or configs/; was only included in the initial commit by oversight. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-06-02 07:33:06 -07:00
jknapp	55c28a0c11	Add cac-litespeed image family (OpenLiteSpeed, native LSAPI) ... New paid-tier per-customer image built on litespeedtech/openlitespeed:1.8.4-lsphpNN. Matrix: 8.1-8.5. Native LSAPI suexec to customer uid, server-level LSCache, all WP/WooCommerce extensions (memcached, redis, imagick, mbstring, etc.) baked in. Files: - Dockerfile.litespeed (FROM prebuilt LiteSpeed base, layers wp-cli/composer/mariadb) - configs/litespeed/{httpd_config,site-template,lsphp-overrides}.tpl - scripts/{entrypoint,create-vhost,detect-memory}-litespeed.sh + install-lscache-wp.sh CI: new Build-LiteSpeed-Images matrix job. OLS_VERSION pinned to 1.8.4 (only release with prebuilt images for all 5 PHP versions on Docker Hub). Spec: whp/docs/superpowers/specs/2026-06-01-cac-litespeed-design.md Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-06-02 07:32:47 -07:00
Claude Code	1756d496e5	detect-memory: raise PHP_WORKER_ESTIMATE_MB default 60→128 ... The 60 MB worker estimate was optimistic for plugin-heavy WordPress and WooCommerce stacks. Concrete measurement on alphaone 2026-06-01: Container memory : 1024 MiB (later 2048 MiB) Pool sized by formula : pm.max_children = (1024-100)/60 = 15 Actual per-worker RSS : ~193 MB (anon+file+shmem from kernel OOM dumps) Worst-case peak : 15 × 193 MB ≈ 2.9 GB That math put traffic-burst peak demand well over the container cap, producing 1,586 cumulative oom_kills across alphaone's two containers over 18 days and intermittent fork-starvation for unrelated tenants on the host. 128 MB is a more realistic baseline: closer to actual WP+Woo+page- builder worker footprint, still conservative enough that lighter sites continue to get reasonable concurrency. The matrix at common container tiers: Tier (MiB) | old children | new children | new peak demand 256 | 2 (floored) | 2 (floored) | ~256 MB 512 | 6 | 3 | ~384 MB 768 | 11 | 5 | ~640 MB 1024 | 15 | 7 | ~896 MB 2048 | 15 (capped*) | 15 | ~1.9 GB (* old formula returned 32 at 2 GiB but production containers were booted at lower tiers and never recalculated; see whp01 audit.) Existing containers keep their boot-time pm.max_children until they are recreated — this change only affects new containers. Customers or operators can override per-container via FPM_MAX_CHILDREN env.	2026-06-01 08:23:09 -07:00
jknapp	d5d027c0ab	chore(ci): trigger fresh build to verify older PHP tags repopulate ... The registry currently only carries cac:{latest,php84,php85} and cac-fpm:{latest,php84,php85}, even though run #49's runner log shows all 14 jobs (74,80,81,82,83,84,85 × cac, cac-fpm) successfully pushed on 2026-04-02. The older manifests have since been deleted from the registry — direct probe by digest returns 404, so it's not just an orphaned-tag situation. We do not believe there is an active cleanup process. This empty commit triggers a fresh push so we can confirm the workflow is still producing all 14 images and that the tags persist after build. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-29 07:59:12 -07:00
jknapp	28bb1055da	Use proxy_block placeholder in vhost template for FPM load balancing ... Replaced hardcoded SetHandler + ProxyFCGISetEnvIf directives with a ~~proxy_block~~ placeholder. The shared_httpd_manager generates either a direct SetHandler (single container) or a mod_proxy_balancer config (multiple containers) depending on the site's container count. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-02 09:03:11 -07:00
jknapp	e9604b8721	Fix shared httpd log tailing for dynamically added vhosts ... The entrypoint used 'tail -f /var/log/httpd/*' which expands the glob at startup. Log files created later (when new vhost configs are added) were never tailed, so 'docker logs' showed nothing for sites added after the container started. Replaced with a loop that re-discovers log files every 60 seconds and restarts tail to include new ones. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-01 22:22:10 -07:00
jknapp	e81b0df5b8	Reduce idle PHP-FPM memory footprint ... Opcache: - memory_consumption: 128MB → 64MB (most WordPress sites use <40MB) - max_accelerated_files: 10000 → 4000 (sufficient for WordPress) - revalidate_freq: 2s → 60s (reduce stat() calls in production) - enable_cli: Off (don't cache scripts run from command line) FPM workers: - process_idle_timeout: 10s → 5s (faster worker teardown when idle) - max_requests: 500 → 200 (recycle workers sooner to release leaked memory) These changes primarily reduce the baseline memory of idle containers where opcache was reserving 128MB even for small sites. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-01 15:58:42 -07:00
jknapp	c65f533dcc	Add HEIC/HEIF/AVIF support + fix MariaDB repo for AlmaLinux 10 ... Added ImageMagick-heic package to both Dockerfile and Dockerfile.fpm. This is a separate EPEL subpackage that provides HEIC, HEIF, and AVIF format support via libheif. Without it, ImageMagick is installed but cannot process iPhone photos and modern image formats. Also fixed MariaDB repo URL: AlmaLinux 10 uses $releasever=10 but MariaDB mirrors don't have an 'almalinux10' directory. Changed to 'rhel10' which is the supported path for EL10 derivatives. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-01 15:48:58 -07:00
jknapp	c6f1f42987	Final vhost template: SetHandler + ProxyFCGISetEnvIf for both paths ... Reverts from ProxyPassMatch back to SetHandler + ProxyFCGISetEnvIf. ProxyPassMatch couldn't override DOCUMENT_ROOT (Apache sets it as a CGI param after all directives run). SetHandler with unconditional ProxyFCGISetEnvIf correctly overrides both: - DOCUMENT_ROOT: set to /home/{user}/public_html (FPM path) - SCRIPT_FILENAME: constructed from DOCUMENT_ROOT + SCRIPT_NAME This fixes WordFence WAF and other plugins that use DOCUMENT_ROOT to locate config/log files. Tested on live sites with WordPress pretty URLs, wp-admin, static assets, and WordFence WAF optimization. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-01 13:58:11 -07:00
jknapp	e20f5620d7	Fix DOCUMENT_ROOT for PHP-FPM in shared httpd mode ... WordPress plugins like WordFence use $_SERVER['DOCUMENT_ROOT'] to locate config/log files. With ProxyPassMatch, Apache sends its own mount path (/mnt/users/...) as DOCUMENT_ROOT, which doesn't exist in the FPM container. ProxyFCGISetEnvIf can't override DOCUMENT_ROOT when using ProxyPassMatch (Apache sets it after the directive evaluates). Instead, set it via the FPM pool config's env[] directive which takes precedence. create-php-config.sh now adds env[DOCUMENT_ROOT] = /home/$user/public_html when in TCP listen mode (shared httpd), giving PHP the correct path. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-01 13:04:53 -07:00
jknapp	1490bde56e	Switch shared vhost from SetHandler to ProxyPassMatch for PHP-FPM ... SetHandler + ProxyFCGISetEnvIf doesn't work for path remapping because reqenv('SCRIPT_FILENAME') is empty when the directive evaluates with the SetHandler approach. ProxyPassMatch directly maps .php URLs to the FPM container's filesystem path, bypassing the SCRIPT_FILENAME rewrite issue entirely: ^/(.*\.php(/.*)?)$ -> fcgi://fpm:9000/home/{user}/public_html/$1 Static assets (CSS, JS, images) bypass the proxy since they don't match \.php and are served directly by Apache from the read-only mount. Tested and confirmed working on live site with WordPress (including pretty URLs via .htaccess mod_rewrite). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-01 12:50:54 -07:00
jknapp	e5e055d198	Fix ProxyFCGISetEnvIf syntax for SCRIPT_FILENAME rewrite ... The previous expr= with s|...|...| substitution syntax doesn't exist in Apache expressions — it silently failed, leaving SCRIPT_FILENAME pointing to /mnt/users/ which PHP-FPM can't find. Fixed to use regex match in the conditional with backreferences: reqenv('SCRIPT_FILENAME') =~ m#^/mnt/users/([^/]+)/([^/]+)/public_html(.*)# -> /home/$1/public_html$3 This is also generic (captures user from the path) so the template no longer needs per-user placeholder substitution for this directive. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-01 12:32:52 -07:00
jknapp	c68b555a5f	Fix PHP-FPM path mismatch in shared httpd vhost template ... The shared httpd serves files from /mnt/users/{user}/{domain}/public_html but PHP-FPM containers have them at /home/{user}/public_html. When Apache proxied PHP requests via fcgi, SCRIPT_FILENAME pointed to the Apache path which doesn't exist inside the FPM container, causing "File not found". Added ProxyFCGISetEnvIf to rewrite SCRIPT_FILENAME from the shared httpd path to the FPM container path before proxying the request. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-01 12:22:53 -07:00
jknapp	7f7cb456f0	Add openssl to package installs for AlmaLinux 10 ... AlmaLinux 10 base image does not include openssl by default (AL9 did). Add it explicitly to all three Dockerfiles since it's needed for self-signed cert generation. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-01 11:11:10 -07:00
jknapp	dc6ce2bf12	Upgrade base image from AlmaLinux 9 to AlmaLinux 10 ... Bump all three Dockerfiles to almalinux/10-base with matching EPEL 10 and Remi 10 repository URLs. AlmaLinux 10.1 has been stable since Nov 2025. All PHP versions (7.4-8.5) confirmed available via Remi for EL10. Also removes --allowerasing from shared-httpd Dockerfile since AL10 base does not ship curl-minimal. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-01 10:55:26 -07:00
jknapp	fc55752379	Fix curl-minimal conflict in shared-httpd Dockerfile ... The almalinux/9-base image ships curl-minimal which conflicts with the full curl package. Add --allowerasing to allow dnf to replace it. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-01 10:44:24 -07:00
jknapp	367da7806c	Fix ImageMagick install: use EPEL packages instead of upstream RPMs ... The official ImageMagick 7.1.2-18 RPMs require GLIBC 2.38 which is not available on AlmaLinux 9 (ships GLIBC 2.34). Switch to EPEL-provided ImageMagick packages which are built for EL9 and guaranteed compatible. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-01 10:44:03 -07:00
jknapp	a5cb45a386	Install latest ImageMagick 7.1.2-18 from official RPMs ... Adds ImageMagick and ImageMagick-libs from the official CentOS x86_64 RPMs before PHP installation so php-pecl-imagick links against the latest version. Applied to both Dockerfile (standalone) and Dockerfile.fpm (shared httpd mode). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-01 10:15:15 -07:00
jknapp	c78167871c	Add shared httpd + PHP-FPM-only container architecture ... Separate Apache and PHP-FPM into distinct container roles to reduce per-customer memory overhead on shared servers. Adds three new images: - Dockerfile.fpm: PHP-FPM only (no Apache), listens on TCP port 9000 - Dockerfile.shared-httpd: Apache only (no PHP), with SSL and proxy_fcgi - Existing Dockerfile unchanged for standalone mode Key changes: - detect-memory.sh: CONTAINER_ROLE env var (combined/fpm_only/httpd_only) controls the memory budget split - create-php-config.sh: FPM_LISTEN env var for TCP port vs Unix socket, added /fpm-ping and /fpm-status health endpoints - New entrypoints for each container role - tune-mpm.sh for hot-adjusting Apache MPM settings - shared-vhost-template.tpl with proxy_fcgi and SSL on port 443 - CI/CD builds all three image types in parallel Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-01 10:08:00 -07:00
jknapp	87c4f2befc	Optimize Apache & PHP-FPM memory for lower idle usage ... Switch PHP-FPM from pm=dynamic to pm=ondemand (zero idle workers), auto-detect container memory via cgroups to calculate appropriate limits, and generate Apache MPM config at runtime. All tuning values are now overridable via environment variables. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-02-25 18:52:15 -08:00
jknapp	a153385d8f	Adding support for PHP 8.5	2026-02-08 07:57:04 -08:00
jknapp	468bc7b088	Move user crontab to persistent home directory ... - Created user-specific crontab file at /home/$user/crontab - Crontab now persists through container restarts/refreshes - Users can manage their own cron jobs by editing their crontab file - Automatically loads user crontab on container start - Updated DEV environment to use user crontab for MySQL backups 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>	2025-08-13 07:36:35 -07:00
jknapp	8b9708e351	Add essential development tools to container ... Added git, nano, rsync, unzip, zip, mariadb client, bind-utils, jq, patch, nc, tree, and dos2unix to provide developers with commonly needed tools for PHP development and debugging. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>	2025-08-13 07:19:25 -07:00
jknapp	92ed9885ec	Remove php-ioncube-loader from PHP 8.1 to fix Composer installation ... The php-ioncube-loader package is incompatible with PHP 8.1 and was causing a segmentation fault (exit code 139) when the Composer installer tried to run PHP. This aligns PHP 8.1 with other PHP versions that already had ioncube-loader removed. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>	2025-08-12 16:41:33 -07:00
jknapp	844b21bd7c	Add Composer to container for PHP dependency management ... - Install Composer globally at /usr/local/bin/composer - Available for all PHP versions and users - Also includes previously added microdnf and less utilities 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>	2025-08-12 15:50:18 -07:00
jknapp	3d903b437f	Fix PHP error log path to use correct user directory ... PHP error logs were incorrectly being written to /etc/httpd/logs/error_log instead of the expected /home/$user/logs/php-fpm/ directory. Updated the php_admin_value[error_log] setting to point to the proper location. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>	2025-07-31 10:21:15 -07:00
jknapp	152dd413ef	adding claude infor	2025-07-28 07:29:03 -07:00
jknapp	617fdbcd21	Add PostgreSQL support for all PHP versions ... - Added postgresql-devel package to Dockerfile for client libraries - Added php-pgsql extension to all PHP versions (7.4, 8.0, 8.1, 8.2, 8.3, 8.4) - Enables PHP applications to connect to PostgreSQL databases 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>	2025-07-28 07:27:39 -07:00
jknapp	154f42ae09	Optimize memory usage for Apache and PHP-FPM, remove ioncube-loader ... - Apache mpm_event: Reduced StartServers from 10 to 2, adjusted spare threads and worker limits for container environments - PHP-FPM: Switched from static to dynamic process management with lower process counts (5 max children instead of 10) - Removed php-ioncube-loader from PHP 8.0 installation - Expected memory reduction: 60-70% in idle state while maintaining responsiveness 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>	2025-07-20 16:52:04 -07:00
jknapp	b5857d73c2	Fix issue where PHP Sessions were not working as expected	2025-07-20 12:06:15 -07:00
jknapp	b1de7021a3	fix build issues	2025-07-16 08:01:07 -07:00
jknapp	9f8beb45b8	Switching builds to include PHP version to limit memory requirements on deploy. ... improve build size and speed for images.	2025-07-16 07:55:03 -07:00
jknapp	88f462eb04	Updated the README.md ... Added a healthcheck to the container adjusted Apache limits for memory consumption switch to microdnf for improved memory usage	2025-07-16 05:56:33 -07:00
jknapp	e7b0bce666	Update MariaDB Version	2025-06-14 16:02:00 -07:00
jknapp	5a097034c4	Update MariaDB Version	2025-03-16 11:12:46 -07:00
jknapp	a41157fad0	fix url	2025-03-16 10:58:25 -07:00
jknapp	4fd7ee465a	Adding support for PHP 8.4 and upgrading MariaDB to 11.4.5	2025-03-16 10:43:16 -07:00
Josh Knapp	8a7490ef98	forgot to add iproute	2024-12-17 21:52:38 -08:00
jknapp	9df776ef08	Merge pull request 'fix path to remote_ip.conf' (#18) from update-to-fix-ip-and-options-issue into trunk ... Reviewed-on: #18	2024-12-18 05:47:59 +00:00
Josh Knapp	7bab6d39fc	fix path to remote_ip.conf	2024-12-17 21:47:32 -08:00
jknapp	9630408ca0	Merge pull request 'Added fix for issues found while setting up anhonesthost' (#17) from update-to-fix-ip-and-options-issue into trunk ... Reviewed-on: #17	2024-12-18 05:44:51 +00:00
Josh Knapp	49c5438866	Added fix for issues found while setting up anhonesthost	2024-12-17 21:44:09 -08:00
jknapp	885deb5979	Merge pull request 'fix spacing on versions' (#16) from fix-readme into trunk ... Reviewed-on: #16	2024-10-16 01:50:31 +00:00
Josh Knapp	23253e9f37	fix spacing on versions	2024-10-15 18:50:11 -07:00
jknapp	fde567d5f9	Merge pull request 'Fix/Update README.md' (#15) from fix-readme into trunk ... Reviewed-on: #15	2024-10-16 01:45:51 +00:00