fix(backend): registry install command

[matmair]

Fixes problems with installing from custom indexes
Also cleans up logic a bit to be easier to understand

Fixes #11460

[netlify]

✅ Deploy Preview for inventree-web-pui-preview canceled.

Name	Link
🔨 Latest commit	c6cfc18
🔍 Latest deploy log	https://app.netlify.com/projects/inventree-web-pui-preview/deploys/6a24412618dee00008a78a82

[matmair]

@vrzh can you qualify if this solves your issue?

[codecov]

Codecov Report

❌ Patch coverage is 94.44444% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 91.49%. Comparing base (4c4e0eb) to head (c6cfc18).

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #11657      +/-   ##
==========================================
+ Coverage   86.57%   91.49%   +4.91%     
==========================================
  Files        1385      979     -406     
  Lines       88870    52449   -36421     
  Branches     9954        0    -9954     
==========================================
- Hits        76943    47989   -28954     
+ Misses      11865     4460    -7405     
+ Partials       62        0      -62     

Flag	Coverage Δ
backend	90.50% <94.44%> (+0.01%)	⬆️
web	?

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
Backend Apps	92.04% <94.44%> (+0.01%)	⬆️
Backend General	93.52% <ø> (ø)
Frontend	∅ <ø> (∅)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[vrzh]

@vrzh can you qualify if this solves your issue?

I am not sure what is the correct way to fill out the InvenTree UI, what are the correct values for "Package Name" and "Source URL". In my original bug report, I have 3 options, is the first one correct?

Package Name: "my_custom_plugin"
Source URL: "https://my-custom-domain.com/python"

[matmair]

That is a difficult question. Anything pip will resolve works - that can be a local package, an http/https repository, any number of vcs repositories.

The option you listed should work.

[vrzh]

@vrzh can you qualify if this solves your issue?

What is a quick way of testing this branch please, ideally through docker? Sorry, I am not very familiar with Inventree dev setup.

I saw here https://docs.inventree.org/en/latest/start/docker/#tagged-images that you can get the latest main using inventree:latest is there something quick and simple I can use in this case?

[SchrodingersGat]

@matmair pushing this to the next release, hoping to get the 1.3.0 out soon

[matmair]

@vrzh we are not releasing docker-images for PRs; you would need a dev setup or build the branch locally; are you able to do that?

[vrzh]

@vrzh we are not releasing docker-images for PRs; you would need a dev setup or build the branch locally; are you able to do that?

Hi, sorry for the delay, it took a while to follow the devcontainer instructions for the first time and getting it working. I think the fix works great, at least I now get the "Plugin installed successfully" toast message. Now I need to work on my plugin :)

FYI I now use the following:

• Package Name: "my_custom_plugin"
• Source URL: "https://my-custom-domain.com/python" (i.e. the root of the repository)

Which is what I would have expected to work - so that is great. In the future I will also test specifying an exact version to install.