The current wrangling of the .bash_history is necessary to allow a bind mount (and presumably a volume mount) to override and/or persist the data between container runs.
Let's consider how we expand handling other .bash* files in the home directory.
@tekante said in #1
We'd likely want to copy over .bash_profile and .bashrc if they didn't exist in $TRIGGER_DIR rather than just link like we can with .bash_history.
Specifically I've found that I desire this when working with things like Acquia's BLT toolset which sets up a blt alias in .bash_profile as an alternative to PATH manipulations to get vendor/bin pulled in.
Since it is possible for a user to mount in their own .bash_profile, it may be a good security stance to recommend this be read-only. Outputting a warning if it's writable may be reasonable.
The current wrangling of the .bash_history is necessary to allow a bind mount (and presumably a volume mount) to override and/or persist the data between container runs.
Let's consider how we expand handling other
.bash*files in the home directory.@tekante said in #1
Since it is possible for a user to mount in their own .bash_profile, it may be a good security stance to recommend this be read-only. Outputting a warning if it's writable may be reasonable.