-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows support #416
Comments
I can confirm it doens't work on a linux VM on a Windows host due to the colons in the filenames. I see lots of protocol errors both in the installer and when I try and run the migrations after a composer install. I'd love to see some support for those of us with dev VMs on Windows hosts. |
Hi Ed Thank you for confirming this. Unfortunately, active development on Mothership has temporarily been haulted because the parent company doesn't exist anymore. There is a branch in Cog for Windows support, though #447 that works by using exclamation marks instead of colons by default. It may be a bit involved to get it working with this branch though Thanks, Thomas [https://avatars0.githubusercontent.com/u/5089510?v=3&s=400]#447 Windows support by kuiche · Pull Request #447 · mothership-ec/coghttps://github.com//pull/447 From: edhardie [email protected] I can confirm it doens't work on a linux VM on a Windows host due to the colons in the filenames. I see lots of protocol errors both in the installer and when I try and run the migrations after a composer install. I'd love to see some support for those of us with dev VMs on Windows hosts. You are receiving this because you authored the thread. |
Currently Cog/Mothership does not support Windows, and I believe this is even on a virtual machine. The reason is that Windows does not allow for colons in file/directory names.
When the assets are copied over to the public directory, they are put in directories that use colon separated namespaces (e.g.
Message:Mothership:CMS
). The same applies for view overrides (although the potential to mitigate this would come about once #401 is merged).I feel that our options are to either no longer use the colon separated namespaces, which would probably bring about a rather sizeable BC break, or to implement some sort of fallback, such as hyphens, when generating on a windows server.
The text was updated successfully, but these errors were encountered: