Repository navigation
docs: run a job by hand through systemd-run - #78
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
session-ops run <job> --dry-run, as every job doc gives it, fails on the host withmissing <VAR> in the environment:session-ops rundoes not read the job's env files, its unit loads them as root, and the job's account cannot read them either.deploy/README.mdgives thesystemd-runcommand that runs a job by hand with its account, env files and state directory, and where a job's drop-in names them.expiry.toml.examplepoints to the token-expiry doc instead of the bare command.Docs only.