-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Local engine doesn't get copied or used #603
Comments
Turns out the sync fails even without a space and with the proper path.
|
Trailing whitespace should always be removed, everywhere. I mean, we shouldn't have to strip it ourselves, but still. Trailing whitespace is anathema. |
Yes, turns out it is has nothing to do with this issue though. I falsely assumed my first run (with no trailing whitespace) worked. Since the hooks handle and parse the boxfile my guess is nanobox isn't mounting in the engine to be rsynced from the specified location. It is planned to incorporate the boxfile validation in nanobox itself, so as to save time before finding out a bad node was entered, but there is much in the plans (so no solid ETA). |
Turns out when we renamed boxfile nodes, we never updated nanobox to match. This addresses that and properly mounts in a specified local engine as well as cleans up the mount should a user stop using the local engine. Resolves #603
Example boxfile.yml: (
·
represent space)The text was updated successfully, but these errors were encountered: