-
-
Notifications
You must be signed in to change notification settings - Fork 124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Progress thread: PHP #240
Comments
It would be useful to have a composer translator and php builder, perhaps taking inspiration from https://github.com/svanderburg/composer2nix I see the composer.lock file format does have a |
I sometimes have to touch PHP and I see that there's often a Also, some PHP modules seem to use relative imports to get configuration from the main project, or is that rare? So if the Basically, I'm wondering how the vendor dir would best be built. |
Some frameworks also have composer plugins which add their own php files. Case in point Symfony flex |
So, two modes, one just symlinks a vendor dir (when all components behave), and the other mode copies the entire thing? |
It would be cool if we test this packaging solution against demo repos of popular frameworks like symfony demo: https://github.com/symfony/demo Having demo apps working out of the box would be a great DX for nix usage in php ecosystem |
It is also a good way to document how to build php apps which depend on nodejs/webpack for their front-end using dream2nix since it supports building packages for multiple ecosystems. |
See dream2nix indexers feature: https://nix-community.github.io/dream2nix/intro/indexers.html We could implement a PHP indexer to produce a list of the X most well known php github projects etc. Alternatively there already exists an ecosystem agnostic indexer Apart from that all subsystems in dream2nix should provide a usage example under |
|
PHP has standardized on composer as it's package manager, would be great to support it here.
The text was updated successfully, but these errors were encountered: