Web server: Linux (Ubuntu on my dev setup), Apache, PHP 5.3, Symfony 1.4, Doctrine 1.2.
Database server: Microsoft Windows 2008 Server, MS SQL Server
Trying to get Symfony to talk to the database server has been a painful experience for the last few days. But perseverance has paid off.
Lots of Googling with trial & error has resulted in actually achieving a development setup that will mirror the eventual production setup.
- Follow the FreeTDS and ODBC setup instructions of http://jamesrossiter.wordpress.com/2011/03/08/connecting-to-microsoft-sql-server-using-odbc-from-ubuntu-server/
- Use the following in config/databases.yml
In the above snippit, replace ‘datasourcename’ with whatever you used in /etc/odbc.ini and replace ‘sqlserver’ with the name used in /etc/freetds/freetds.conf & /etc/odbc.ini
It’s late and I’ve been struggling to get this working for some time. I may expand this entry in the future if required.
References and insperation:
Via the Ubuntu Software Centre:
- Search for thunderbird
- Click on the search result “Thunderbird Email” and then on the “More Info” button
- Enable at least the “Calendar Extension for Thunderbird – Google Calendar support (xul-ext-gdata-provider)”
- Install the add-ons
- Open your Google Calendar in your web browser
- In the left-hand column, under “My calendars”, hover over the calendar of choice and click the down arrow that appears after the calendar name
- Select “Calendar settings”
- Close to the bottom of the page will be the “Calendar ID” (in my case it is my full email address. Make a note of this ID.
- Start up Thunderbird upon completion.
- File -> New -> Calendar
- Select “On the Network” and click Next
- Select “CalDAV”
- In the Location field enter: https://www.google.com/calendar/dav/calendar.id.noted.in.point.8/events
- Click Next then enter a name for the calendar and set an email account against it
- When prompted, enter your username and password for accessing this calendar
Installed Ubuntu 10.04 from ISO onto a blank virtual box machine.
All worked well for a while, until I recently did an aptitude safe-upgrade.
The next time I booted the system, mysql failed to start and refused to do so when I issued: sudo service mysql start
It would just hang there.
Tracked the issue down to this bug. How I maged to get get it to work:
In a terminal: sudo /usr/sbin/mysqld
In another terminial:
sudo service mysql start
sudo service mysql stop
sudo killall mysqld
Now mysql will start and stop on the system as it should.
[nb: this is a rough artical, I will flesh it out when I have more time]
[edit 27-05-2010: this is not a permanent fix and requires to be executed after every system start. Looking forward to a fix on this…]
[edit 22-06-2010: see Ryan’s comment to fix this issue. I hope this helps others :)]