I’m working on what should be a simple raspberry pi display project and I came up with the need for a set of ad-hoc python modules that were installable from my gitlab server. It was a bit of a journey. Here are the broad steps:<\/p>\n\n\n\n
git+ssh:\/\/git@gitlabs.example.com...<\/code> for this but I chose to use a gitlabs impersonation token for this since ssh isn’t installed everywhere and sometimes the installation needs a bunch of hints in ~\/.ssh\/config<\/code>.<\/li>- A standard install will be done with pip as follows pip install
git+https:\/\/{user}:{password}@git.example.com\/example-group\/example-project.git<\/code>. If you created a gitlabs impersonation token about, you can substitute it for password here.<\/li><\/ul>\n\n\n\nSometimes I need to edit the installed package that I’m working on. The way to do this is to use the –editable<\/em> flag to pip. To do that you need to specify some extra information to git when checking out the project. I found that this command line: <\/p>\n\n\n\npip install --editable git+https:\/\/{user}:{token}@gitlabs.example.com\/example-group\/example-project.git#egg={module_name}<\/code> <\/p>\n\n\n\nI think that the #egg={module_name} piece provides pip with name of the module as installed. I found the documentation that explains this here: “https:\/\/pip.pypa.io\/en\/stable\/topics\/vcs-support\/”.<\/a> Assuming that you are doing this in a venv, and it doesn’t make sense not to, you’ll get a new directory called venv\/src\/{module_name}<\/code> which has a git checkout of your module so you can edit it to your needs for this particular project.<\/p>\n\n\n\n<\/p>\n","protected":false},"excerpt":{"rendered":"
I’m working on what should be a simple raspberry pi display project and I came up with the need for a set of ad-hoc python modules that were installable from my gitlab server. It was a bit of a journey. Here are the broad steps: Create a gitlabs project for your python module. Since will … <\/p>\n