mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-10 12:47:04 +00:00
aceb5295efmoved Cosmos, Quick Setup and Credits out of the committed role READMEs and into the documentation build's own scratch checkout, so a committed copy can no longer go stale when the metadata moves. Merging feature/designer (ebad39422c) took origin/main's side of those files, which still carries them, and reinstated all 290 along with the cosmos make target and its i8cos alias. tests/lint/ansible/roles/test_readme.py hard-fails on a committed copy, and the reinstated Credits block credited one person with two URLs, which tripped the credits-attribution lint as well. Stripped with the repository's own fence-aware parser against MANAGED_SECTIONS, not with a line filter: the Cosmos block holds a mermaid fence a naive filter would cut through. The result is byte-identical toaceb5295effor every README that carries no prose change since. The cosmos target wrote the forbidden section straight back into the checkout, so it goes with them. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
24 lines
1.1 KiB
Markdown
24 lines
1.1 KiB
Markdown
# Global JavaScript Injector for NGINX
|
||
|
||
## Description
|
||
|
||
This Ansible role injects a custom JavaScript snippet into all HTML responses served by NGINX. It leverages NGINX’s `sub_filter` to seamlessly insert your application-specific script just before the closing `</head>` tag, ensuring that your code runs on every page load, which is useful for global feature flags, analytics, or UI enhancements.
|
||
|
||
## Overview
|
||
|
||
This role injects a custom JavaScript snippet into Nginx-served HTML responses via sub_filter.
|
||
|
||
## Features
|
||
|
||
- **One-line Script Injection**
|
||
Collapses your JavaScript into a single line and injects it via `sub_filter` for minimal footprint and maximal compatibility.
|
||
|
||
- **Easy CSP Integration**
|
||
Automatically computes and appends a CSP hash entry for your script, so you can lock down Content Security Policy without lifting a finger.
|
||
|
||
- **Conditional Activation**
|
||
Activates only when you enable the `javascript` feature for a given application, keeping your server blocks clean and performant.
|
||
|
||
- **Debug Mode**
|
||
Supports an `MODE_DEBUG` flag that appends optional `console.log` statements for easier troubleshooting in staging or development.
|