Merge _configs/ into config/ for single configuration directory. Update all path references. Changes: - Move _configs/* to config/ - Update .gitignore for new patterns - No code references to _configs/ found Impact: -1 root directory (layout_conventions.md compliance)
46 lines
1.3 KiB
Markdown
46 lines
1.3 KiB
Markdown
# Syntaxis NuShell Templates
|
|
|
|
This directory contains syntaxis-specific NuShell templates that override the default provctl templates.
|
|
|
|
## Files
|
|
|
|
If you need to customize NuShell script generation for syntaxis, add these files:
|
|
|
|
- `export-config.nu.j2` - Generate NuShell script that exports deployment configuration as environment variables
|
|
|
|
## Usage
|
|
|
|
By default, provctl's standard NuShell templates are used. To customize for syntaxis:
|
|
|
|
1. Copy the corresponding template from provctl's config/gen/templates/nushell/
|
|
2. Place it in this directory
|
|
3. Modify for syntaxis-specific needs
|
|
4. Run: `provctl gen deployment --config .provctl/gen.toml`
|
|
|
|
## Example Customization
|
|
|
|
For example, to add syntaxis-specific helper functions:
|
|
|
|
```nushell
|
|
# Syntaxis-specific helpers
|
|
def setup-dev [] {
|
|
"""Set up development environment for syntaxis"""
|
|
# Source deployment config
|
|
source export-config.nu
|
|
|
|
# Custom setup steps...
|
|
}
|
|
|
|
def start-all-services [] {
|
|
"""Start all syntaxis services for development"""
|
|
# Custom service startup...
|
|
}
|
|
```
|
|
|
|
## Fallback Behavior
|
|
|
|
If template files are not present here, provctl will use the default templates from:
|
|
`~/.config/provctl/gen/templates/`
|
|
|
|
This allows syntaxis to use standard templates while having the option to customize later.
|