Conversation
| # https://git-scm.com/docs/git-config#git-config-corepreloadIndex | ||
| RUN git config --global core.preloadindex true | ||
|
|
||
| # Run the s6-based init. |
There was a problem hiding this comment.
Fix the comment, we are not using s6
There was a problem hiding this comment.
Corrected the comment and added customization instructions.
|
How would outrigger/build handle it's nvm stuff? Would it simply override the /init script with it's own entirely (adding in the nvm parts?) |
| if [ -e ~/.bash_history ]; then | ||
| rm -f ~/.bash_history | ||
| fi | ||
| ln -sf $TRIGGER_DIR/.bash_history ~/.bash_history |
There was a problem hiding this comment.
Should we consider expanding this to all of the .bash items in the home directory? 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.
There was a problem hiding this comment.
I think this makes a lot of sense. That seems like something we should do as a follow-up.
That's the current approach, which isn't great but works. Do you think we should get fancier? E.g., have a directory we autoload scripts from? |
|
I don't think we need fancy right now. |
3 participants
Here's a first cut at a CLI base image. The build containers would be rebased onto this.