When I log in to the web console with the given credentials, I am logged in as bash 4.2.
I am attaching the screenshot.
When I log in to the web console with the given credentials, I am logged in as bash 4.2.
I am attaching the screenshot.
Hey Ravi,
Run the following command in your web console:
echo 'export PS1="\u@\h:\w$ "' >> ~/.bashrc && source ~/.bashrc
Explanation:
\u → username\h → hostname\w → current working directory$ → prompt symbolAfter running this, your shell prompt will look like:
username@myhost:~/project$
Hi,
By mistake I made some changes in .bashprofile and now I am getting the following issue after logging in
.
After that, i am not able to enter any command in the terminal.
Hey Ravi,
The issue has been fixed — the broken .bash_profile was causing the terminal to hang, and it has now been corrected.
To clarify how things work in CloudxLab: the web console is essentially just a terminal interface, but it’s not the only way to interact with your environment. All the shell or terminal is doing is running your startup scripts (.bash_profile, .bashrc, etc.) and providing command-line access. If a startup script has an error, the terminal may fail to load, which is what happened in this case.
We can also interact with the same environment through Jupyter’s shell interface, which lets you execute commands without loading the terminal’s startup scripts. This allows us to safely edit or fix configuration files like .bash_profile even when the terminal itself is unresponsive.
So while the shell is a convenient way to check or run commands, the underlying environment can be accessed and managed through other interfaces like Jupyter, which is why we were able to resolve the issue.