event-dispatcher | Event Dispatcher with a focus on Domain Events | Pub Sub library

I am trying to build a docker image with a PHP application in it.

This application installs some dependencies via composer.json and, after composer install, needs some customizations done (eg some files must be copied from vendor folder into other locations and so on).

So I have written these steps as bash commands and putted in the composer.json post-install-cmd section.

This is my composer.json (I've omitted details, but the structure is the same):

I have a Symfony bundle on a git repository managed by GitLab. The bundle is added to Symfony using composer and pointing to the gitlab as an additionnal repository.

Everything works fine, the dependency is tracked perfectly and the bundle does work as expected however, in order to optimize my project sources I would like to avoid including the .git folder in the vendor/my-org/my-bundle directory.

Here is a sample of the composer.json of the Symfony project:

./vedor/bin/pimcore-install command getting stuck at 0% in ubuntu 20.04.

Sometimes it goes to 18% and stuck.

I am not able to solve it.

In the error log it show some symfony related warning.

I am trying to create a custom event dispatcher. I have read this article and implemented the code

I want to use jwt token in my symfony project. But i have a problem because when i use: curl.exe -X POST -H "Content-Type: application/json" http://localhost:81/api/login_check -d '{"username": "f.djawid@outlook.com","password":"000000"}'

I get : {"code":401,"message":"JWT Token not found"}

This is my security.yml:

While my end goal is to prevent Swagger UI from losing authentication upon browser reload, I believe I might have found a solution assuming swagger-ui parameters can be changed when using api-platform, and described it at the tail of this post.

A REST API uses Symfony, API-platform and authenticates using JWT and documentation is provided by swagger-ui. On the swagger-ui page, after submitting the apiKey, future requests include it in the header, however, if the browser is refreshed, the authorization token is lost.

There has been some discussion on this topic primarily on this github post and some on this stackoverflow post, and the general consensus seems to be that swagger-ui there is no "official" way to persist tokens.

Overall Swagger UI does not store tokens, and probably on purpose. There is no switch to enable this, but looks like there are little things that can be done to remember a token via cookie, local storage, indexdb, etc and when the page is reloaded, populate the token back in.

The swagger configuration documentation, however, appears to have an Authorization parameter which will allow the authorization data to be persisted upon browser refresh.

• Parameter name: persistAuthorization
• Docker variable: PERSIST_AUTHORIZATION
• Description: Boolean=false. If set to true, it persists authorization data and it would not be lost on browser close/refresh

Assuming I correctly interpret the Swagger documentation, how can the persistAuthorization parameter be set to true?

When modifying config/api_platform.yaml to set persistAuthorization, I received errors Unrecognized option "persistAuthorization" under "api_platform.swagger.api_keys.apiKey". Available options are "name", "type". and Unrecognized option "persistAuthorization" under "api_platform.swagger". Available options are "api_keys", "versions".

Sometimes when Travis CI is building my package, there's a short list of dependencies, like so:

I would like to use a DataProvider for a password reset by token. I have a custom operation on the User entity

I'm quite new at Symfony and struggle with this issue for my internship, when trying to run the project locally :