Build scripts for windows #31
One more problem is paths in public/assets/tasks/icon.js, i saw you used path.resolve('frontend/icons') but i got the syntax is incorrect when build, and i changed it to path.resolve('frontend\icons') but still got same problem.
windows 10 mamp 4 pro php 7.1.7
then if I remove the copy part
at the moment the installation experience is not very good
Regarding problems in the migrations files, I assume your database does not support JSON columns.
Navigation configuration goes into
Tutorial videos are definitely on our short term roadmap, stay tuned!
Thank you so much for your enthusiasm in trying out Twill.
Thanks for the answer, I have installed now
Sorry to hear you're still encountering these issues. Sadly is hard to test across all the environments and configurations.
I'm using Windows 10 but not natively, instead using Windows Subsystem for Linux (WSL) which can be enabled on Windows 10 Pro.
We have discussed with @ifox to simplify these commands by using
A quick workaround will be to edit
"twill-build": "npm run twill-copy-blocks && cd vendor/area17/twill && npm ci && npm run prod && xcopy /E /Y public/*.* ../../../public",
I'm going to setup a Windows native installation next week and will be able to introduce changes to improve this.
Hope the quick hack works on your end and stay tuned for updates.
Thank you for your patience and interest in Twill.
Hello @khyoz, sadly, no easy solution. Did you try introduce the change I made?
The issue is caused by the nature of the commands being executed, as mentioned here (the last part of the comment) the embedded commands fail.
The only workaround we are thinking of is to replace that one-liners with an artisan task, but need to regroup internally on the fix.
Will keep you informed on this.
Hi guys im on windows and i faced the same problems, but i got most of it working except the hot reload which i still didnt had enough time to debug/fix on my own... but the main issue on windows is that when u run
so u need to instruct it to use bash.exe instead of cmd.exe you can do this by
also the bash on windows is very weird sometimes.... this command specified on the documentation
will work on mac, linux... but wont have the same behavior on bash on windows, the folder will be copied over blocks so u ended having /blocks/blocks, the following fixes it and also doesnt change the behavior on the other OS
-cp -R resources/assets/js/blocks/ +cp -R resources/assets/js/blocks/*
so perhaps updating the docs to /* by default would be a good idea.
also https://www.npmjs.com/package/windows-build-tools is a must on windows regardless of which project u are working on... things always tend to break without these tools...
I also had problem with bash complaining about npm not being found, so I will just add this here as using bash seems to be the only solution in this case. Also it might be useful to know that 'bash' in this case is windows bash (as part of windows linux subsystem) and not Git Bash. I found the easiest solution to missing npm is to install node and npm again in bash: