Open Landelor opened 8 years ago
After some troubleshooting downloaded an earlier tree. Found out that Tree:b34ca26d0a works fine. Hope that helps.
Nice troubleshooting! Looks like there are a few more things which need updating in the documentation. I think the one thing you're missing is a file named .env
containing:
WEBSITE_SERVER_PORT=8080
I've updated the documentation. If you don't mind, could you look it over to see if there any steps you needed to add which aren't reflected there?
That looks good. Works now.
However still getting an error when using $ grunt clean build start
. Have to run the script manually ./scripts/start
for it to go.
Also the URL in the doc is still showing port 8000.
I'll do this from scratch again on a different box and let you know if there are any steps missing.
Cheers,
Flows nicely doing it from scratch.
Only issue left is the error when running $ grunt clean build start
Running "script:start" task
Fatal error: spawn .\scripts\start ENOENT
Huh. Those backslashes make it look like you're running that on Windows. Does dir .\scripts\start
show up as a proper file?
Running it on Git for Windows yes. I can see the start file in the scripts directory.
I'm baffled, then. This is the exact line where the problem is coming from. All I can suggest is that you try messing around with various ways of getting it to call that script. Unfortunately, I don't have access to a Windows machine to test things out on. 😢
From what I can find it seems to be a problem with grunt spawn not working well/at all on windows. There are some variants for Windows "win-spawn", "cross-spawn". Unfortunately my coding knowledge is rudimentary and I have no idea how I would implement one of those in this case.
Thanks for figuring that out! I might upgrade the project at some point, but, for now, I'll update the docs to tell people to just run the script manually.
Sounds good.
Apologies for the necro, but I think it should be mentioned that you need to run $ grunt clean build start
once in order for ./scripts/start
to work. Adding that one line to the wiki instructions ought to save potential contributors a headache.
@GreenGhost21 Jesus dude you just saved my life, I was following the documentation to the letter and started over a bunch before finding this.
@andrewminer Definitely update the documentation saying that $ grunt clean build start
has to be run once before doing ./scripts/start
Done. Thanks for troubleshooting, guys!
In going through the setup, I encountered two serious issues. For reference, I'm using the Linux Subsystem for Windows.
1) Version pinning for crafting-guide-common is too lax. NPM installed a version old enough (5.6.0) to not work with the current master branch. I had to manually upgrade to the latest version.
2) The data directory isn't linked over correctly in any of the setup steps. I had to manually symlink crafting-guide-data/data
to crafting-guide/build/static/data
before I could get it working. I notice you mention rsync in the documentation but never include a setup step for it.
As an addition to this, you should maybe mention that running ./scripts/start
is only necessary if grunt start
doesn't work.
EDIT: it's possible that the windows command mklink
may also work instead of rsync.
Wasn't sure if you read closed issues. This is the current state of things.
As a side note. I had to manually install Ruby, Sass and nodemon for the Windows environment.
Regards.