New issue
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
Allow user additions to bashrc in web container #926
Comments
I think we should probably have a directory that auto-mounts if it exists, and have the container's .bashrc include scripts in there. That way every request like this could be resolved by the user. |
I changed the title to a more generic solution. I propose that we add .ddev/bash_profile and .ddev/bashrc handling to the container's .bash_profile and .bashrc, so those get included. That way every project can have custom bash setup as needed. |
+1 for this please. |
From #1459 - host gitconfig would be completely reasonable here also. |
@pcambra requested ~/.ssh/config configuration... |
Another related request from @wizonesolutions : Keep bash history around. |
For just doing exactly what was requested here in a post-start hook, Stack Overflow How to add alias on post-start hook? |
Related: Request for composer auth file in #1641 |
…istent bash history, for #926 (#1688) * Make bash history persist in web and db containers, for #926 * Add ddev-router to list of trusted names * Give image names to built web and db images * Use 10.1 Docker mariadb 10.1.40, same as 10.1.40-bionic * ssh-agent and bgsync needs shadow package to allow high userids
Is your feature request related to a problem? Please describe.
Coming from https://github.com/beetboxvm/beetbox I have gotten used to have the
ll
command (short forls -la
) available OOTB when I ssh into the VM. With ddev, I have to type the whole command, which is an annoyance.Describe the solution you'd like
I would like it if
ll
worked out of the box when I ssh to the VM.Describe alternatives you've considered
I can set up the shortcut inside the VM, but having to do this every time I destroy/rebuild a VM is really tedious.
The text was updated successfully, but these errors were encountered: