svn: warning: W155010: '/cygdrive ...

>PROBLEM

svn fails throwing the folling message:
  svn: warning: W155010: '/cygdrive ...

>SOLUTION

The cygwin's svn command is called instead a windows command, like Tortoise, etc.
Correct the Path envvar.
Set the windows' cmd path (i.e. Tortoise) before cygwin's path.

>ENV

windows7

Arquillian exceptions: Caused by: java.lang.IllegalArgumentException: DeployableContainer must be specified

>PROBLEM

  Caused by: java.lang.IllegalArgumentException: DeployableContainer must be specified
 
  or
 
  org.jboss.arquillian.container.test.impl.client.deployment.ValidationException: DeploymentScenario contains a target (_DEFAULT_) not matching any defined Container in the registry.
  Please include at least 1 Deployable Container on your Classpath.
  add a container adapter to the classpath.


>SOLUTION

Go to http://arquillian.org/guides/getting_started/ at "Add a Container Adapter" topic.

"couldn't make stderr distinct from stdout" when running Cygwin commands

>SOLUTION

Check you envvars.

Originally the Path had Git's bin before cygwin64.
  Path=..;C:\Git\bin;C:\cygwin64\bin

Switching places:
  Path=..;C:\cygwin64\bin;C:\Git\bin
in order to read cygwin's library first.

In such case, you may get issues with git. So test it after your have changed the Path.

If it happens to get problems with Git, it's necessary to point git's executables manually or using a script to set the local envvar during git's execution context.

Another solution could be adopting one or another.

>ENV

Windows 7-10

apache2 vs. php5 (lump) - install failure on debian 7 (wheezy)

If you get one of the messages below, probably you need to upgrade your installation.
Check the commands at the end.

-------------------------------------------------------------------------------------------------------

>failure messages

apache2: Syntax error on line 140 of /etc/apache2/apache2.conf: 

Syntax error on line 1 of /etc/apache2/mods-enabled/php5.load: Cannot load /usr/lib/apache2/modules/libphp5.so into server: /usr/lib/x86_64-linux-gnu/libk5crypto.so.3: symbol krb5int_buf_len, version krb5support_0_MIT not defined in file libkrb5support.so.0 with link time reference

--- --

[FAIL] Starting web server: apache2 failed!

[warn] The apache2 configtest failed. ... (warning).

Output of config test was:

apache2: Syntax error on line 140 of /etc/apache2/apache2.conf: Could not open configuration file /etc/apache2/mods-enabled/php5.load: No such file or directory

-- --

Action 'configtest' failed.

The Apache error log may have more information.

-------------------------------------------------------------------------------------------------------
>commands

If you have MySQL already installed, you just need to install apache, php and phpmydmin.
If not, install MySQL first.

To install apache and php5, run the following commands as root (su or sudo).

apt-get ugrade
apt-get update
apt-get install apache2
apt-get install php5
apt-get install libapache-mod-php5

maven version conflict

>PROBLEM
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.RequireMavenVersion failed with message:
Detected Maven Version: 3.0.4 is not in the allowed range 3.1.1.


>SOLUTION
Using an old version incompatible with the version required.
  M2_HOME=D:\portables_d\apache-maven-3.0.4

Switch the M2_HOME envvar to the new maven version:
  M2_HOME=D:\portables_d\apache-maven-3.1.1

Apache or Node? Which one is best?

My Thoughts and Conclusions About Two Different Ways of Doing Something Concerning Server's Approaches Using Node.js vs. Apache Comparison Example

When the major problem is the number of persons to travel, matter less if the car has front-wheel drive or rear-wheel drive.
Number of seats care most.

Being straight, more requests demand more resources and increase possible concurrencies issues.
It matters less how the process requests are handled, but how the project's resources in general may scale with high availability.

Putting aside that, if you have light CPU processing per request, Node.js will be lighter approach, otherwise, if it is not possible to guarantee that, threads will fit better, so Apache is a better choice.

See more at:

http://www.quora.com/What-are-the-pros-and-cons-of-Node-js-versus-Apache-web-server

http://voidcanvas.com/describing-node-js/

http://www.toptal.com/nodejs/why-the-hell-would-i-use-node-js

https://thomashunter.name/blog/php-vs-nodejs/