Local development of a PEP561 plugin

[wolflu05]

Hello,

if I have such a structure of plugin and want to develop locally, the easiest way is by placing this folder in a folder which is in INVENTREE_PLUGIN_DIR, but I didn't see the plugin appearing the the UI. Do I need something else to get that to work?

If I place a single file which contains a plugin in the INVENTREE_PLUGIN_DIR, it appears in the UI. What are your recommendations to develop a plugin which consists of a PEP 561 compliant package like shown in the documentation?

[matmair]

@wolflu05 this probalby will take a few posts so it probably would work better as a bug / issue ut I am going to try anyway.

There are a few things that could happen here. Please ensure all following conditions are met. This is all for development. For deploying I would strongly recomment to distribute via pypi or similar indexes.
Requirements:

• plugins are enabled
• plugin_dir points to the right directory
• __init__.py file in plugin_dir -> needed for module dicsovery
• __init__.py file in plugin subdir -> needed for module dicsovery
• inventree-server (the application, not the linux host it runs on) must be restarted once after placing the file
• specific plugin enabled in global settings\plugins or in the admin interface -> defaults to False

I started to use editable installs recently. Quite handy if you work with several plugins and have the same folder structure for all your repos.

[wolflu05]

@matmair Thank you very much, now it's working.
But one thing is not clear to me, what is the purpose of this signature field? And how can I get my plugin a signature?

[matmair]

it is for gpg signatures - if you signed your commits with gpg it will show up here. I am actually thinking about disabeling signature information by default.

[wolflu05]

@matmair This does not really work, as you can see, my last commits in dev are signed and I still have this red box with the no signature warning.

[matmair]

This only works if you:

• a) included git metadata
• b) have gpg installed in our env

I am going to disable this by default becaues it only creates confusion and only a select few users care about this at all.

[wolflu05]

Ok. Thank you for clarification.