Added support for host's ZSH terminal configuration #53
Conversation
- Installed Zsh and set it as the default shell using CMD. - Added Antibody for plugin management and configured Zsh with autosuggestions and syntax highlighting. - Set up `.zshrc` with a default theme, aliases, and plugin sourcing. - Ensured compatibility with Alpine Linux by removing unsupported `chsh` command. - Configured default commands to launch Zsh in the container.
Kavignon
added
Devcontainer
|
So here, I've tried to mount the powerlevel10k theme from my host machine. It could be that other developers aren't using that theme or don't want to use it by default (which is fine). It's already way better (IMO) for UX than the default theme that came with the default Bash or Zsh in the container before. So, the mounting could have been more successful; we got to set the theme when opening a container session, which is annoying but not the end of the world. Because I want the support for my theme ASAP, I'll consider the 'matter closed' but open the following issue to get that fix whenever possible. With that, I made another update to the container image: https://github.com/Elixir-journey/elixir-kickoff/pkgs/container/elixir-kickoff/323023919?tag=latest. |
This task was created because I wanted to replicate my development environment as closely as possible in a dev container.
We can now pull the host's ZSH terminal configuration using the template repository.
Just in case of handling plugins dynamically, the container is smart enough to have a fallback in case of errors when trying to perform installs.
Due to changes occurring in development and to ensure that we'd have the correct image version, I pushed the latest container image to the registry: https://github.com/Elixir-journey/elixir-kickoff/pkgs/container/elixir-kickoff/323006964?tag=latest
Soon, this will become automated to reduce the risk of forgetting to update it.