wdevs/unitdore
5
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 8 Wiki Activity

Add template support for generated unit files #2

New Issue
Closed
opened 2026-04-03 13:57:12 +00:00 by sgcommand · 1 comment
sgcommand commented 2026-04-03 13:57:12 +00:00
Member
Copy Link
Copy Source

Allow users to provide their own .service file template to override the built-in one.

Use cases

  • Add custom [Unit] dependencies (Requires=, After=docker.service, etc.)
  • Set environment variables (Environment=, EnvironmentFile=)
  • Change restart policy, timeouts, resource limits
  • Add ExecStartPre / ExecStartPost hooks

Proposed config

template: /etc/unitdore/unit.service.tmpl  # optional path to custom template

Template uses Go text/template with the same templateData struct already in systemd/generator.go. Built-in template is used as fallback if no custom template is set.

Per-unit override

Also consider allowing per-unit template overrides:

units:
  - name: nginx
    template: /etc/unitdore/templates/nginx.service.tmpl
Allow users to provide their own `.service` file template to override the built-in one. ## Use cases - Add custom `[Unit]` dependencies (`Requires=`, `After=docker.service`, etc.) - Set environment variables (`Environment=`, `EnvironmentFile=`) - Change restart policy, timeouts, resource limits - Add `ExecStartPre` / `ExecStartPost` hooks ## Proposed config ```yaml template: /etc/unitdore/unit.service.tmpl # optional path to custom template ``` Template uses Go `text/template` with the same `templateData` struct already in `systemd/generator.go`. Built-in template is used as fallback if no custom template is set. ## Per-unit override Also consider allowing per-unit template overrides: ```yaml units: - name: nginx template: /etc/unitdore/templates/nginx.service.tmpl ```
warkanum commented 2026-04-03 14:00:58 +00:00
Owner
Copy Link
Copy Source

With this feature we must have the ability to get all the variables we can use. maybe a list-variables command that lists the [variable name] and what it does and is for.

With this feature we must have the ability to get all the variables we can use. maybe a list-variables command that lists the [variable name] and what it does and is for.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Medium
3
The priority is medium
Priority
Low
4
The priority is low
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
Status
Abandoned
3
Somebody has started to work on this but abandoned work
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
hein (Hein) root sam sgcommand (SG Command) warkanum (Warky)
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: wdevs/unitdore#2