Facebook
TwitterI deployed a laravel application, i made some changes so the public folder remains in the root and node modules and all dependencies related are inside a folder called laravel. Made some configurations and everything works fine. The problem is the composer scanner does let me choose a path where i have the composer file. I tried copy the file to the root but it will give me some errors because it cannot find the core packages cause they are inside the laravel directory.
Issue Specify folder path for composer for laravel application
Hi,
we're working on a project where we wanted to change both the root directory and the application folder. Switching the root directory went off without a hitch. But changing the application folder for PHP Composer just wouldn't work.
When I click on PHP Composer, there's an option at the top to [Change] the folder. That opens up a small popup titled "Select Folder." But the only thing it shows is the current application folder, no option to create a new one or browse to a different location. So it really doesn't matter whether I click Change Folder or Cancel, because the exact same thing happens: nothing at all.
Any ideas on what might be going on? Solutions?
Thank you.
we're working on a project where we wanted to change both the root directory and the application folder. Switching the root directory went off without a hitch. But changing the application folder for PHP Composer just wouldn't work.
When I click on PHP Composer, there's an option at the top to [Change] the folder. That opens up a small popup titled "Select Folder." But the only thing it shows is the current application folder, no option to create a new one or browse to a different location. So it really doesn't matter whether I click Change Folder or Cancel, because the exact same thing happens: nothing at all.
Any ideas on what might be going on? Solutions?
Thank you.
Hello, is there any update on this? How did you solve this?
I haven't found this one before create my own thread: Issue - PHP Composer application folder can't be changed
I haven't found this one before create my own thread: Issue - PHP Composer application folder can't be changed
Perhaps this support article helps: https://support.plesk.com/hc/en-us/...-extension-the-path-of-the-composer-json-file
Yeah, the SSH command helped. It's a bit unfortunate, because our customers don't have SSH access due to German privacy policies
and we want them to use plesk for their php composer applications.
Is there also a way to remove old applications or enviornments?
In the article someone declined, is that correct? are there updates on this?
Thank you really much @Kaspar
@marc@orxo , we do have an internal task (EXTPHPCOMP-115) for improving the behavior, but I cannot provide an ETA for the release. Currently, the other alternatives, apart from the command already suggested, are:
Unfortunately not, for the time being.
- Reinstall Composer PHP extension (but it'll remove information about all scanned applications server-wide)
- Manually update Application table in %plesk_dir%/var/modules/composer/composer.sqlite3 with a new path (which is also not recommended)
Unfortunately not, for the time being.
I get that, but honestly, it’s just not cutting it.
I thought you had a large team of developers behind this. How is it possible that a feature that’s been out for months or even years still is half-baked?
Every solution you've mentioned so far seems more like a patch job than a real fix. Are you planning to actually address this properly, or is the price for plesk just going to keep climbing while the quality stays stuck in the same frustrating place?
Personally, I also find it disappointing that with almost every issue, you're basically forced to turn to the community and dig around for workarounds, just because the actual Plesk support team either never responds in a helpful way or just keeps stringing you along without offering a real solution...
I thought you had a large team of developers behind this. How is it possible that a feature that’s been out for months or even years still is half-baked?
Every solution you've mentioned so far seems more like a patch job than a real fix. Are you planning to actually address this properly, or is the price for plesk just going to keep climbing while the quality stays stuck in the same frustrating place?
Personally, I also find it disappointing that with almost every issue, you're basically forced to turn to the community and dig around for workarounds, just because the actual Plesk support team either never responds in a helpful way or just keeps stringing you along without offering a real solution...
@marcDE , thank you for the provided feedback. That particular case is assigned low priority - likely because there's a relatively simple workaround and it doesn't affect wide range of users (that's my personal guess). It is understandable the workaround is not convenient in all cases. I will consult with our team about this on Monday and I will try to provide more clarity.
