Pear for 1.4, mage for 1.5. File downloaded into /downloader/.cache/community/
./pear download magento-community/Shipping_Agent
./mage download community Shipping_Agent
# Nginx config for Hudson CI behind a virtual host with SSL. | |
# Replace hudson.example.com with your domain name. | |
# Upstream Hudson server, e.g.: on port 3001 | |
upstream hudson { | |
server localhost:3001 | |
} | |
# Redirect all HTTP requests to HTTPS. | |
server { |
$ node yui.js | |
info: (yui): Modules missing: io, 1 | |
info: (yui): Fetching loader: /usr/local/lib/node/.npm/yui3-core/3.3.0/package/build/loader/loader-debug.js | |
info: (get): URL: /usr/local/lib/node/.npm/yui3-core/3.3.0/package/build/loader/loader-debug.js | |
info: (get): Loaded: /usr/local/lib/node/.npm/yui3-core/3.3.0/package/build/loader/loader-debug.js | |
info: (yui): Modules missing: oop,parallel,event-custom-base,nodejs-dom,event-base,dom,node-base,dom-style-ie,node-style,queue-promote,datatype-xml,io,io-nodejs, 13 | |
info: (yui): Using Loader | |
info: (loader): attempting to load oop, /usr/local/lib/node/.npm/yui3-core/3.3.0/package/build/ | |
info: (get): URL: /usr/local/lib/node/.npm/yui3-core/3.3.0/package/build/oop/oop-min.js | |
info: (get): Loaded: /usr/local/lib/node/.npm/yui3-core/3.3.0/package/build/oop/oop-min.js |
YUI().use("singleton-class", function (Y) { | |
var instance1 = new Y.SingletonClass(), | |
instance2 = new Y.SingletonClass(); | |
Y.log(instance1 === instance2); // true! | |
window.instance1 = instance1; | |
}); | |
YUI().use("singleton-class", function (Y) { |
// Run this somewhere with a command you want to pipe stuff through. | |
// | |
// On a machine that needs data processed, run this: | |
// curl --data-binary @/some/file http://server:port/ > output | |
var http = require('http'); | |
var spawn = require('child_process').spawn; | |
// 0 == node, 1 == [this script] | |
var PORT = parseInt(process.argv[2]); |
YUI.add('foo', function (Y) { | |
Y.foo = 'foo'; | |
}); |
It's helpful to understand how Composer works and how to best utilize the environment as you implement your PSR-0 Namespace. There are factors that you, where you, as a user of the environment, will not be able to change and you should be aware of those points. There are areas where your choices directly impact the folder path and the implementation of your namespace.
##1. Composer Name Parameter##
The first data relevant to the package install path is the name you provide to Composer.
###What is the purpose of the name parameter?###
'use strict' | |
/* | |
* Rewrite package.json to get dependencies from Git repository instead of npm. | |
* | |
* See also: https://medium.com/@azerbike/i-ve-just-liberated-my-modules-9045c06be67c | |
* and: http://blog.npmjs.org/post/141577284765/kik-left-pad-and-npm | |
* | |
* Usage: cd /path/to/your/package && node npm2git | |
* | |
* This script is warning because: |
<?php | |
namespace GoetasWebservices\Xsd\XsdToPhp\Php; | |
use GoetasWebservices\Xsd\XsdToPhp\Php\Structure\PHPClass; | |
use GoetasWebservices\Xsd\XsdToPhp\Php\Structure\PHPProperty; | |
use Zend\Code\Generator\ClassGenerator; | |
use Zend\Code\Generator\DocBlock\Tag\VarTag; | |
use Zend\Code\Generator\DocBlockGenerator; | |
use Zend\Code\Generator\MethodGenerator; |
git status -s | awk '{print $2}' | sed 's/\(.*\)/rsync -cav \1 user@remote.server.com:~\/\1/' | sh |