Create droplet of your liking (ubuntu 12.10 x32)
ssh to root in terminal with your server ip
ssh [email protected]
Add ssh fingerprint and enter password provided in email
<?xml version="1.0"?> | |
<!DOCTYPE tsung SYSTEM "/opt/local/share/tsung/tsung-1.0.dtd" []> | |
<tsung loglevel="notice" version="1.0" dumptraffic="true"> | |
<!-- Each client that will be running Tsung during the test --> | |
<clients> | |
<client host="localhost" use_controller_vm="true" maxusers="1000" /> | |
</clients> | |
<!-- Each remote server that Tsung should performance test against. Only one would be needed if you have a load balancer. --> |
Create droplet of your liking (ubuntu 12.10 x32)
ssh to root in terminal with your server ip
ssh [email protected]
Add ssh fingerprint and enter password provided in email
<meta itemprop="name" content="[ TITLE ]" /> | |
<meta itemprop="image" content="[ LISTING IMAGE ]" /> | |
<meta itemprop="description" content="[ ARTICLE DESCRIPTION ]" /> | |
<meta name="description" content="[ ARTICLE DESCRIPTION ]" /> | |
<meta name="author" content="[ AUTHOR FULL NAME ]" /> | |
<meta property="article:author" content="[ GOOGLE+ AUTHOR URL ]" /> | |
<meta property="article:published_time" content="[ PUBLISHED TIMESTAMP ]" /> | |
<meta property="article:section" content="[ CATEGORY ]" /> |
In an earlier video we took a look at Rack to build incredibly lightweight web applications with Ruby. Rack's toolkit allowed us to quickly throw to get a working application, but we did have to put a little effort into it once we wanted to build something a little more complex.
Sometimes you want a fast and simple framework for building a simple web application. Perhaps you only need to respond to a handful of routes, or you want the response time for a small part of a bigger application to be lighting fast. The Sinatra framework is made for just these moments.
Today let's take a quick look at this framework and see how quickly we can build lightweight web applications.
To get started we first need to install the Sinatra gem:
gem install sinatra
#import <UIKit/UIKit.h> | |
@interface ExampleViewController : UIViewController | |
@end | |
#pragma mark - | |
@implementation ExampleViewController | |
- (void)viewDidLoad |
0. SSH to server | |
1. Edit /opt/bitnami/apps/jenkins/jenkins_home/config.xml | |
2. set userSecurity to false: <userSecurity>false</userSecurity> | |
3. delete | |
<authorizationStrategy> and <securityRealm> | |
4. /etc/init.d/bitnami restart |
function functionReplacer(key, value) { | |
if (typeof(value) === 'function') { | |
return value.toString(); | |
} | |
return value; | |
} | |
function functionReviver(key, value) { | |
if (key === "") return value; | |
jQuery does good jobs when you're dealing with browser compatibility. But we're living in an age that fewer and fewer people use old-school browsers such as IE <= 7. With the growing of DOM APIs in modern browsers (including IE 8), most functions that jQuery provides are built-in natively.
When targeting only modern browsers, it is better to avoid using jQuery's backward-compatible features. Instead, use the native DOM API, which will make your web page run much faster than you might think (native C / C++ implementaion v.s. JavaScript).
If you're making a web page for iOS (e.g. UIWebView), you should use native DOM APIs because mobile Safari is not that old-school web browser; it supports lots of native DOM APIs.
If you're making a Chrome Extension, you should always use native APIs, not only because Chrome has almost the latest DOM APIs available, but this can also avoid performance issue and unnecessary memory occupation (each jQuery-driven extension needs a separate
/* | |
* author Huber Flores | |
*/ | |
# Install on each Node | |
$ su | |
# Perl Templating-Toolkit and the Gnu plotting utility to create HTML and graphical reports with the result data set. | |
$ apt-get install gnuplot-nox libtemplate-perl libhtml-template-perl libhtml-template-expr-perl |
sudo apt-get install vim tmux git curl