We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi, i like your work to create a more modern envsubst combined with statically compiling with musl, it's a very portable and efficient solution.
envsubst
I have a minor request: is it possible to implement write the output in the same file as input? (without using some other tool like sponge)
sponge
ex:
cat test.txt test: it $TEST export TEST=work renvsubst --variable=TEST --input=test.txt --output=test.txt file test.txt test.txt: empty
if the output file is different, it works perfectly:
renvsubst --variable=TEST --input=test.txt --output=test2.txt cat test2.txt test: it work
The text was updated successfully, but these errors were encountered:
hi @m47730
I like your idea! I’ll try to add a flag for this.
In the meantime, you can use something like this:
cat test.txt test: it $TEST export TEST=work cat test.txt | ./renvsubst | tee test.txt file test.txt test.txt: test: it work
It is ugly, but working.
Sorry, something went wrong.
great to hear it!
I used your solution in the meantime, i ended up on something like:
# substitute variables in the same file of input ./renvsubst --variable TEST --input test.txt | tee test.txt 1>/dev/null
Thank you
No branches or pull requests
Hi,
i like your work to create a more modern
envsubst
combined with statically compiling with musl, it's a very portable and efficient solution.I have a minor request: is it possible to implement write the output in the same file as input? (without using some other tool like
sponge
)ex:
if the output file is different, it works perfectly:
The text was updated successfully, but these errors were encountered: