Jan Böhmer

Im currently working on a system, where you can configure (most) of Part-DB settings using the web frontend. If that is existing, then settings like this can be added.

Exposing the info provider datastructures should be relatively easy to implement via the API. Directly having API endpoint to create a part from it, is most likely more difficult. And...

How does the format of the IPNs you use look like? The problem is that there could be many different formats, which may not be configurable only with your described...

You need to remove the quotes around DEFAULT_URI. See issue #427 Besides the Default URI currently is not really required besides when you want to use SAML. More important is...

> Can confirm removal of the quotes has resolves the HTTP 500. However, I can't say the same about setting TRUSTED_PROXIES and the Part-DB Docker container continuing to point the...

This should be fixed with the latest commit from the master branch.

The main problem, is that attachments (similar to parameters) can belong to different elements, and there are different classes to model that. However when trying to create a new attachment...

Currently its not possible to upload files via API and its also not possible to let Part-DB download files. In the moment you can only do that via the WebUI.

It's not "intended" by me, but that's what the json merge specification says, and how the API framework works. I tried out some stuff, and there seems to be no...

With the latest commits, the POST endpoint for attachments and parameters work fine. The attachment type is normally autodetected on the IRI of the `element` property passed. So no need...