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.
Generally, when sourcing a file, you want to use either ./ or the full path, so what I’d recommend is using:
#!/usr/bin/env bash
source ./name_Env/bin/activate
or
#!/usr/bin/env bash
source /root/environments/name_Env/bin/activate
Though you should also be able to use double-quotes around the source file as well.
#!/usr/bin/env bash
source "./name_Env/bin/activate"
or
#!/usr/bin/env bash
source "/root/environments/name_Env/bin/activate"
You could even set the file to a variable:
#!/usr/bin/env bash
readonly sourceFile="./name_Env/bin/activate"
source ${sourceFile}
or
#!/usr/bin/env bash
readonly sourceFile="/root/environments/name_Env/bin/activate"
source ${sourceFile}