Over the years, we have built our own PHP development environment, based on the open-source Zend framework. We have a strong belief in the Model-View-Controller (MVC) architecture, and strict version control with Subversion (SVN), because the results are cleaner, more efficient code. Utilizing the Zend framework also gives us access to the large and expanding library for Rapid Application Development (RAD), while still having the flexibility to customize the framework and make it our own.

Using the MVC design pattern allows us to have a clear separation of business logic and presentation logic.  This presents a distinct advantage when building web applications because it separates what the user sees from what goes on in the background.  This moves away from mixing data-layer code, such as database queries, in with your display code and allows us to create reusable modules, such as photo galleries and shopping carts, for significantly faster builds in large applications.

The MVC architecture also offers ease of maintenance, since each component (model, view and controller) is self contained, performing upgrades and changes, such as switching databases from Access to MySQL, become much less painful and cumbersome then in the past.

We make it a priority to stay on the frontline of the ever changing technology in the Web and Internet industry; currently, we are working on a 2.0 version of our framework that will use portions of Domain Driven Design (DDD) to create clean structure and more efficient code patterns.  One of the biggest changes on the way is a central code base with customizable modules.  With this 2.0 framework we will be able to increase our build time on large projects, and push upgrades to a central code base rather then individual applications.

But don’t think that since we developed our own PHP framework we are averse to working with other languages.  Just send your application our way and we are happy to roll up our sleeves, jump into your Ruby/Flash/ASP project and get our hands dirty.

————————————————————————————————————–

Founded in 1995, WebSight Design offers business clients a range of website design and development services, including website programming, website hosting, website marketing, and colocation management.

WebSight Design in Development is a post from: WebSight Design, Inc. company blog. With headquarters in the San Francisco bay area, WebSight Design, Inc. has been providing world class web engineering, creative design and hosting solutions since 1995. WebSight Design

How to solve this? It is really easy actually. There are 2 possible solutions, the first is the easiest, but really shouldn’t be considered and that is to make the folders that PHP needs to write to 0777, which opens a possible security hole and that is why you shouldn’t really consider it.

The second is to simply add the user apache uses, which under Plesk is usually “apache” to the group “psacln”. You can edit the /etc/group and /etc/group- files if you know what you are doing, or use usermod.

If you want to edit the files directly, locate the line that looks like this:

psacln:x:2524:

and just tack on “apache” to the end of it like so…

psacln:x:2524:apache

Do this for both files and restart apache and you are done.

Or, simpler

/usr/sbin/usermod -a -G psacln apache

Then simply make the folders and/or files that php needs access to 0775, which makes it more secure.

You can do similar with any server enviroment, we just happen to use Plesk here.

Rob

Allowing PHP to write files in a Plesk server environment is a post from: WebSight Design, Inc. company blog. With headquarters in the San Francisco bay area, WebSight Design, Inc. has been providing world class web engineering, creative design and hosting solutions since 1995. WebSight Design