Saturday, July 25, 2009

Plesk 9.2 and files starting with dot

After the default setup of Plesk 9.2 for Unix, the default FTP config hides the files starting with dot. To resolve this problem with the latest versions of ProFTPd, you have to add the following line to the /etc/proftpd.conf:

ListOptions “-a”

More information on this directive

Thursday, July 23, 2009

Plesk 9.2 and the postmaster

My company uses Plesk to provide hosting services to our Clients. We faced with the problem of creating the default domain e-mail addresses for all domains. I mean postmaster@domain.com, root@domain.com, and abuse@domain.com.

To create these e-mail addresses the easiest way is to create a script which copies the .qmail-postmaster file into each domain’s mailnames (/var/qmlail/mailnames) folder. So I wrote the following little script to do this updated, and I called it from crontab periodically.

#!/bin/bash for domain in `ls /var/qmail/mailnames/ | xargs`; do if [ ! -f "/var/qmail/mailnames/$domain/.qmail-postmaster" ] then echo "Updating postmaster account for $domain domain" cp /var/qmail/alias/.qmail-postmaster /var/qmail/mailnames/$domain/.qmail-root cp /var/qmail/alias/.qmail-postmaster /var/qmail/mailnames/$domain/.qmail-abuse cp /var/qmail/alias/.qmail-postmaster /var/qmail/mailnames/$domain/.qmail-postmaster fi done

But it not works with the Domain Aliases (as Plesk calls them). These are the virtual domains in the Qmail’s language. So I will try to dig how it works fine with these virtual ones.

After a couple of days…

I found the answer for my question. I wrote a script which queries the Plesk’s database for domains with aliases and creates a symbolic link to the domain’s folder in the mailnames QMail folder.

Friday, May 1, 2009

How to delete Team Project on TFS 2008

I have experienced some issue while deleting Team Projects.

Because we had too many obsolete projects on our Team Foundation Server, we decided to delete them. First I backed up the whole database. For the detailed instruction, read Microsoft’s paper: How to: Back Up a Team Foundation Server

To delete a Team Project, you have to use the TFSDeleteProject command from the Visual Studio 2008 Command Prompt. This operation cannot be done from the Team Explorer.

Preparation

Before doing this operation we have to clarify what will be the state of the branched code. I have found the answer on the following Microsoft site: Using TFSDeleteProject to Delete Projects on Team Foundation Server. The FAQ section’s first question clarifies this issue: only those source control items will be deleted whose in the deleted Team Project. The deletion not will operate outside of the given Team Project. I tried it, and it really works in this way. Note if you delete the parent of branch it will be orphaned. The work items (bugs, and more) will be deleted too.

The TFSDeleteProject command cannot be executed without all required security permission.

You have to be in the Team Project’s Administrators. To set it go to Team Explorer in Visual Studio. Right click on the team project, and select Team Project Settings > Group Membership…

image

Select the Project Administrators group, and press Properties button.

image

Add your user to the list.

You must be the SharePoint site’s Administrator.

Go to the SharePoint Central Administration Site.

image

Select the Application tab and then the Site collections administrators.

image

Select the Site Collection associated with the given Team Project and set the Primary site collection administrator to your user.

The execution

After the preparation you can issue the following command:

> TFDeleteProject /server:YOURSERVER TEMPPROJECT

The command asks for your confirmation:

Warning: Deleting a team project is an irrecoverable operation. All version control, work item tracking and Team Foundation build data will be destroyed from the system. The only way to recover this data is by restoring a stored backup of the databases. Are you sure you want to delete the team project and all of its data (Y/N)?y

If everything went good you will see the following:

Deleting from Build ...
Done
Deleting from Work Item Tracking ...
Done
Deleting from Version Control ...
Done
Deleting Report Server files ...
Done
Deleting SharePoint site ...
Done
Deleting from Team Foundation Core ...
Done

After the deletion the Team Project disappears immediately, but the Version Control items will be only flagged as they can be deleted. The Team Foundation Server will delete these items at next midnight. You can hurry this by executing the job manually. You can read here how to do this: http://msdn.microsoft.com/en-us/library/dd206696.aspx#jobhistory

Thursday, February 5, 2009

VS.Php 2.6 available!

After a long development period the new version of VS.Php (2.6) officially released by Jcx.Software! This is my favorite tool for PHP editing. I think it's a great combination of two technologies which are so far away from each other. (Visual Studio 2008 and PHP)

So I downloaded the new version today. I own the 2.x for Visual Studio 2008 licence. After the installation, the system asked me to enter the serial number. It doesn't accept the old serial number. Pardon. To be exact: it accepts the old serial, but asks to go to the website and request a new one. Prepare yourself: you have to find the order number...

The new serial is came instantly after submitted my request. Fine. I will try the new version in the next weeks. I'll share my experience.

What's new in 2.6

(from the developer's site)

Major Changes

  • Project-wide intellisense support
  • Drag and drop files in solution view
  • IIS7 integration for creating, debugging PHP applications on IIS7
  • Handle very large projects with ease (10000+ files)

Minor Changes

  • Improved bracket matching support with custom background color
  • Zend Framework 1.7.3
  • Intellisense has two tabs, one for frequently used items and one for project wide items
  • Add more flexibility in customizing color coding of PHP tokens
  • Numerous performance improvements
  • Fix issues with updater on x64 systems
  • Use PHP CGI for built-in Apache for increased stability
  • Add MS SQL Server PHP module to the list of available modules for intellisense and built-in preview engine
  • Include PHP 5.2.6 and PHP 4.4.9
  • Include $argv and $argc for globals
  • Show disconnected overlay icon when there is no local copy of the file.
  • Speed up the solution refresh command, in particular which very large projects.
  • Allow remote server project wizard to continue even if the wizard fails to run phpinfo on the remote server to collect server information.
  • Many bug fixes!

 

More information: http://www.jcxsoftware.com/jcx/home