Thatoo
Thatoo
now `bench build --app erpnext` doesn't even launch the command `node esbuild --production --apps erpnext --run-build-command` but indeed, if I launch manually `node /var/www/dokos/dokos-bench-folder/apps/frappe/esbuild/esbuild.js --production --apps erpnext --run-build-command` it works!
Well instead of `bench get-app`, I download from git the app, put it in `bench/apps/erpnext` and then I do `python -m pip install --upgrade -e bench/apps/erpnext` I thought that would...
It works! Thank you so much @cogk . I'll manage to make it working in fine, with all the help of this community :smile: Next step, understanding how `bench init`is...
Now that I'm able to install erpnext with ``` sudo -u dokos /var/www/dokos/dokos-bench-folder/env/bin/activate sudo -u dokos /var/www/dokos/dokos-bench-folder/env/bin/python -m pip install --upgrade -e /var/www/dokos/dokos-bench-folder/apps/erpnext chown -R $app:www-data "/var/www/dokos/dokos-bench-folder/apps/erpnext" sudo -u dokos...
last logs are : ``` 2024-05-14 10:35:18,182: DEBUG - + sudo -u dokos env /opt/node_n/n/versions/node/18/bin/yarn install --check-files 2024-05-14 10:35:18,522: DEBUG - yarn install v1.22.22 2024-05-14 10:35:18,714: DEBUG - [1/5] Validating...
> @Thatoo The `build` command is provided by the `frappe` app, and is not a built-in in `bench`. However, ` sudo -u dokos env /var/www/dokos/bin/bench build --app erpnext` does work....
No. If I first install `frappe` thanks to `bench init` then, all that works perfectly fine : ``` sudo -u dokos /var/www/dokos/dokos-bench-folder/env/bin/activate sudo -u dokos /var/www/dokos/dokos-bench-folder/env/bin/python -m pip install --upgrade...
Well actually, I get this warning right from `sudo -u dokos /var/www/dokos/bin/bench setup env`
To solve my issue, I need to add ``` sudo -u dokos /var/www/dokos/bin/bench setup procfile sudo -u dokos /var/www/dokos/bin/bench setup socketio ``` before ``` sudo -u dokos /var/www/dokos/dokos-bench-folder/env/bin/activate sudo -u...