In the original Kohana wiki application the URLs in the views were hardcoded. If we wanted to change the domain name or restructure a route we would need to go through the application and change every single URL.
Thankfully the Kohana Route class comes with a method url() which allows us to generate URLs to routes we have specified in the application. In the first tutorial we defined the following routes in application/bootstrap.php:
Route::set('wiki-edit', 'wiki/<page>/edit')
->defaults(array(
'controller'=> 'wiki',
'action' => 'edit_page',
));
Route::set('wiki-save', 'wiki/<page>/save')
->defaults(array(
'controller'=> 'wiki',
'action' => 'save_page',
));
Route::set('wiki-page', 'wiki/<page>')
->defaults(array(
'controller'=> 'wiki',
'action' => 'view_page',
));
Route::set('default', 'wiki')
->defaults(array(
'controller' => 'wiki',
'action' => 'view_page',
'id' => 'index',
));
Before we can generate routes we need to set some configuration options in application/bootstrap.php (line ~82). We need to specify the base_url and index_file attributes in the array passed to Kohana::init(). The application on my local install is located at 127.0.0.1/query7kwiki/index.php, so my Kohana::init() statement would read:
Kohana::init(array(
'base_url' => '/query7kwiki/',
'index_file' => 'index.php'
));
In application/views/edit.php the form action attribute was hardcoded to the value /query7kwiki/index.php/wiki/. That can be replaced by:
<?php echo Route::url('wiki-save', array('page' => $page)); ?>
In application/views/single.php there is a…
In this tutorial you will learn how to create a simple wiki using the PHP framework Kohana version 3.1. Several years ago Siddharta Govindaraj created a screencast demonstrating how to create a wiki using Django, this is essentially the Kohana version of that. It covers using Kohana’s Routing, ORM and MVC systems. Full source code of the application is available on github.
The wiki application has 3 different pages:
- /wiki/somepage/save – handles the saving of the page
- /wiki/somepage/edit – displays a form that allows the user to edit the page
- /wiki/somepage – displays the page
Configuration
We will be using the ORM module to query the database for our wiki pages so we must load it in the application/bootstrap.php file (Line ~99).
Kohana::modules(array(
'database' => MODPATH.'database', // Database access
'orm' => MODPATH.'orm', // Object Relationship Mapping
));
We also need to specify our database configuration settings. This is done in application/config/database.php.
<?php
return array
(
'default' => array
(
'type' => 'mysql',
'connection' => array(
'hostname' => '127.0.0.1',
'username' => 'root',
'password' => 'root',
'persistent' => FALSE,
'database' => 'query7kwiki',
),
'table_prefix' => '',
'charset' => 'utf8',
'caching' => FALSE,
'profiling' => TRUE,
),
);
…
Dojo is an open source Javascript toolkit. It provides an easy way to access and modify the DOM as well as a rich user interface widget library. One of the most powerful widgets in the Dojo toolkit is DataGrid. It provides an easy way to represent what is essentially a cross between a spreadsheet and a table. In a recent Django project I needed to output the contents of a model into the DataGrid. Thanks to django-dojoserializer this is very easy.
Setup
We need the Python package django-dojoserializer. This can be installed by downloading the source and running
python setup.py install
or with setuptools using
easy_install django-dojoserializer
or with pip using
pip install django-dojoserializer
Then add django-dojoserializer to the INSTALLED_APPS tuple in settings.py.
Dojo will need to be linked correctly in the Django template. We need to require the dojox.grid.DataGrid and dojo.data.ItemFileReadStore classes.
<script src="/static/libs/dojo/dojo.js" djConfig="parseOnLoad: true">%lt;/script>
<script type="text/javascript">
dojo.require('dojox.grid.DataGrid');
dojo.require('dojo.data.ItemFileReadStore');
</script>
Django Model
PROXY_TYPE_CHOICES = (
('SOCKS4', 'SOCKS4'),
('SOCKS5', 'SOCKS5'),
('HTTP', 'HTTP'),
)
class Proxy(models.Model):
ip = models.CharField(max_length=50)
type = models.CharField(max_length=6, choices=PROXY_TYPE_CHOICES)
alive = models.BooleanField(default=False)
added = models.DateTimeField(auto_now=False, auto_now_add=True)
last_checked = models.DateTimeField(auto_now=True, auto_now_add=False)
def __unicode__(self):
return self.ip
Django View
The view needs…
Introduction
In a recent Django project I needed to issue some HTTP requests to a website, save the results and then display the information to the user. I could have issued those HTTP requests in a Django view, however the requests could take up to 10 seconds to return, and I didn’t want the page hanging that long for the user. I ended up using Celery, an asynchronous task queue written in Python, to execute the requests.
Installation
Celery
Celery is in pypi so installation is simple.
easy_install celery
pip install celery
Or download the source code, extract it and
python setup.py install
Django + Celery
In a high traffic production environment Celery should be paired with the RabbitMQ backend. However for my low traffic application I went with the django-kombu backend. django-kombu uses the Django database as a message store and requires very little configuration compared to other backends. We also need the djcelery package.
easy_install django-kombu
easy_install django-celery
Configuration
Before we can start using Celery we need configure our Django project. In settings.py make sure you add djkombu and djcelery to the INSTALLED_APPS tuple. Also make sure your database is configured and working.
Also add…
NodeJS is a powerful evented Javascript platform running on top of Google’s V8 javascript engine. Over the last year the popularity of NodeJS has increased greatly, as shown by the number of discussions on programming forums such as Hacker News, Reddit and Stackoverflow. Despite this NodeJS is still young and it falls short to Python and Ruby when it comes to the number and range of libraries and modules available.
The Problem
I wanted to convert one of my web scraping applications I made in PHP to NodeJS. The application interacts with SOCKS4 and SOCKS5 proxies using PHP’s cURL bindings. Unfortunately there are no cURL bindings (or SOCKS protocol wrappers) written for NodeJS. NodeJS does come with an HTTP client module that can issue web requests, however it doesn’t support SOCKS proxies.
The Solution
Although there are no specific NodeJS bindings for cURL, we can still issue cURL requests via the command line interface. NodeJS comes with the child_process module which easily allows us to start processes and read their output. Doing so is fairly straight forward. We just need to import the exec method from the child_process module and call it. The first parameter is the command…
In this series of tutorials we use Appcelerator’s Titanium Mobile platform to create Android applications. This tutorial walks you through developing and packaging a soundboard application. Full source and packaged application is available on github.
In this series of tutorials we use Appcelerator’s Titanium Mobile platform to create Android applications. This tutorial walks you through developing and packaging your first Titanium application. Full source and packaged application is available on github.
If you are new to using PHP and cURL please refer to the PHP cURL tutorial. It covers why you should using cURL (as opposed to file_get_contents) and goes over how to make cURL requests with a custom class.
This tutorial will cover how to use different types of proxies – SOCKS4, SOCKS5 and HTTP with cURL.
Basic cURL Request
We’ll start by creating a simple cURL script that requests the web page checkip.dyndns.org and displays the result on the screen. The website just displays our current IP address, this is useful when working with proxies. Below is our very basic cURL request.
$url = 'http://checkip.dyndns.org/';
$c = curl_init($url);
curl_setopt($c, CURLOPT_RETURNTRANSFER, true);
$result = curl_exec($c);
echo '<pre>';
var_dump($result);
echo '</pre>';
curl_close($c);
As we can expect, the output will be your IP address.
202.183.56.21
Using Proxies with cURL
To use proxies with cURL we need to set 2 additional cURL options: CURLOPT_PROXYTYPE and CURLOPT_PROXY. CURLOPT_PROXYTYPE should be set to either CURLPROXY_SOCKS5 or CURLPROXY_SOCKS4, depending on the type of proxy you are using. CURLOPT_PROXY should be set to the IP address and port of the proxy you are using.
If you are using an HTTP proxy then you…
Skype4Py is a Python module that allows developers to programatically interact with the Skype client running on their computer. In this tutorial we will look at and use the Skype4Py module to create simple but useful scripts.
Installation
Skype4Py is a normal Python module and is listed in the Python package index (Pypi). To install it with setuptools enter the following in a command prompt.
easy_install Skype4Py
To install it with pip enter the following in a command prompt.
pip install Skype4Py
Getting Started
Skype4Py interacts with the Skype client running on your desktop, it doesn’t talk directly to the Skype servers. For any of the scripts we cover in this tutorial to work the Skype application must be running and you need to be logged in. You can either start Skype yourself or use the following snippet to start it using Skype4Py.
s = Skype4Py.Skype()
if not s.Client.IsRunning:
s.Client.Start()
Before we can interact with the Skype client from Skype2Py, we need to connect Skype4Py to the instance of Skype running on your desktop. This is done using the Attach method.
import Skype4Py
s = Skype4Py.Skype()
s.Attach()
After executing this you need to check the Skype client on…
In this tutorial we will cover how to build a module from scratch in Kohana 3. If you aren’t familiar with the Kohana framework then I recommend you read the beginners introduction to Kohana.
The Plan
We will be building a module that replaces Kohana’s own view layer (Kohana_View). It will use the PHP template library Twig. We want our own view layer to be API compatible with Kohana’s view layer. This will ensure that other modules work out of the box and that the only code the developer will need to alter in their application are the templates (so that they are Twig compatible). No code in any controller will need to be modified.
Because Kohana follows HMVC (see beginners introduction to Kohana) we will be calling our class View. This means that all calls in the application to the class of View will be to the View class in our module, not Kohana’s own View class.
Directory Structure
Enabling The Module
The name of any Kohana module is the same name as the directory inside the modules directory. So in this case it is twig. To activate any module, we must add it…
Subscribe to feeds
