Issue description:
I am connecting to a GitHub Enterprise playground server as data source to fetch repositories. These playground servers are often not secured with a certificate from an official certification authority, but a self-signed one. This does not go well with git per default.
It is possible to configure git on the Perceval container to work with this certificate, but every time after the container is shut down, this configuration has to be re-done.
Request:
If it is possible to do, it would be a major help to have a persistent configuration option to register this self-signed certificate, which is then picked up by the Perceval container on startup.
Type: Feature Request
Issue description: I am connecting to a GitHub Enterprise playground server as data source to fetch repositories. These playground servers are often not secured with a certificate from an official certification authority, but a self-signed one. This does not go well with git per default.
It is possible to configure git on the Perceval container to work with this certificate, but every time after the container is shut down, this configuration has to be re-done.
Request: If it is possible to do, it would be a major help to have a persistent configuration option to register this self-signed certificate, which is then picked up by the Perceval container on startup.
Error message example: