Creating svn directories

svn mkdir -m "create default directories" http://svn.clients.rajatpandit.com/project-name/trunk http://svn.clients.rajatpandit.com/project-name/tags http://svn.clients.rajatpandit.com/project-name/branches

Checkout these directories locally:

svn co http://svn.clients.rajatpandit.com/project-name/ .

Move to the trunk directory

cd trunk

Creating a new project

$  symfony generate:project brp
$ php symfony generate:app --escaping-strategy=on --csrf-secret=s3cr3t fe

Clear cache and log and add that to svn

rm -rf cache/* log/*
chmod 777 cache/ log/
svn add *

svn propedit svn:ignore cache
svn propedit svn:ignore log

Enter * in both the cases so that no files in cache and log get commited to svn

Add the new files to svn

svn ci -m 'adding the initial set of files'

Update the database settings, add the doctrine plugin and disable the propel plugin instead, edit the file config/ProjectConfiguration.class.php
and update the line with the following line:

  $this->enableAllPluginsExcept(array('sfPropelPlugin', 'sfCompat10Plugin'));

Publish the plug-in assets

rp@devbox:~/websites/project-name/trunk$ php symfony plugin:publish-assets
    plugin    Configuring plugin - sfProtoculousPlugin
    plugin    Configuring plugin - sfDoctrinePlugin

Delete the files for the propel plugin:

svn delete web/sfPropelPlugin
svn delete config/propel.ini
svn delete config/schema.yml
svn mkdir config/doctrine

Create new schema file and remove the default schema file.

rp@devbox:~/websites/project-name/trunk$ cd config/doctrine/
rp@devbox:~/websites/project-name/trunk/config/doctrine$ touch schema.yml
rp@devbox:~/websites/project-name/trunk/config/doctrine$ svn add schema.yml
A         schema.yml
rp@devbox:~/websites/project-name/trunk/config/doctrine$ svn ci -m 'adding schema for app'

svn delete config/databases.yml
svn ci -m 'removed the default databases.yml file'

Add database configuration settings:

php symfony configure:database --name=doctrine --class=sfDoctrineDatabase "mysql:host=127.0.0.1;dbname=project1" root password

Link to externals so that the latest version of the plugins and symfony gets checked out:

cd lib/
svn mkdir vendor
svn propedit svn:externals lib/vendor
svn ci -m 'updating symfony to version 1.2.7'
svn update lib/vendor/

That pulls out the most updated tagged version of symfony.

Update the configuration file config/ProjectConfiguration.class.php to use the local symfony version instead of the site-wide settings.

require_once dirname(__FILE__) . '/../lib/vendor/symfony/lib/autoload/sfCoreAutoload.class.php';

Share:

JeOS on VirtualBox has been my preferred distro/app for running vm for basic development for a while now, thanks for Brad’s post and it has worked quite well for me so far.

One of the problems that I faced when setting up development environments for the team was when we prepared an image and copied over to a server to run it for other users to use, it would loose all its networking settings. The solution for its fix was as follows:

#ifconfig -a

This will show you all the interfaces, even the ones that dont show up when you run ifconfig by itself. If you can see the eth0.. etc in there then edit the file at /etc/udev/rules.d/70-persistent-net.rules

#sudo vi /etc/udev/rules.d/70-persistent-net.rules

remove all the entries in it that were returned by the ifconfig -a command, save and reboot. When the networking service gets started again (actually you could just restart the service ‘networking’ rather than rebooting the vm) the interfaces would get configured correctly.

Share:

I had to implement custom events on JQuery found this kind of working for what I needed it to do. Not so sure if this was the most ideal way to do it, but would be worth getting your views on it.

$(document).ready(function() {
	$(document).bind('custom-event', doSomething);
	$(document).bind('custom-event', doAnotherthing);

	$('#some_name').click(function() {
		$(document).trigger('custom-event', ['foo1', 'foo2']);
	});

});

function doSomething(e, param1, param2) {
	console.log(arguments);
	console.log('doing something..');
}
function doAnotherthing(e, param1, param2)
{
	console.log(arguments);
	console.log('doing another thing..');
}

Share:

This week, since I no longer have access to VMWare Fusion (where things just worked out of the box), i had to consider setting up my vms on the one of the popular open source alternatives VirtualBox.

Its pretty neat and easy to setup and getting a vm installed and running on it, however the first thing that struck me was that the VM are setup to use NAT which means that the VM can ping the host and the internet, but cannot be contacted by the outside world, not even the host. This being a great idea in case you need it just to check your emails or surf the internet in a safe manner, turns out to be a limitation is you are like me, interested in hosting your servers on the vm to be used as a dev box.

It turns out that virtual machine receives its network address and configuration on the private network from a DHCP server integrated into VirtualBox. The IP address thus assigned to the virtual machine is usually on a completely different network than the host. As more than one card of a virtual machine can be set up to use NAT, the first card is connected to the private network 10.0.2.0, the second card to the network 10.0.3.0 and so on. If you need to change the guest-assigned IP range for some reason, please refer to the section called “Configuring the address of a NAT network interface”.

Pinging this ip adress from the host doesnt work as its on a different subnet than the host (as its usually the case). The documentation for virtualbox states if you need to access a server on the guest on the host, you would need to setup Port Forwarding on the host so that the traffic on the host is directed to a port on the vm.

This turns out to be a pretty handy feature, especially since it can be used to protected your server from OS specific exploitable vulnerabilities, as the actual OS hosting the service can not be contacted. Obviously its assumed that in this case the host/guest OS are not the same .

So here’s my sample setup. I am running a LAMP server on my guest os an image of JeOS and for now i am only concerned about accessing the webserver on my host machine and also from other machines on the network (something that you cant do out of the box on VMWare Fusion, though i am sure it can be done on it by one means or the other).

I run the following commands:

  # VBoxManage setextradata "JeOS" "VBoxInternal/Devices/pcnet/0/LUN#0/Config/guesthttp/Protocol" TCP
  # VBoxManage setextradata "JeOS" "VBoxInternal/Devices/pcnet/0/LUN#0/Config/guesthttp/GuestPort" 80
  # VBoxManage setextradata "JeOS" "VBoxInternal/Devices/pcnet/0/LUN#0/Config/guesthttp/HostPort" 8080

The above example assumes a PCNet virtual network card; if you have configured the guest to use the Intel PRO/1000, replace “pcnet” with “e1000″ in the above commands. Similarly, if you want to configure a different interface instance replace the /0/ with the appropriate index. pcnet and e1000 are counted separately in this respect, and counting starts at 0 for both types.

The name guesthttp is an arbitrary one chosen for this particular forwarding configuration. With that configuration in place, all TCP connections to port 8080 on the host will be forwarded to port 80 on the guest. Protocol can be either of TCP or UDP (these are case insensitive). To remove a mapping again, use the same commands, but leaving out the values (in this case TCP, 80 and 8080).

It is not possible to configure incoming NAT connections while the VM is running. However you can change the settings for a VM which is currently saved (or powered off at a snapshot).

Share:

defaults write com.macromates.textmate OakDocumentDisableFSMetaData 1

Share:

Also means that it looks really ugly on the terminal. So here are the commands to reset it permanently so that it doesn’t change again after a reboot.

$ sudo hostname foobox.local
$ sudo scutil --set HostName foobox.local
$ sudo scutil --set LocalHostName foobox

Share:

If you want to write code for a criteria object for the SQL statement which is something like this.

SELECT field1, field2 from table1 where field1 in (5,30,23)

The corresponding PHP for that would be as follows

$values = array(5,30,23);
$criteria_for_select = new Criteria();
$c = new Criteria();
$criteria_for_select = $c->getNewCriterion(table1::field1, $values, Criteria::IN);

That’s pretty much it, now this criteria object $criteria_for_select can now be used in your doSelectXXX calls.

Another really cool app that automates the task of writing criteria object is availabile here.
http://propel.jondh.me.uk/

The cool thing about this utility is you drop in your selection condition and it will write the code for the criteria object for you, now that’s really cool.

Share:

Share:

This is what you would get if you have a similar problem:

% curl -k https://www.yahoo.com
curl: (1) Protocol https not supported or disabled in libcurl

The problem is that you would usually have something that depends on curl so you cant install the version of curl with its variant straightaway, so you will first need to remove the dependent first, then remove curl and clean up the install and then finally install curl with its ssl variant followed by its dependents.

The steps are something like this:

busybox:web rp$ sudo port uninstall curl @7.19.3_0 curl @7.19.3_0+ssl
--->  Unable to uninstall curl 7.19.3_0, the following ports depend on it:
--->  	php5
Error: port uninstall failed: Please uninstall the ports that depend on curl first.
busybox:web rp$ sudo port uninstall curl @7.19.3_0 curl @7.19.3_0+ssl
busybox:web rp$ sudo port uninstall php5
--->  Deactivating php5 @5.2.9_0+apache2+macosx+mysql5+pear+sqlite
--->  Uninstalling php5 @5.2.9_0+apache2+macosx+mysql5+pear+sqlite
busybox:web rp$ sudo port uninstall curl @7.19.3_0 curl @7.19.3_0+ssl
--->  Deactivating curl @7.19.3_0
--->  Uninstalling curl @7.19.3_0
--->  Uninstalling curl @7.19.3_0+ssl
busybox:web rp$ sudo port install php5 @5.2.9_0+apache2+macosx+mysql5+pear+sqlite
Error: Requested variants do not match original selection.
Please perform 'port clean curl' or specify the force option.
Error: The following dependencies failed to build: curl
Error: Status 1 encountered during processing.
busybox:web rp$ sudo port clean curl
--->  Cleaning curl
busybox:web rp$ sudo port clean php5
--->  Cleaning php5
busybox:web rp$ sudo port clean php5
--->  Cleaning php5
busybox:web rp$ sudo port clean curl
--->  Cleaning curl
busybox:web rp$ sudo port clean php5
busybox:web rp$ sudo port install curl +ssl
--->  Fetching curl
--->  Verifying checksum(s) for curl
--->  Extracting curl
--->  Configuring curl
--->  Building curl
--->  Staging curl into destroot
--->  Installing curl @7.19.3_0+ssl
--->  Activating curl @7.19.3_0+ssl
--->  Cleaning curl
busybox:web rp$ sudo port install php5 @5.2.9_0+apache2+macosx+mysql5+pear+sqlite
--->  Fetching php5
--->  Verifying checksum(s) for php5
--->  Extracting php5
--->  Applying patches to php5
--->  Configuring php5
--->  Building php5
--->  Staging php5 into destroot
Warning: php5 requests to install files outside the common directory structure!
--->  Installing php5 @5.2.9_0+apache2+macosx+mysql5+pear+sqlite

If this is your first install, you might want
cd /opt/local/apache2/modules
/opt/local/apache2/bin/apxs -a -e -n "php5" libphp5.so

* copy  /opt/local/etc/php.ini-dist to  /opt/local/etc/php.ini
--->  Activating php5 @5.2.9_0+apache2+macosx+mysql5+pear+sqlite
--->  Cleaning php5

Share:

Step 2: Update variable myhostname in the file /etc/postfix/main.cf
Set the variable to your hostname, you might need to uncomment the default value.

Step 3: Find your php.ini file and update the sendmail_path and make it
/your/path/sendmail -t -i

Now open another terminal window and do a tail on the log file to see if you have any further errors.
tail -f /var/log/mail.log

You can start the server by running the following command:

sudo postfix start

The above changes worked for me, however you might need to investigate this a little more if you still have trouble.

Share: