considerations when changing the PHP environment

[nitinpatel1117]

Hi, i'm not sure if i'm posting this message in the right place, but as its PHP related thought this may be the best place.

I've built a CMS using PHP that runs on windows IIS server. What I what to know is if this CMS was transferred from a windows IIS server to a UNIX server, (i.e. the hosting machine is on another server) what implications will this have in terms of the file system and the way that php is run. (basically, will it work on unix striaght away, or are there details that I have to sort out before transferring to unix)


The CMS has all the normal features of a CMS, like uploading files, images, adding/removing pages.... etc. So, my main concerns were to do with directory manipulations, and owning files and file permissions, which exist in UNX but not so much so for IIS.

This CMS was built with the help of another senior programmer, who has now left our company, leaving only myself (with a little over a years PHP knowledge) to try to sort this out.

any help on this would be must helpful. or even just a point in the right direction to any online resources/websites.

thanks.

[pbmods]

Heya, nitinpatel.

If the last guy did his job properly, you shouldn't have to change anything, or at worst, everything that you do need to change should either be in a single file somewhere or else saved in the database.

For the most part, all you should have to worry about is making sure that your PHP build includes all of the features that your script needs. That and making sure that file paths use '/' instead of '\\'.

And of course, if you run into specific problems while you're moving the site over, post back and we'll help you out.

[nitinpatel1117]

Hi pbmods,

When we were developing the CMS, portability was always taken into consideration, so i'm hoping everything does go well first time round and there aren't any changes required.

But there are some things that i am unsure of, and would like some clarification on.
This is basically on the file permissions and ownership of files.

The way that our CMS works, is it creates a new file whenever a page is created through the CMS. e.g. if a user creates a page called 'temp' in the 'about us' section, then the system (cms) will create a page called 'temp.php' in the 'about-us' directory.

It is this creation of files and sub-directories and also the removing of them (when pages/sections are deleted) that i'm worried may cause some problems.
Becuase, the system was built to run on IIS we never manipulated any file permissions anywhere in the CMS. and thus there is no coding currently in the CMS that uses chmod to change/allow permissions.


Also, all file paths are referred to with '/'. so all includes and references to directories should be ok.


thanks in advance, to anyone who can shed some more light on this topic.

[pbmods]

Heya, nitinpatel.

In that case, you shouldn't run into [m]any problems at all.

In terms of permissions, any file your CMS generates will be readable and writable by your application. You can specify a default permission setting via the umask() function.

[nitinpatel1117]

Thanks for your help,

I'll post back to this thread if i come accross any issues on this, or any changes that i had to make to get it to work,

which may be in a few weeks -:)

[pbmods]

Good luck with the transition!