github-starred/newt
2
0
Fork 0
mirror of https://github.com/fosrl/newt.git synced 2026-03-09 07:12:28 -05:00
Code Issues 21 Packages Projects Releases 25 Wiki Activity

[docs improvement] Additional environment variable for blueprint #64

New Issue
Closed
opened 2025-11-19 07:13:07 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-19 07:13:07 -06:00
Owner
Copy Link

Originally created by @didotb on GitHub (Sep 25, 2025).

My newt docker compose file's being ran directly inside my PVE host, which none of my LXC and VMs can see, so I thought using docker compose's labels inside my LXC or VM wouldn't work for me at all, nor did I want to use the newt cli since I didn't want to think about another 3rd party app when things break (I would definitely forget about it).

So I instead added these lines in my newt docker compose file:

environment:
    - BLUEPRINT_FILE=/blueprint.yaml
volumes:
    - /path/to/blueprint.yaml:/blueprint.yaml

to which my blueprint.yaml would have the hostname under targets be the IP of my LXC or VM, and it works fine for my case.

I just thought this would be a good addition, especially to those new to this project, to have this option immediately known to them.

Originally created by @didotb on GitHub (Sep 25, 2025). My newt docker compose file's being ran directly inside my PVE host, which none of my LXC and VMs can see, so I thought using docker compose's labels inside my LXC or VM wouldn't work for me at all, nor did I want to use the newt cli since I didn't want to think about another 3rd party app when things break (I would definitely forget about it). So I instead added these lines in my newt docker compose file: ```yaml environment: - BLUEPRINT_FILE=/blueprint.yaml volumes: - /path/to/blueprint.yaml:/blueprint.yaml ``` to which my blueprint.yaml would have the `hostname` under `targets` be the IP of my LXC or VM, and it works fine for my case. I just thought this would be a good addition, especially to those new to this project, to have this option immediately known to them.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
good first issue
help wanted
Improvement
pull-request
Mirrored from GitHub Pull Request
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/newt#64
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?