Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Frequently Answered Questions

Alexander Vassbotn Røyne-Helgesen edited this page · 15 revisions

This is a wiki page dedicated to frequently answered questions.

Table of Contents

  1. How do I install patsy?
  2. When will I be able to use in-development feature 'X'?
  3. Does patsy work on Windows?
  4. How can I contribute?
  5. Error installing patsy with npm: Cannot run in wd
  6. ECONNRESET, Socket hang up
  7. EADDRINUSE, Address already in use
  8. Warning: Grunt: Warning: Native modules not compiled...
  9. Why does Recess exclude my css file?
  10. What the heck is this scripture thingy?

How do I install patsy?

For general installation instructions, please read the Installation-section. For a more in-dept guide on how to install patsy, check out the Installing-patsy page.

When will I be able to use in-development feature 'X'?

Installing both published and unpublished development versions of patsy is covered in the Installing patsy guide.

Does patsy work on Windows?

Patsy works great on Windows, MacOs and Linux! This because Node.js and npm both work fine on Windows. Usually the problematic part is Cygwin, because it bundles an outdated version of Node.js.

The best way to avoid this issue is to use the msysGit installer to install the git binary and the Node.js installer to install the node and npm binaries, and to use the built-in Windows command prompt or PowerShell instead of Cygwin.

Error installing patsy with npm: Cannot run in wd

Try to install it againg with sudo npm install patsy -g --unsafe-perm or open your CLI as an administrator if you have similar errors in a Windows environment.

⬆ Go to the TOC

ECONNRESET, Socket hang up

Getting this?

>> EXCEPTION: { [Error: socket hang up] code: 'ECONNRESET' }

Downgrade to node 0.8.19 (0.8.20 introduces fix that throws this error), see: http://clock.co.uk/tech-blogs/preventing-http-raise-hangup-error-on-destroyed-socket-write-from-crashing-your-nodejs-server

⬆ Go to the TOC

EADDRINUSE, Address already in use

If you get this error when starting patsy, possible reasons could be:

  1. The patsy project configuration file is not configured properly with the ports for proxy, fileserver and project environment details
  2. Something else on your system is hogging your ports.

Try first to check if you have a misconfiguration in your patsy project config file. If this does not solve things, or that you are determined that you want to use your ports you have configured and you want to release your hogged ports, following guides will help you with that.

Find used ports in Windows

You can either check with:

C:\User>netstat -an

This option does not specify the program that's hogging the port.

Or check with TCPView. We recommend the usage of TCPView to get more information and to see what program that's hogging your ports

TCPView v3.05

Download TCPView here: http://technet.microsoft.com/en-us/sysinternals/bb897437

TCPView is a Windows program that will show you detailed listings of all TCP and UDP endpoints on your system, including the local and remote addresses and state of TCP connections.

Find used ports in a Linux environment

$ sudo -i
$ netstat -tulpn

⬆ Go to the TOC

Warning: Grunt: Warning: Native modules not compiled...

If you get this error when running patsy, it's due to a dependency called websocket. This is a dependency of grunt-reload, a grunt plugin we use for LiveReloading.

We have an open issue with websocket to silence or give an option to silence these errors, since they have no effect on the usage of patsy.

Excerpt from websocket readme:

As of version 1.0.7, Native modules are now optional. If they fail to compile, WebSocket-Node will still work but will not verify that received UTF-8 data is valid, and xor masking/unmasking of payload data for security purposes will not be as efficient as it is performed in JavaScript instead of native code.

⬆ Go to the TOC

Why does Recess exclude my css file?

Well, WHY is something that cannot be answered, but this might solve it: remove all occurences of comment strings starting with /** and ending with **/, and replace with /* and */. That means: no silly comments please ;)

⬆ Go to the TOC

What the heck is this scripture thingy?

Oh, it's a silly silly thing we added to fun up the CLI interaction a bit. We found that general CLI interaction is rather, dull, so we juiced it up a little. The scripture roles are derived from Monty Pythons Quest for The Holy Grail. Well, if you failed to see the link between our project name (patsy) with that film.. Well, it's a silly silly thing really.

You will meet characters such as Patsy (well, doh?), King Arthur, God and some other charcters from the modules starring in this elkmövie with or without lamas , perhaps a fish-slapping dance and some other silly silly roles as: Grunt, Proxy, Server et al.

If you do not like it, then turn it off! In the patsy.json file, set options.scripture to false. But be aware that your development cycles will be as dull as a bankiers life..

⬆ Go to the TOC

Something went wrong with that request. Please try again.