Christoph Kappestein

Hi @bangash-92, so I would recommend to create a dedicated `index.html` for production and staging, then you can adjust the url according to the environment.

Hi @justspamjustin, yes this is easy possible but for this you would need to build a custom action in PHP. Basically this is really simple you can take a look...

Hi @gilney-canaltelecom indeed, since we use `vimeo/psalm` as dev dependencies we never run our test cases with `nikic/php-parse` 5.0 since it is not yet supported, but I have just checked...

Hi @Pierre-Lannoy so we have recently added a Domains-Chapter s. https://github.com/apioo/fusio#domains to our readme. In general I would recommend to create an `api.example.com` for the Fusio API and an `developer.example.com`...

It would be really nice if we could merge this, currently it is not possible to install Psalm with PHPUnit 11 since it requires `nikic/php-parser: ^5.0`

So in general the best way is to download the latest release and simply replace the `vendor/` folder and the `composer.json` and `composer.lock` files from the release, then you only...

Hi @gpenin this is indeed currently a wrong behaviour, I have just provided a commit s. https://github.com/apioo/fusio-impl/commit/201697160ac9bf285877caf3decd622280512cf7 to fix this which will be available in the next release

Hi @Entrebear can you show me the `log/app.log` file and also the response of the request to see whether there is an error?

Hi Hanno, do you have the option to switch to Mysql, currently we run our integration tests only against Mysql, Postgres and Sqlite. It looks like our schema contains an...

Hi @wdhwang currently we have no Helm chart but in general this is a good idea, we should add this to our docker repo s. https://github.com/apioo/fusio-docker