In place editing of a file with sed
Friday, January 27, 2012
When writing a file modification script I find it annoying (read: boring) to write the logic of saving the file under a different name, moving to override original and then cleaning up. This is what I recently had to do and instead decided to look around at what other options were available, one of which was sed.
The following command will replace the word testdomain with proddomain.
$ echo 'www.testdomain.com' > test.txt
$ cat test.txt
www.testdomain.com
$ sed -i '' s/testdomain/proddomain/ test.txt
$ cat test.txt
www.proddomain.com
The key to how this works is the -i '' argument of the sed command. -i specifies the file extension, by passing an empty string it uses the same file.
The following command will replace the word testdomain with proddomain.
$ echo 'www.testdomain.com' > test.txt
$ cat test.txt
www.testdomain.com
$ sed -i '' s/testdomain/proddomain/ test.txt
$ cat test.txt
www.proddomain.com
The key to how this works is the -i '' argument of the sed command. -i specifies the file extension, by passing an empty string it uses the same file.
Getting node-compress to work on Node 0.6
Thursday, January 26, 2012
I have a lot of respect for Node, but sometimes certain npm packages become out of sync with the latest version and break. Today, that npm package was node-compress.
While the package looked to build, when attempting to require the module it would error.
$ node
> var c = require('compress')
Error: Cannot find module 'compress'
After a quick look around on GitHub I found a fork with the fix https://github.com/elliotttf/node-compress/
In your package.json, simply reference the tarball, clean out the node_modules directory, install and everything should work again.
Package.json
, "compress":"https://github.com/elliotttf/node-compress/tarball/1edaa48bf33f7c836f1e275691e1d8645f0a71c3"
While the package looked to build, when attempting to require the module it would error.
$ node
> var c = require('compress')
Error: Cannot find module 'compress'
After a quick look around on GitHub I found a fork with the fix https://github.com/elliotttf/node-compress/
In your package.json, simply reference the tarball, clean out the node_modules directory, install and everything should work again.
Package.json
, "compress":"https://github.com/elliotttf/node-compress/tarball/1edaa48bf33f7c836f1e275691e1d8645f0a71c3"
Labels: nodejs
Video of How To Deploy a .NET App with Mono on Heroku
Wow. Chris Kemp (Advance technical solutions team at Salesforce.com) has create a great short video based on my blog post about How To Deploy a .NET App with Mono on Heroku. A huge thank you!
Link: http://www.youtube.com/watch?v=LkdiTzgqqsk&hd;=1
Link: http://www.youtube.com/watch?v=LkdiTzgqqsk&hd;=1
Help us by answering a questionnaire on Google Analytics
Wednesday, January 25, 2012
To help with development of Mayday we are asking people to fill out a questionnaire about how they use Google Analytics. If you use Google Analytics and have a moment to fill out the questionnaire then we would be most grateful.
Thank you.
Labels: Google Analytics, maydayhq
A JavaScript equivalent to Ruby's respond_to?
Tuesday, January 24, 2012
While working on the new version of Mayday, I wanted to show a message if no data was returned from Google Analytics. To add to the complexity, I wanted to be able to override the default message on a per page basis.
I'm already using the ICanHazJS client-side tempting engine which has a method for each template block on a page. However, if the page doesn't have the block then the method won't exist and an error will be thrown.
What I needed was functionality similar to Ruby's respond_to. With this method I can ask the object if it will respond to the method call. For example:
Object.respond_to? 'test' #=> false
Object.respond_to? 'to_s' #=> true
Luckily this is just as easy to do in JavaScript using 'in'
> 'test' in Object
false
> 'toString' in Object
true
This allowed me to write the following:
var e = $('#data')
if('nodata' in ich)
e.append(ich.nodata());
else
e.append('No Data Found');
If a nodata ICanHaz template block appears on the page then it will be rendered, otherwise it will fall back to the default. Problem solved.
Update:
Problem almost solved. As pointed out on Twitter by @nmosafi and @theprogrammer, just using 'in' along is not enough. For example:
> Object.test = "test"
"test"
> 'test' in Object
true
> Object.test()
TypeError: Property 'test' of object function Object() { [native code] } is not a function
What you need to do is ensure that the property is also a function. Something I had assumed previously.
> 'test' in Object && typeof(Object.test) == "function"
false
> 'toString' in Object && typeof(Object.toString) == "function"
true
Labels: ICanHazJS, Javascript, jQuery
Remove X-Powered-By for Express and NodeJS
Monday, January 23, 2012
When responding to a web request it's common for servers to tell the client various bits of information. The one they enjoy most is some promotion around the name and version "powering" the site. Sadly, hackers also love this as it gives them more information for an attack vector.
By default, ExpressJS with NodeJS will return a X-Powered-By header.
$ curl -I 0.0.0.0:3000/
HTTP/1.1 302 Moved Temporarily
X-Powered-By: Express
I wasn't overly impressed by this but it's easy to remove. In your application configuration, at the top, add a new middleware function which removes the header.
app.configure(function(){
app.use(function (req, res, next) {
res.removeHeader("X-Powered-By");
next();
});
app.set('views', __dirname + '/views');
app.set('view engine', 'jade');
app.use(express.bodyParser());
app.use(express.methodOverride());
app.use(express.cookieParser());
app.use(express.static(__dirname + '/static'));
});
Simple.
By default, ExpressJS with NodeJS will return a X-Powered-By header.
$ curl -I 0.0.0.0:3000/
HTTP/1.1 302 Moved Temporarily
X-Powered-By: Express
I wasn't overly impressed by this but it's easy to remove. In your application configuration, at the top, add a new middleware function which removes the header.
app.configure(function(){
app.use(function (req, res, next) {
res.removeHeader("X-Powered-By");
next();
});
app.set('views', __dirname + '/views');
app.set('view engine', 'jade');
app.use(express.bodyParser());
app.use(express.methodOverride());
app.use(express.cookieParser());
app.use(express.static(__dirname + '/static'));
});
Simple.
Finding out where that console.log output is coming from
Saturday, January 21, 2012
While trying to solve a problem, we have all sometimes done a little console.log outputting to help us gain additional understanding. While it's far from the most effect way of debugging, it's more annoying when those statements appear in your production logs. That was my scenario today.
Thankfully, with a simple grep command I was able to identified all of my "debugging" statements and the lines they occurred on.
$ grep -nr console * | grep -v "node_modules/*" | grep -v "static/"
endpoints/browser_stats.js:35: if(error) { console.log(error); }
endpoints/browser_stats.js:51: if(error) { console.log(error); }
endpoints/browser_stats.js:67: if(error) { console.log(error); }
endpoints/events.js:16: console.log(eventsUrl);
endpoints/events.js:17: console.log(hitsUrl);
endpoints/events.js:20: if(error) { console.log(error); }
endpoints/events.js:27: if(error) { console.log(error); }
passport.js:23: console.log("Auth");
In this case, I filtered out any matches from node_modules and static javascript files. Keep in mind that in some cases it's a node module causing the output.
A simple command to help keep your production logs clean and readable.
Thankfully, with a simple grep command I was able to identified all of my "debugging" statements and the lines they occurred on.
$ grep -nr console * | grep -v "node_modules/*" | grep -v "static/"
endpoints/browser_stats.js:35: if(error) { console.log(error); }
endpoints/browser_stats.js:51: if(error) { console.log(error); }
endpoints/browser_stats.js:67: if(error) { console.log(error); }
endpoints/events.js:16: console.log(eventsUrl);
endpoints/events.js:17: console.log(hitsUrl);
endpoints/events.js:20: if(error) { console.log(error); }
endpoints/events.js:27: if(error) { console.log(error); }
passport.js:23: console.log("Auth");
In this case, I filtered out any matches from node_modules and static javascript files. Keep in mind that in some cases it's a node module causing the output.
A simple command to help keep your production logs clean and readable.
Javascript WTF: The Date object
Friday, January 20, 2012
Almost every time I have to deal with the Date object in Javascript I always hit the same WTF.
The documentation is clear but the API has some strange aspects that personally I don't think reflect the real world and how we naturally handle dates.
For example:
getDay() returns the day of the week (0-6) leaving getDate() to return 1-31. Personally, I would have imagined getDate() to return DMY with getDay() returning 1-31.
getMonth() returns 0-11. Classic computer science with starting the count at 0 while the Gregorian calendar is 1-12. This is also inconsistent with getDate() which starts at 1.
getYear() returns the year (usually 2-3 digits). For example, 2012 is obviously 112. You need to use getFullYear() to return 2012. The logic about how the method came to 112 is found at https://developer.mozilla.org/en/JavaScript/Reference/Global_Objects/Date/getYear
JavaScript 1.0 - we love you and you have left an impact in many ways.
Labels: Javascript
Setting a cookie in Javascript shouldn't be THAT difficult
Thursday, January 19, 2012
With Javascript becoming increasingly popular, I'm still shocked at how bad the online documentation and examples are. Let's take the search phase "setting a cookie in javascript", a fairly common problem which I always forget the correct syntax for.
The first four results are as follows:
http://www.w3schools.com/js/js_cookies.asp
http://www.quirksmode.org/js/cookies.html
http://techpatterns.com/downloads/javascript_cookies.php
http://www.javascripter.net/faq/settinga.htm
Sorry to the original authors, but each one of them IS AWFUL!
Let's take W3Schools as an example. It defines a variable called ARRCookies
The best link which describes handling cookies, and generally any Javascript documentation, can be found on the Mozilla Developer Network (MDN).
https://developer.mozilla.org/en/DOM/document.cookie
While I'm not an SEO expert, this looks to be light on SEO (Search Engine Optimisation) related to phases people search for. As a result the link was found in the lonely spot on page 3 which is should be number 1.
Wouldn't it be great if MDN had SEO focused content to support the excellent reference material it already has available? The PromoteJS movement has made a start but I think it needs a kick-start.
Who's with me?
UPDATE (20/1/12):
In a moment of great timing, the Mozilla WebDev team started a AMA (Ask Me Anything) thread on Reddit. I pointed out the above comments and had some great responses from the team.
It turns out that MDN is a wiki so it's in the community (and my hands) to make a difference.
You can read the comments here:
http://www.reddit.com/r/IAmA/comments/oonrg/iama_member_of_the_mozilla_webdev_team_ama/c3iup1b
The first four results are as follows:
http://www.w3schools.com/js/js_cookies.asp
http://www.quirksmode.org/js/cookies.html
http://techpatterns.com/downloads/javascript_cookies.php
http://www.javascripter.net/faq/settinga.htm
Sorry to the original authors, but each one of them IS AWFUL!
Let's take W3Schools as an example. It defines a variable called ARRCookies
The best link which describes handling cookies, and generally any Javascript documentation, can be found on the Mozilla Developer Network (MDN).
https://developer.mozilla.org/en/DOM/document.cookie
While I'm not an SEO expert, this looks to be light on SEO (Search Engine Optimisation) related to phases people search for. As a result the link was found in the lonely spot on page 3 which is should be number 1.
Wouldn't it be great if MDN had SEO focused content to support the excellent reference material it already has available? The PromoteJS movement has made a start but I think it needs a kick-start.
Who's with me?
UPDATE (20/1/12):
In a moment of great timing, the Mozilla WebDev team started a AMA (Ask Me Anything) thread on Reddit. I pointed out the above comments and had some great responses from the team.
It turns out that MDN is a wiki so it's in the community (and my hands) to make a difference.
You can read the comments here:
http://www.reddit.com/r/IAmA/comments/oonrg/iama_member_of_the_mozilla_webdev_team_ama/c3iup1b
Labels: Javascript, MDN, PromoteJS
How to deploy Mono projects with Heroku
Wednesday, January 11, 2012
Last week I mentioned how I had successfully deployed Nancy / Mono (C# frameworks) onto Heroku. This post covers how you can deploy your own Mono projects onto Heroku.
As before, this approach is completely unsupported by Heroku and I'm not 100% sure if it's production ready. I would love to hear your experiences.
0) Prerequisites
There are a few requirements before deploying a project.
- The solution can compile using Mono on Linux (Ubuntu 10.04 - Lucid Lynx).
- The launch application must be a self-hosted executable.
- The self-hosted executable must stay alive and not exit. Example: https://github.com/BenHall/nancy-demo-hosting-self/blob/master/src/Program.cs#L20-23
1) Update heroku gem
Before you continue, make sure your running the latest heroku gem as you need the buildpack option which is only supported in later versions. Thanks Andy Pike for pointing this out.
2) Listening to Heroku requests
This is the only part which I'm not too happy with. In order for Mono to accept Heroku requests, you need to bind the listener to the full hostname provided by Heroku - for example http://deep-moon-1452.herokuapp.com.
The application also needs to listen on a particular port randomly defined by Heroku. This is provided via an environment variable.
Example:
https://github.com/BenHall/nancy-demo-hosting-self/blob/master/src/Program.cs#L12
Ironically this is the part which blocked me and after multiple combinations I was left with hard-coding the name as my last resort - see the commit https://github.com/BenHall/nancy-demo-hosting-self/commit/4d9e07bed92559a53b1463c37e837045d59c3a9a
3) How projects are built during deployment
Projects are built on Heroku during the git push process. To find a solution to build, the command "ls $BUILD_DIR/*.sln | head -1" is used. This will return the name of the first solution file found.
Once the name has been determined, xbuild is called with the output streamed back. If the build fails, the deployment is stopped.
4) How the application is launched - Procfile
Once the project has been built, the self-hosted executable needs to be executed via a Procfile.
An example can be found here:
https://github.com/BenHall/nancy-demo-hosting-self/blob/master/Procfile
The web property specifies the command used by Heroku. The first part is the path to mono which is defined in the buildpack and shouldn't be change. The second part is the relative path to your compiled executable.
In the example I also defined a local environment command allowing me to replicate the hosted environment locally via "foreman start local".
5) Creating the Heroku environment - Cedar and buildpacks
When creating your Heroku application to host your project, it's important to specify the stack as cedar along with the buildpack for Mono. The buildpack defines the steps required to download Mono from my S3 account, configure the environment and build your solution.
Remember to change the hostname your exe listens on otherwise you'll received a Bad Request (Invalid Host) response.
If you receive the error "!Name must start with a letter and can only contain lowercase letters, numbers, and dashes" then make sure your using the latest Heroku gem (currently 2.18.1).
6) Push
A simple push should now be all you need.
Important links:
Buildpack: https://github.com/BenHall/heroku-buildpack-mono
Example: https://github.com/BenHall/nancy-demo-hosting-self
tl;dr: The main steps are
0)
1)
2)
3)
4) Replace deep-moon-1452 in src/Program.cs to the application name created above
5)
6)
7) Tweet to say how amazing it is.
As before, this approach is completely unsupported by Heroku and I'm not 100% sure if it's production ready. I would love to hear your experiences.
0) Prerequisites
There are a few requirements before deploying a project.
- The solution can compile using Mono on Linux (Ubuntu 10.04 - Lucid Lynx).
- The launch application must be a self-hosted executable.
- The self-hosted executable must stay alive and not exit. Example: https://github.com/BenHall/nancy-demo-hosting-self/blob/master/src/Program.cs#L20-23
1) Update heroku gem
Before you continue, make sure your running the latest heroku gem as you need the buildpack option which is only supported in later versions. Thanks Andy Pike for pointing this out.
$ gem update heroku
2) Listening to Heroku requests
This is the only part which I'm not too happy with. In order for Mono to accept Heroku requests, you need to bind the listener to the full hostname provided by Heroku - for example http://deep-moon-1452.herokuapp.com.
The application also needs to listen on a particular port randomly defined by Heroku. This is provided via an environment variable.
Example:
https://github.com/BenHall/nancy-demo-hosting-self/blob/master/src/Program.cs#L12
Ironically this is the part which blocked me and after multiple combinations I was left with hard-coding the name as my last resort - see the commit https://github.com/BenHall/nancy-demo-hosting-self/commit/4d9e07bed92559a53b1463c37e837045d59c3a9a
3) How projects are built during deployment
Projects are built on Heroku during the git push process. To find a solution to build, the command "ls $BUILD_DIR/*.sln | head -1" is used. This will return the name of the first solution file found.
Once the name has been determined, xbuild is called with the output streamed back. If the build fails, the deployment is stopped.
4) How the application is launched - Procfile
Once the project has been built, the self-hosted executable needs to be executed via a Procfile.
An example can be found here:
https://github.com/BenHall/nancy-demo-hosting-self/blob/master/Procfile
The web property specifies the command used by Heroku. The first part is the path to mono which is defined in the buildpack and shouldn't be change. The second part is the relative path to your compiled executable.
In the example I also defined a local environment command allowing me to replicate the hosted environment locally via "foreman start local".
5) Creating the Heroku environment - Cedar and buildpacks
When creating your Heroku application to host your project, it's important to specify the stack as cedar along with the buildpack for Mono. The buildpack defines the steps required to download Mono from my S3 account, configure the environment and build your solution.
$ heroku create --stack cedar --buildpack http://github.com/BenHall/heroku-buildpack-mono Remember to change the hostname your exe listens on otherwise you'll received a Bad Request (Invalid Host) response.
If you receive the error "!Name must start with a letter and can only contain lowercase letters, numbers, and dashes" then make sure your using the latest Heroku gem (currently 2.18.1).
6) Push
A simple push should now be all you need.
$ git push heroku masterImportant links:
Buildpack: https://github.com/BenHall/heroku-buildpack-mono
Example: https://github.com/BenHall/nancy-demo-hosting-self
tl;dr: The main steps are
0)
$ gem update heroku 1)
$ git clone https://github.com/BenHall/nancy-demo-hosting-self2)
$ cd nancy-demo-hosting-self3)
$ heroku create --stack cedar --buildpack http://github.com/BenHall/heroku-buildpack-mono4) Replace deep-moon-1452 in src/Program.cs to the application name created above
5)
$ git commit -am "Changed application name" 6)
$ git push heroku master7) Tweet to say how amazing it is.
Experiment: Deploying C# / Mono on Heroku
Tuesday, January 03, 2012
Over the past couple of days I've been trying to get Mono running on top of Heroku.
I'm pleased to report that I have successfully deployed Nancy (a C# web framework) on top of Heroku.
It's far from a production ready solution and is completely unsupported by Heroku but it's an interesting experiment. More technical details in future posts but here's some proof.
Server response headers:
$ curl -i http://deep-moon-1452.herokuapp.com/
HTTP/1.1 200 OK
Content-Type: text/html
Date: Tue, 03 Jan 2012 16:33:02 GMT
Nancy-Version: 0.9.0.0
Server: Mono-HTTPAPI/1.0
Screenshot:
This is the output when you push your git repository to Heroku. The source code is built on Heroku.
$ git push heroku master
Counting objects: 9, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (4/4), done.
Writing objects: 100% (5/5), 514 bytes, done.
Total 5 (delta 3), reused 0 (delta 0)
-----> Heroku receiving push
-----> Fetching custom buildpack... done
-----> Mono app detected
-----> Fetching Mono binaries
tar: Ignoring unknown extended header keyword `SCHILY.dev'
tar: Ignoring unknown extended header keyword `SCHILY.ino'
tar: Ignoring unknown extended header keyword `SCHILY.nlink'
tar: Ignoring unknown extended header keyword `SCHILY.dev'
tar: Ignoring unknown extended header keyword `SCHILY.ino'
tar: Ignoring unknown extended header keyword `SCHILY.nlink'
tar: Ignoring unknown extended header keyword `SCHILY.dev'
tar: Ignoring unknown extended header keyword `SCHILY.ino'
tar: Ignoring unknown extended header keyword `SCHILY.nlink'
tar: Ignoring unknown extended header keyword `SCHILY.dev'
tar: Ignoring unknown extended header keyword `SCHILY.ino'
tar: Ignoring unknown extended header keyword `SCHILY.nlink'
tar: Ignoring unknown extended header keyword `SCHILY.dev'
tar: Ignoring unknown extended header keyword `SCHILY.ino'
tar: Ignoring unknown extended header keyword `SCHILY.nlink'
tar: Ignoring unknown extended header keyword `SCHILY.dev'
tar: Ignoring unknown extended header keyword `SCHILY.ino'
tar: Ignoring unknown extended header keyword `SCHILY.nlink'
tar: Ignoring unknown extended header keyword `SCHILY.dev'
tar: Ignoring unknown extended header keyword `SCHILY.ino'
tar: Ignoring unknown extended header keyword `SCHILY.nlink'
tar: Ignoring unknown extended header keyword `SCHILY.dev'
tar: Ignoring unknown extended header keyword `SCHILY.ino'
tar: Ignoring unknown extended header keyword `SCHILY.nlink'
tar: Ignoring unknown extended header keyword `SCHILY.dev'
tar: Ignoring unknown extended header keyword `SCHILY.ino'
tar: Ignoring unknown extended header keyword `SCHILY.nlink'
-----> Vendoring mono 2.10.8
-----> building via /tmp/mono-GssQ/bin/mono /tmp/mono-GssQ/lib/mono/4.0/xbuild.exe /tmp/build_19y6xv4nr43ic/Nancy.Demo.Hosting.Self.sln
XBuild Engine Version 2.10.8.0
Mono, Version 2.10.8.0
Copyright (C) Marek Sieradzki 2005-2008, Novell 2008-2011.
Build started 01/03/2012 16:28:24.
__________________________________________________
Project "/tmp/build_19y6xv4nr43ic/Nancy.Demo.Hosting.Self.sln" (default target(s)):
Target ValidateSolutionConfiguration:
Building solution configuration "Debug|Mixed Platforms".
Target Build:
Project "/tmp/build_19y6xv4nr43ic/src/Nancy.Demo.Hosting.Self.csproj" (default target(s)):
Target PrepareForBuild:
Configuration: Debug Platform: x86
Created directory "bin/"
Created directory "obj/x86/Debug/"
Target CopyFilesMarkedCopyLocal:
Copying file from '/tmp/build_19y6xv4nr43ic/lib/Nancy.dll' to '/tmp/build_19y6xv4nr43ic/src/bin/Nancy.dll'
Copying file from '/tmp/build_19y6xv4nr43ic/lib/Nancy.Hosting.Self.dll' to '/tmp/build_19y6xv4nr43ic/src/bin/Nancy.Hosting.Self.dll'
Target GenerateSatelliteAssemblies:
No input files were specified for target GenerateSatelliteAssemblies, skipping.
Target CoreCompile:
Tool /tmp/mono-GssQ/bin/dmcs execution started with arguments: /noconfig /debug:full /debug+ /optimize- /out:obj/x86/Debug/Nancy.Demo.Hosting.Self.exe Program.cs TestModule.cs /target:exe /define:"DEBUG;TRACE" /main:Nancy.Demo.Hosting.Self.Program /platform:x86 /reference:/tmp/mono-GssQ/lib/mono/4.0/System.dll /reference:../lib/Nancy.dll /reference:../lib/Nancy.Hosting.Self.dll /reference:/tmp/mono-GssQ/lib/mono/4.0/System.Xml.Linq.dll /reference:/tmp/mono-GssQ/lib/mono/4.0/System.Data.DataSetExtensions.dll /reference:/tmp/mono-GssQ/lib/mono/4.0/Microsoft.CSharp.dll /reference:/tmp/mono-GssQ/lib/mono/4.0/System.Data.dll /reference:/tmp/mono-GssQ/lib/mono/4.0/System.Xml.dll /reference:/tmp/mono-GssQ/lib/mono/4.0/System.Core.dll /reference:/tmp/mono-GssQ/lib/mono/4.0/mscorlib.dll /warn:4
Target _CopyDeployFilesToOutputDirectoryAlways:
Creating directory '/tmp/build_19y6xv4nr43ic/src/bin/Views'
Copying file from '/tmp/build_19y6xv4nr43ic/src/Views/staticview.html' to '/tmp/build_19y6xv4nr43ic/src/bin/Views/staticview.html'
Target _CopyAppConfigFile:
Copying file from '/tmp/build_19y6xv4nr43ic/src/app.config' to '/tmp/build_19y6xv4nr43ic/src/bin/Nancy.Demo.Hosting.Self.exe.config'
Target DeployOutputFiles:
Copying file from '/tmp/build_19y6xv4nr43ic/src/obj/x86/Debug/Nancy.Demo.Hosting.Self.exe.mdb' to '/tmp/build_19y6xv4nr43ic/src/bin/Nancy.Demo.Hosting.Self.exe.mdb'
Copying file from '/tmp/build_19y6xv4nr43ic/src/obj/x86/Debug/Nancy.Demo.Hosting.Self.exe' to '/tmp/build_19y6xv4nr43ic/src/bin/Nancy.Demo.Hosting.Self.exe'
Done building project "/tmp/build_19y6xv4nr43ic/src/Nancy.Demo.Hosting.Self.csproj".
Done building project "/tmp/build_19y6xv4nr43ic/Nancy.Demo.Hosting.Self.sln".
Build succeeded.
0 Warning(s)
0 Error(s)
Time Elapsed 00:00:01.0730530
-----> Discovering process types
Procfile declares types -> local, web
-----> Compiled slug size is 78.3MB
-----> Launching... done, v18
http://deep-moon-1452.herokuapp.com deployed to Heroku
To git@heroku.com:deep-moon-1452.git
4d9e07b..6ce44e4 master -> master
I'm pleased to report that I have successfully deployed Nancy (a C# web framework) on top of Heroku.
It's far from a production ready solution and is completely unsupported by Heroku but it's an interesting experiment. More technical details in future posts but here's some proof.
Server response headers:
$ curl -i http://deep-moon-1452.herokuapp.com/
HTTP/1.1 200 OK
Content-Type: text/html
Date: Tue, 03 Jan 2012 16:33:02 GMT
Nancy-Version: 0.9.0.0
Server: Mono-HTTPAPI/1.0
Screenshot:
This is the output when you push your git repository to Heroku. The source code is built on Heroku.
$ git push heroku master
Counting objects: 9, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (4/4), done.
Writing objects: 100% (5/5), 514 bytes, done.
Total 5 (delta 3), reused 0 (delta 0)
-----> Heroku receiving push
-----> Fetching custom buildpack... done
-----> Mono app detected
-----> Fetching Mono binaries
tar: Ignoring unknown extended header keyword `SCHILY.dev'
tar: Ignoring unknown extended header keyword `SCHILY.ino'
tar: Ignoring unknown extended header keyword `SCHILY.nlink'
tar: Ignoring unknown extended header keyword `SCHILY.dev'
tar: Ignoring unknown extended header keyword `SCHILY.ino'
tar: Ignoring unknown extended header keyword `SCHILY.nlink'
tar: Ignoring unknown extended header keyword `SCHILY.dev'
tar: Ignoring unknown extended header keyword `SCHILY.ino'
tar: Ignoring unknown extended header keyword `SCHILY.nlink'
tar: Ignoring unknown extended header keyword `SCHILY.dev'
tar: Ignoring unknown extended header keyword `SCHILY.ino'
tar: Ignoring unknown extended header keyword `SCHILY.nlink'
tar: Ignoring unknown extended header keyword `SCHILY.dev'
tar: Ignoring unknown extended header keyword `SCHILY.ino'
tar: Ignoring unknown extended header keyword `SCHILY.nlink'
tar: Ignoring unknown extended header keyword `SCHILY.dev'
tar: Ignoring unknown extended header keyword `SCHILY.ino'
tar: Ignoring unknown extended header keyword `SCHILY.nlink'
tar: Ignoring unknown extended header keyword `SCHILY.dev'
tar: Ignoring unknown extended header keyword `SCHILY.ino'
tar: Ignoring unknown extended header keyword `SCHILY.nlink'
tar: Ignoring unknown extended header keyword `SCHILY.dev'
tar: Ignoring unknown extended header keyword `SCHILY.ino'
tar: Ignoring unknown extended header keyword `SCHILY.nlink'
tar: Ignoring unknown extended header keyword `SCHILY.dev'
tar: Ignoring unknown extended header keyword `SCHILY.ino'
tar: Ignoring unknown extended header keyword `SCHILY.nlink'
-----> Vendoring mono 2.10.8
-----> building via /tmp/mono-GssQ/bin/mono /tmp/mono-GssQ/lib/mono/4.0/xbuild.exe /tmp/build_19y6xv4nr43ic/Nancy.Demo.Hosting.Self.sln
XBuild Engine Version 2.10.8.0
Mono, Version 2.10.8.0
Copyright (C) Marek Sieradzki 2005-2008, Novell 2008-2011.
Build started 01/03/2012 16:28:24.
__________________________________________________
Project "/tmp/build_19y6xv4nr43ic/Nancy.Demo.Hosting.Self.sln" (default target(s)):
Target ValidateSolutionConfiguration:
Building solution configuration "Debug|Mixed Platforms".
Target Build:
Project "/tmp/build_19y6xv4nr43ic/src/Nancy.Demo.Hosting.Self.csproj" (default target(s)):
Target PrepareForBuild:
Configuration: Debug Platform: x86
Created directory "bin/"
Created directory "obj/x86/Debug/"
Target CopyFilesMarkedCopyLocal:
Copying file from '/tmp/build_19y6xv4nr43ic/lib/Nancy.dll' to '/tmp/build_19y6xv4nr43ic/src/bin/Nancy.dll'
Copying file from '/tmp/build_19y6xv4nr43ic/lib/Nancy.Hosting.Self.dll' to '/tmp/build_19y6xv4nr43ic/src/bin/Nancy.Hosting.Self.dll'
Target GenerateSatelliteAssemblies:
No input files were specified for target GenerateSatelliteAssemblies, skipping.
Target CoreCompile:
Tool /tmp/mono-GssQ/bin/dmcs execution started with arguments: /noconfig /debug:full /debug+ /optimize- /out:obj/x86/Debug/Nancy.Demo.Hosting.Self.exe Program.cs TestModule.cs /target:exe /define:"DEBUG;TRACE" /main:Nancy.Demo.Hosting.Self.Program /platform:x86 /reference:/tmp/mono-GssQ/lib/mono/4.0/System.dll /reference:../lib/Nancy.dll /reference:../lib/Nancy.Hosting.Self.dll /reference:/tmp/mono-GssQ/lib/mono/4.0/System.Xml.Linq.dll /reference:/tmp/mono-GssQ/lib/mono/4.0/System.Data.DataSetExtensions.dll /reference:/tmp/mono-GssQ/lib/mono/4.0/Microsoft.CSharp.dll /reference:/tmp/mono-GssQ/lib/mono/4.0/System.Data.dll /reference:/tmp/mono-GssQ/lib/mono/4.0/System.Xml.dll /reference:/tmp/mono-GssQ/lib/mono/4.0/System.Core.dll /reference:/tmp/mono-GssQ/lib/mono/4.0/mscorlib.dll /warn:4
Target _CopyDeployFilesToOutputDirectoryAlways:
Creating directory '/tmp/build_19y6xv4nr43ic/src/bin/Views'
Copying file from '/tmp/build_19y6xv4nr43ic/src/Views/staticview.html' to '/tmp/build_19y6xv4nr43ic/src/bin/Views/staticview.html'
Target _CopyAppConfigFile:
Copying file from '/tmp/build_19y6xv4nr43ic/src/app.config' to '/tmp/build_19y6xv4nr43ic/src/bin/Nancy.Demo.Hosting.Self.exe.config'
Target DeployOutputFiles:
Copying file from '/tmp/build_19y6xv4nr43ic/src/obj/x86/Debug/Nancy.Demo.Hosting.Self.exe.mdb' to '/tmp/build_19y6xv4nr43ic/src/bin/Nancy.Demo.Hosting.Self.exe.mdb'
Copying file from '/tmp/build_19y6xv4nr43ic/src/obj/x86/Debug/Nancy.Demo.Hosting.Self.exe' to '/tmp/build_19y6xv4nr43ic/src/bin/Nancy.Demo.Hosting.Self.exe'
Done building project "/tmp/build_19y6xv4nr43ic/src/Nancy.Demo.Hosting.Self.csproj".
Done building project "/tmp/build_19y6xv4nr43ic/Nancy.Demo.Hosting.Self.sln".
Build succeeded.
0 Warning(s)
0 Error(s)
Time Elapsed 00:00:01.0730530
-----> Discovering process types
Procfile declares types -> local, web
-----> Compiled slug size is 78.3MB
-----> Launching... done, v18
http://deep-moon-1452.herokuapp.com deployed to Heroku
To git@heroku.com:deep-moon-1452.git
4d9e07b..6ce44e4 master -> master
2011 - An Unexpected Journey
Sunday, January 01, 2012
When I started this post I wanted to reflect on the interesting year I've had. I wanted to talk about how launching a start-up had taught me so much about business, technology and myself. I wanted to go on and cover how it has also meant making sacrifices, such as missing Glastonbury even when I had a ticket and cutting back on spending, blogging, open source and conference speaking - the things I really enjoy. Finally, I wanted to end with how start-up life has sometimes meant working in isolation and at times being demotivated and stressed with how everything was going.
However, while it's important for me to look back I also want to focus on looking forward which can be summed up by this tweet:
To get the ball rolling, interested in hiring me? Send me an email at blog@benhall.me.uk
However, while it's important for me to look back I also want to focus on looking forward which can be summed up by this tweet:
#2012 Release more. Blog more. Drink more. Earn more.
— Ben Hall (@Ben_Hall) January 1, 2012
To get the ball rolling, interested in hiring me? Send me an email at blog@benhall.me.uk
Slides on Amazon Web Services (AWS) from DDD North
Monday, October 10, 2011
This weekend I had the pleasure of presenting on Amazon Web Services at DDD North. Please find my slides below which discusses S3, EC2, some architecture and other services provided by AWS.
If you have any questions, please ping me an email or tweet.
If you have any questions, please ping me an email or tweet.
Join @maydayhq as a start-up co-founder
Wednesday, August 31, 2011
Cross-posted with http://blog.maydayhq.com/2011/08/31/join-mayday-as-a-start-up-co-founder/
We currently have an exciting opportunity to join the founding team of Mayday. Ideally, the person would bring a level of visual design / UI / UX expertise in the role of a front-end developer and help us build an amazing product. As a co-founder, you’ll be a key member of the company at an early stage, involved in building the vision, product and the company.
The product is SaaS-based, enabling clients to improve their website by alerting them when and where users experience problems. Combining lightweight integration with ‘Big Data’ technologies, we monitor users engagement, interaction and client details allowing us to identity why they’re having problems.
Our concept is still evolving, and you’ll be in a position to make your mark. Mayday has the potential to have a huge impact on development, testing and production systems and impact how we handle modern software issues and their related testing concerns.
Mayday recently graduated from the Springboard Accelerator Programme in Cambridge and has been covered by sites including TechCrunch and TheNextWeb. The next stages for the company involve a funding round, building an amazing team to allow us to change the world and then achieving profit. The product is currently an early alpha, with a small number of users providing valuable feedback before opening it up to the private invite list. A demo is available at http://app.maydayhq.com/demo
Key characteristics for the role include:
- Passionate about startups. Building a company is amazing and extremely rewarding, but it takes a certain type of person.
- Passionate about building amazing products and changing the world.
- Capable of producing amazing visual design.
- Capable of turning an amazing visual design into reality via HTML, CSS, Javascript and any other cool tools you fancy.
- Understands the importance of UX, workflows and the key metrics required to monitor and improve.
- Self motivated, proactive while taking pride in their work and looking for ways to learn / improve.
Remuneration: Variable; let’s discuss. As a co-founder you’ll be a key part of the business with significant founder share options available.
Location: Old Street, London (open minded to other locations.)
Interested?
Email workwithus {at} Maydayhq.com and tell us about yourself. It would be great to hear about recent projects you’ve been excited about, examples of your work and links to github, Twitter, LinkedIn, blog etc.
Why not add something different to the mix by telling us what features you would love to see in Mayday and how you see it growing over the next few years? What other startups currently excite you and why?
If you don’t fit the role of front-end developer, but feel you could make a difference to the company and add value in a different role, please email and tell us – we’d love to hear from you!
We currently have an exciting opportunity to join the founding team of Mayday. Ideally, the person would bring a level of visual design / UI / UX expertise in the role of a front-end developer and help us build an amazing product. As a co-founder, you’ll be a key member of the company at an early stage, involved in building the vision, product and the company.
The product is SaaS-based, enabling clients to improve their website by alerting them when and where users experience problems. Combining lightweight integration with ‘Big Data’ technologies, we monitor users engagement, interaction and client details allowing us to identity why they’re having problems.
Our concept is still evolving, and you’ll be in a position to make your mark. Mayday has the potential to have a huge impact on development, testing and production systems and impact how we handle modern software issues and their related testing concerns.
Mayday recently graduated from the Springboard Accelerator Programme in Cambridge and has been covered by sites including TechCrunch and TheNextWeb. The next stages for the company involve a funding round, building an amazing team to allow us to change the world and then achieving profit. The product is currently an early alpha, with a small number of users providing valuable feedback before opening it up to the private invite list. A demo is available at http://app.maydayhq.com/demo
Key characteristics for the role include:
- Passionate about startups. Building a company is amazing and extremely rewarding, but it takes a certain type of person.
- Passionate about building amazing products and changing the world.
- Capable of producing amazing visual design.
- Capable of turning an amazing visual design into reality via HTML, CSS, Javascript and any other cool tools you fancy.
- Understands the importance of UX, workflows and the key metrics required to monitor and improve.
- Self motivated, proactive while taking pride in their work and looking for ways to learn / improve.
Remuneration: Variable; let’s discuss. As a co-founder you’ll be a key part of the business with significant founder share options available.
Location: Old Street, London (open minded to other locations.)
Interested?
Email workwithus {at} Maydayhq.com and tell us about yourself. It would be great to hear about recent projects you’ve been excited about, examples of your work and links to github, Twitter, LinkedIn, blog etc.
Why not add something different to the mix by telling us what features you would love to see in Mayday and how you see it growing over the next few years? What other startups currently excite you and why?
If you don’t fit the role of front-end developer, but feel you could make a difference to the company and add value in a different role, please email and tell us – we’d love to hear from you!
Labels: maydayhq
Count number of times a file has been download via HTTP logs
Wednesday, August 17, 2011
Today, I wanted to find out how many times a file had been downloaded from a web server. Without Google Analytics, it was time to pull out the big guns - grep.
The command I used was:
grep -o /e.js /var/log/lighttpd/access.log | wc -w
/e.js is the file I'm interested in, while access.log is the file.
The output of grep will be a long list of the string /e.js to indicate the matches. wc counts number of words. With the use of the pipe, you have a lovely quick command to find out how many times a file has been downloaded via your logs.
The command I used was:
grep -o /e.js /var/log/lighttpd/access.log | wc -w
/e.js is the file I'm interested in, while access.log is the file.
The output of grep will be a long list of the string /e.js to indicate the matches. wc counts number of words. With the use of the pipe, you have a lovely quick command to find out how many times a file has been downloaded via your logs.
Labels: unix
Social networks
Twitter GitHub SlideShare