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	79e3225
🔍 Latest deploy log	https://app.netlify.com/projects/inventree-web-pui-preview/deploys/69d5441c97d5a00008e92943

[matmair]

@vrzh can you qualify if this solves your issue?

[codecov]

Codecov Report

❌ Patch coverage is 62.96296% with 20 lines in your changes missing coverage. Please review.
✅ Project coverage is 90.87%. Comparing base (e91f306) to head (79e3225).
⚠️ Report is 39 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #11657      +/-   ##
==========================================
- Coverage   91.44%   90.87%   -0.58%     
==========================================
  Files         964      964              
  Lines       49847    50214     +367     
==========================================
+ Hits        45585    45630      +45     
- Misses       4262     4584     +322     

Flag	Coverage Δ
backend	89.26% <91.66%> (+0.01%)	⬆️

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

Components	Coverage Δ
Backend Apps	90.92% <62.96%> (-0.80%)	⬇️
Backend General	93.41% <ø> (ø)
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