- Thanks to Snehal Maniar and Sebastian Radloff, the mb.cmd file in the self-contained Windows zip is now portable across any directory you run it from.
- I've made attempts at reducing the 'path too long' errors unzipping the Windows zip file in Windows Explorer, but it's a pretty fundamental constraint of Explorer. I provide suggestions on the install page.
- Prevent spurious build failures from pull requests (trying to deploy without the correct environment variables)
- Some work on making the build more robust against OS-level networking differences, with the help of Avalon McRae and Carson Ramsden
- Jason Reid fixed a bug preventing AJAX calls to mb from IE
- Fixed the ATOM feed
Many thanks to the following kind folk for help with this release:
- Snehal Maniar
- Sebastian Radloff
- Avalon McRae
- Carson Ramsden
- Jason Reid
npm install -g firstname.lastname@example.org --production
|Option||node.js required?||sudo required?||links||Description|
|Self-contained archives||No||No||Simply unpack and run
|source tarball||Yes||No||source tarball if you roll that way.|
Windows path limitations
*mountebank wishes very much for your Windows experience to be hassle-free, but he is simply not qualified to address a particular constraint of Windows Explorer. For legacy reasons, some Windows applications, including most notably Windows Explorer, have a maximum number of characters allowed in a path of 260 characters. As mountebank writes these words, the longest path he includes in the zip files is around 175 characters. The zip file name, which is likely to represent itself as two nested directories if you use the defaults to unzip it, will be around 25 characters. That gives you very little wiggle room. If you unzip the file in your users directory, you may very likely get an error because of this constraint.
The following solutions will all work:
- Unzip to the root of your C: drive (or a similar small path)
- Use 7zip to unzip the file instead of Windows Explorer
npmto install mountebank instead of the zip file