Skip to content

Instantly share code, notes, and snippets.

View thehydroimpulse's full-sized avatar

Daniel Fagnan thehydroimpulse

View GitHub Profile
#!/bin/bash
# We need to do a few things here.
# 1) Build the repo
set -e;
APP="$2"; IMAGE="app/$APP"; NAME=$1
META="$HOME/meta"
APPMETA="$META/$NAME"
#!/bin/bash
FILE='../repos.txt'
isDir=false
yes=n
do_get_new () {
running=true
while $running; do
packages.forEach(function(package) {
// Build the assets for each package and concatenate each of them (css and js)
// We'll have the following in the .tower/ folder:
//
// + raw/
// -> This folder will contain the raw concatenated files of each package.
// + packages/
// -> This folder will contain the concatenated assets for each package.
// + final/
// -> The final, concatenated assets of all the packages. This will result in a `app.js` and `app.css`. These files
// Define the autoloading directories:
require('tower').create({
directories: 'default'
});
function History(options) {
this.timestamp = options.timestamp || new Date();
this.time = options.time || new Date().getTime();
}
function Server(options) {
this.port = options.port || null;
this.alias = options.alias || null;
this.queue = [];
this.history = options.history || [];
class Model
fields: []
constructor: ->
@fields = []
@outgoing = []
@incoming = []
@field: (name) ->
console.log @
Tower.watch(path.join(Tower.path, 'packages', '**', '*'))
.ignore(/node_modules/)
.filter(/Test\.js$/)
.latency(0.2)
.forcePolling(false)
.on('changed', function(files) {
console.log(files);
})
.on('removed', function(files) {})
.on('added', function(files) {
@thehydroimpulse
thehydroimpulse / index.html
Last active December 12, 2015 09:09
Splitting ember.js compilation on both the server (Node.js) and client-side. This would solve search engine crawling, speed, and some others. I also gota simple server side implementation. Had to port ember-view to node.js. things are still somewhat unstable. Some issues on the server : * Lack of Router * This means Controllers and Views are not…
<!DOCTYPE html>
<html>
<head>
<meta charset=utf-8 />
<title>Fast Boot</title>
</head>
<body>
<!-- Main application template -->
<script type="text/x-handlebars" data-template-name="application">
Application Template - {{name}}
// client:
// Hybrid appoach:
define(function (require) {
var Tower = require('tower');
var App = require('app');
App.initialize();
define(function(require, module){
// Only use module to access it's ID, and other information, such as parent module.
// Require is completely synchronous - because everything ends up being one huge file
var Tower = require('tower');
var App = require('app');
// This module will return the result of initialize()
return App.initialize();
});