For example, I have a .env file with the following contents:
test1=abc
test2=def
Execute the following command:
export $(grep -v '^#' .env | xargs)
You can see this environment variable on your host side. Execute env to view
env
test1=abc
test2=def
Execute the following command:
export $(grep -v '^#' .env | xargs)
You can see this environment variable on your host side.
env
All rsync error codes are listed here, so in scheduling, we can understand the reason for the failure.
There may still be some old programs in some places, which can only run the old system. But you want to be able to execute and install some desired packages, you may try this method. Please note that if this system is important to you, please evaluate it yourself. It is recommended that you have a Docker environment and have a backup image before trying it.
Not sure who will use it, but I encountered it myself, because my home is a floating IP. A software I installed cannot detect that the ppp0 network card is an external network, so changing the name can trick him into successfully installing it.
No Comment
Post your comment