ships with default vim-theme and vimrc
is it possible to build the containers with a set of configuration files like vimtheme.vim vimrc gitconfig that should be equal across all projects, containers and teammembers?
Activity
We mount the user home directory from the host into each of the L3D containers, all their settings should therefore be available already. That should bring all the Vim settings from the host into the containers.
Or is there anything else required?
Edited by jurgenhaasadded To Do label
mentioned in issue #66 (closed)
hmm mounting the users home-directory is a good idea. like it. however there may be standards in a team and those standards should be shipped with the environment that everyone is supposed to use. So there should be an additional layer. In general it was great to have layers like that:
- user config
- team config
- env config defaults
that means that user config can override team config that can override environmental configs.
marked this issue as related to #74 (moved)
removed the relation with #74 (moved)
-
To answer the question, if and how that can be implemented in L3D it would be helpful to define, how a team/company would manage that on developer laptops/desktops. It seems that if a team/company has a mechanism, to deploy such configurations stacks onto laptops/desktops, that can then be replicated (or just forwarded) into L3D on those hosts.
removed To Do label
-
its not that the company rolls those changes out, but the developers are asked to update their systems with the lastest version of the shared env. so from what i understand a possible scenario would be to have a company-repo that contains a set of files. l3d uses them, in case they are existing at a common set of locations. so the developers would have to update two repos and the settings could be different by teams/companies, but still using l3d.