The WebSocket protocol is an extension of the HTTP protocol. However, the proxy module of Apache2 does not seem to know about it, and throws away crucial headers, converting the call to a standard HTTP call.
Is there a way to make Apache2 either (1) understand WebSocket or (2) simply blindly pass on whatever it gets?
I've got a shell script that performs some tasks using files from a Subversion repository. I would like the Subversion repository to keep up-to-date, but right now the script runs svn up every time which is annoying if I need to run the script several times in a row.
Since svn up changes the last modified timestamp of the .svn directory (even if there were no new commits), I figured that I could use that to make sure it only runs svn up once per day or so.
I tried finding a simple way of just checking whether the .svn directory is older than a day, but there were many seemingly overkill ways of doing it so I thought I'd ask here in case there's actually a very simple way to do it.
I want to create a Debian package that runs a few scripts in postinst. These scripts are only needed in postinst (they're just too unwieldy to include in postinst itself).
Is there a standard way to have them included and accessible in the installation process and then discarded, or should I simply put them in /usr/share/package-name/ and run them from there?
I decided to put the scripts in /usr/share/package-name/ and run them there, but I'm still interested in an answer to the question.