migrating a Unix PHP site to Windows
migrating a Unix PHP site to Windows
am 12.07.2007 06:00:02 von mrecomm101
I copied a PHP site from a Unix server over to a Windows 2003 Server. I
installed PHP5.3 on the Windows Server. When I try to run the site as is, I
get "no input file specified". Will I ever be able to get this site to work?
Any thoughts or suggestions?
Thanks!
Re: migrating a Unix PHP site to Windows
am 12.07.2007 08:15:02 von Steve Schofield
Here is a couple links
http://www.peterguy.com/php/install_IIS6.html
http://www.php.net/install.windows
You could also look at putting FastCGI on your server.
http://www.iis.net/default.aspx?tabid=2&subtabid=25&i=1345
--
Best regards,
Steve Schofield
Windows Server MVP - IIS
http://weblogs.asp.net/steveschofield
"mrecomm101" wrote in message
news:8FA8EE8B-E8AA-4DB4-8BBB-242502DDD861@microsoft.com...
>I copied a PHP site from a Unix server over to a Windows 2003 Server. I
> installed PHP5.3 on the Windows Server. When I try to run the site as is,
> I
> get "no input file specified". Will I ever be able to get this site to
> work?
> Any thoughts or suggestions?
>
> Thanks!
Re: migrating a Unix PHP site to Windows
am 12.07.2007 10:57:16 von David Wang
On Jul 11, 9:00 pm, mrecomm101
wrote:
> I copied a PHP site from a Unix server over to a Windows 2003 Server. I
> installed PHP5.3 on the Windows Server. When I try to run the site as is, I
> get "no input file specified". Will I ever be able to get this site to work?
> Any thoughts or suggestions?
>
> Thanks!
Depends on how well the PHP site is written.
PHP runs well on IIS. Ability to move sites between OSes usually
depends on how well the PHP application is written and how platform
agnostic it is.
Right now, it sounds like the PHP application is making some
assumption about filepath. perhaps it is hardcoded to use "/" instead
of "\" as path specifier. Or it is hardcoded to look at certain paths
or different default directory. It completely depends on how well the
application is written. If the application is supported on Windows,
you can get the support personel to tell you what is wrong. If it is
not supported on Windows -- then you will have to debug the
application to figure out why.
If the application is not well written, then you will never get it to
run on Windows and it will lock you into an OS/platform, despite PHP's
claim of being cross-platform. Always be weary of such promises
because it comes with big hidden asterisks.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//
Re: migrating a Unix PHP site to Windows
am 15.07.2007 07:12:01 von mrecomm101
I'm still not having any luck getting anything to work and have tried on
abother server as well. Is the FASTCGI in place of or in addition to?
"Steve Schofield" wrote:
> Here is a couple links
> http://www.peterguy.com/php/install_IIS6.html
> http://www.php.net/install.windows
>
> You could also look at putting FastCGI on your server.
> http://www.iis.net/default.aspx?tabid=2&subtabid=25&i=1345
> --
>
> Best regards,
>
> Steve Schofield
> Windows Server MVP - IIS
> http://weblogs.asp.net/steveschofield
>
>
> "mrecomm101" wrote in message
> news:8FA8EE8B-E8AA-4DB4-8BBB-242502DDD861@microsoft.com...
> >I copied a PHP site from a Unix server over to a Windows 2003 Server. I
> > installed PHP5.3 on the Windows Server. When I try to run the site as is,
> > I
> > get "no input file specified". Will I ever be able to get this site to
> > work?
> > Any thoughts or suggestions?
> >
> > Thanks!
>
>
Re: migrating a Unix PHP site to Windows
am 16.07.2007 14:11:58 von David Wang
FastCGI is something else altogether.
It is a process model for PHP and should not be a cause for PHP to
logically malfunction nor be a "requirement".
You are going to have to verify from the website's developer/support
personel that the website is even correctly written to run on PHP
across platform. If you cannot get that verification, it is quite
pointless to try any migration unless you can personally handle the
details of the migration.
Remember, even if we managed to "support" you to make the migration
work, you still end up owning the "support" of the migrated website in
the future -- so, unless you can handle the details of the migration
or get the website developer to provide support, it is not feasible.
This is why I say that open source and cross platform are no assurance
against lock-in. Your website is an example.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//
On Jul 14, 10:12 pm, mrecomm101
wrote:
> I'm still not having any luck getting anything to work and have tried on
> abother server as well. Is the FASTCGI in place of or in addition to?
>
>
>
> "Steve Schofield" wrote:
> > Here is a couple links
> >http://www.peterguy.com/php/install_IIS6.html
> >http://www.php.net/install.windows
>
> > You could also look at putting FastCGI on your server.
> >http://www.iis.net/default.aspx?tabid=2&subtabid=25&i=1345
> > --
>
> > Best regards,
>
> > Steve Schofield
> > Windows Server MVP - IIS
> >http://weblogs.asp.net/steveschofield
>
> > "mrecomm101" wrote in message
> >news:8FA8EE8B-E8AA-4DB4-8BBB-242502DDD861@microsoft.com...
> > >I copied a PHP site from a Unix server over to a Windows 2003 Server. I
> > > installed PHP5.3 on the Windows Server. When I try to run the site as is,
> > > I
> > > get "no input file specified". Will I ever be able to get this site to
> > > work?
> > > Any thoughts or suggestions?
>
> > > Thanks!- Hide quoted text -
>
> - Show quoted text -