TiagoSilvaPereira / vemto-issues

Repository to track Vemto Issues
30 stars 0 forks source link

[BUG] Composer is not found #1

Closed fhferreira closed 4 years ago

fhferreira commented 4 years ago

I've created one simple "project" and I receive that error about "composer" on "Generate" button.

[MacOS BigSur] Error: Command failed: composer /bin/sh: composer: command not found

image

fhferreira commented 4 years ago

Just to add more info: image

TiagoSilvaPereira commented 4 years ago

Hi @fhferreira please check if Composer is accessible calling it from the folder you created the project on your terminal

TiagoSilvaPereira commented 4 years ago

Hi @fhferreira I just added a way to configure the composer path on Vemto image

fhferreira commented 4 years ago

To update I should download the "DMG" again or you will provide an feature to automatically update?

fhferreira commented 4 years ago

@TiagoSilvaPereira I've downloaded the last version of Vemto but the problem persist.

image

fhferreira commented 4 years ago

the path is already the composer bin, not a directory. image

TiagoSilvaPereira commented 4 years ago

Hi @fhferreira please remove the /composer from the path and keep only /usr/local/bin/

Vemto updates automatically after you open it (please wait to the message after the download), then close and open it again

asharekh commented 3 years ago

hi,

i have done everything, still not working

this is the error: Starting code generation! Checking php Checking composer Command failed: /usr/local/bin/composer --version /bin/sh: /usr/local/bin/composer: is a directory Command failed: /usr/local/bin/composer --version /bin/sh: /usr/local/bin/composer: is a directory Sorry, Vemto requires composer installed in your system. Please check if composer is globally available on your PATH environment variable, or add its path to the main settings on Vemto Home Page Error: Sorry, Vemto requires composer installed in your system. Please check if composer is globally available on your PATH environment variable, or add its path to the main settings on Vemto Home Page at p.checkDependency (app://./js/chunk-common.9e74499f.js:1:29099) at Xt.checkDependencies (app://./js/generator.f8b0147f.js:1:63134) at Xt.start (app://./js/generator.f8b0147f.js:1:62232) at EventEmitter. (app://./js/generator.f8b0147f.js:1:65369) at EventEmitter.emit (events.js:210:5) at Object.onMessage (electron/js2c/renderer_init.js:2243:16)

TiagoSilvaPereira commented 3 years ago

Hi @asharekh as you can see on your error message:

/bin/sh: /usr/local/bin/composer: is a directory

It means that your composer binary is not inside the /usr/local/bin directory. Maybe it is on /usr/local/bin/composer?

You need to set the exact folder that contains de composer binary.

brianmcaudill commented 2 years ago

I am having an issue on Windows 10, the application is using composer with a single dash command and it should be a double dash. Example: composer --version (is correct) composer -version (incorrect) image

TiagoSilvaPereira commented 2 years ago

@brianmcaudill could you please show the problem happening on Vemto console?

brianmcaudill commented 2 years ago

image

brianmcaudill commented 2 years ago

I removed the path to composer and instead used the default and it is now working. However there is another issue. 'npm run dev' is failing image

brianmcaudill commented 2 years ago

Here is the npm log for that error 2022-05-19T13_01_18_114Z-debug.log

TiagoSilvaPereira commented 2 years ago

I think the -version is only a visual problem (for some reason it is hiding the first "-" when showing it, but Vemto correctly adds the --version when executing the command)... to fix the npm problem, if you can, please try deleting all the generated code and generating it again. If you can't do it, plase run npm install manually from your command line

brianmcaudill commented 2 years ago

I started with only these files in the folder .env.example composer.json package.json

I ran the Generator and received these messages: image

image

brianmcaudill commented 2 years ago

Here is the composer.json file if you need that: { "name": "esg/packager", "description": "esg packager", "type": "project", "license": "na", "authors": [ { "name": "y" } ], "minimum-stability": "beta", "require": { "laravel/installer": "^4.2", "spatie/laravel-permission": "^5.5", "livewire/livewire": "^2.0", "laravel/ui": "^3.0", "illuminate/view": "^8.83", "illuminate/http": "^8.83", "phpunit/phpunit": "^9.5" }, "require-dev": {} }

TiagoSilvaPereira commented 2 years ago

Hi @brianmcaudill it is necessary to remove everything... I recommend to just delete the folder and start again

cnngraphics commented 2 years ago

I almost purchased this license, but after 10 hours of trying to configure the software's composer connection, I give up and would not recommend it to my team.

image

I have other software installed on my system like the very famous "LARAGON" it detects composer path and if not allows me to know during configuration if the path is wrong.

When multiple users are having the same problem with your tool, the author should wonder if they need to do something differently.

TiagoSilvaPereira commented 2 years ago

I almost purchased this license, but after 10 hours of trying to configure the software's composer connection, I give up and would not recommend it to my team.

image

I have other software installed on my system like the very famous "LARAGON" it detects composer path and if not allows me to know during configuration if the path is wrong.

When multiple users are having the same problem with your tool, the author should wonder if they need to do something differently.

Hi @cnngraphics, most composer issues happen when Vemto can't locate it on your system (generally just passing the composer path and restarting Vemto is sufficient)... Could you please share how did you try to configure it?

Also, you can always call me by e-mail to help if necessary (contact@vemto.app)