I visited the BMW website the other day and found that they have a screensaver type of effect on their page. So it got me thinking and I decided to write my own script in MooTools which would let me fire some functions when the user goes idle and when they return. Check out the code and demo after the jump.
Currently browsing Programming
OpenDNS’ services are excellent, but their URL redirections and rewritings can sometimes get in the way of regular browsing. My one particular grievance is their URL rewriting when a URL fails to resolve. I’ve written a small bookmarklet which helps you reload the original URL in case this happens. Check out the code and bookmarklet after the jump.
In the final part of the guide we will automate a couple of systems to get Warehouse and svnserve working together. First we will create a basic hook that will automatically syncrhonize Warehouse when we commit a changeset and finally we will make Warehouse manage our authz and passwd to easily manage access from the web client. Once that is done, our system will be fully functional.
Browsers have mechanisms to distinguish between a left click and a right click, but there are other types of clicks like clicks with shortcut keys that often get overlooked. These tend to perform specific behaviors like opening a new tab, so they should be treated differently than a normal click. With a bit of MooTools scripting, we can check for these types of clicks and take action as needed.
In the first part of the configuration stage, we will prepare and test svnserve to interface with Warehouse. This involves creating a svnserve.conf file with the correct settings to protect and give access to our repository. We will also initialize Warehouse app which will link it to our repositories and allow web access to our code. In the next part we will link svnserve and Warehouse together and our set up will be complete!
In part three of Roll your own Subversion server, we will download and install Warehouse on our server. We will also initialize the app by creating the necessary MySQL databases and users and we will configure the Thin/Nginx servers to begin serving the app. At the end of this guide all the groundwork will be done and we will then move to configure svnserve and Warehouse to our liking.
In part one of Roll your own Subversion Server, we will deploy a Cloud VPS from scratch with the necessary components to power Subversion and Warehouse. We will install the web stack to power Warehouse which consists of Ruby on Rails, a Thin web server cluster to run the app, a Nginx web server to serve static files and proxy requests to Thin, and a MySQL database backend. Additionally we will install Webmin to configure and monitor our server as well as optimize and secure the VPS.
Roll your own Subversion server will focus on getting a Subversion server setup powered by svnserve and Warehouse on a small 256 MB cloud VPS. But the lessons go beyond that. You will learn how to deploy a cloud VPS server, install a full Ruby on Rails stack, and will also configure and optimize your server to keep it from overloading. In the end, you will have a private Subversion server for under $15 a month and will be able to kick-start a VPS setup from scratch without a hitch.