Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
I don’t see where ${drt} is defined. How is this script run? The environment it is run under may change what variable hold values.
For example, take a script named foo.sh that contains:
#!/bin/bash
echo ${FOO}
If you simply run ./foo.sh it will only print an empty line as ${FOO} has not been defined in the script. You could define it when it is run, like:
- FOO=bar ./foo.sh
This would print bar. The same would happen if you run:
- export FOO=bar
- ./foo.sh
Another possibility is to define its value in a separate file and include it by sourcing that file. Perhaps you are doing that here:
cat >> "/etc/bash.bashrc" <<< "source ~/myAddons/appendix.sh"
source ~/myAddons/appendix.sh /etc/bash.bashrc
If so, my advice would be to use the full path for ~/myAddons/appendix.sh (e.g. /home/username/myAddons/appendix.sh) when possible. The ~ will be expanded differently depending on the user the script is run under. So you will have different results based on how the script is run.