I dont think that any framework will be better from another for what you want to do.

I feel that the difficulty level of this depends greatly from the way your code is written.

Moreover is very difficult based on the fact that you dont want downtime. From my very little experience i think that this is nearly impossible to do.

Why dont you cutoff development on your current code (no new features etc etc only serious stop-issues fixing) and move on to port your code to laravel?

I understand. However, I'm searching for ways of making transparent the migration for pieces of code already ported to Laravel, while mantaining functional older plain PHP code.

For example, Laravel "overwrites" superglobals ($_GET, $_POST, etc.) using classes and methods, (ex. Input::get()). My PHP project of course make direct use of superglobals. How can I "make it go" under Laravel without having to rewrite instantly all my PHP code?

In short, you can't.

Why you want to migrate your project to laravel? Does it have a more pro's then cons?

Laravel is just a php framework, just like your "plain" project.

When you like to migate, it would be a big job, but in the future you can build on it.

Thanks citricsquid, I've already implemented a solution similar to your custom route: in the near future I'll know if this may be a good compromise between "using a framework" and "rewriting everything from the ground up" or not. The only problem is that routing DOES NOT work for index.php pages, for example this code:

Route::get('legacy/index.php',function(){
    return "This is index";
});

won't be executed as expected when visiting that page. Why this? Is there a solution?

het86 said:

Thanks citricsquid, I've already implemented a solution similar to your custom route: in the near future I'll know if this may be a good compromise between "using a framework" and "rewriting everything from the ground up" or not. The only problem is that routing DOES NOT work for index.php pages, for example this code:

Route::get('legacy/index.php',function(){ return "This is index"; });

won't be executed as expected when visiting that page. Why this? Is there a solution?

I'd guess that calling anything that ends with index.php is automatically rewritten to go to Laravel's index.php by apache, so from the perspective of the framework, anything that ends with "index.php" just gets treated as if they were the "/" url.

You might want to try using Route::get('legacy/', function() { }); and seeing if that works.

That doesn't work, sorry. I think this could be considered a bug (not expected behaviour) of Laravel 4.x.

thepsion5 said:

het86 said:

Thanks citricsquid, I've already implemented a solution similar to your custom route: in the near future I'll know if this may be a good compromise between "using a framework" and "rewriting everything from the ground up" or not. The only problem is that routing DOES NOT work for index.php pages, for example this code:

Route::get('legacy/index.php',function(){ return "This is index"; });

won't be executed as expected when visiting that page. Why this? Is there a solution?

I'd guess that calling anything that ends with index.php is automatically rewritten to go to Laravel's index.php by apache, so from the perspective of the framework, anything that ends with "index.php" just gets treated as if they were the "/" url.

You might want to try using Route::get('legacy/', function() { }); and seeing if that works.

het86 said:

That doesn't work, sorry. I think this could be considered a bug (not expected behaviour) of Laravel 4.x.

thepsion5 said:

het86 said:

Thanks citricsquid, I've already implemented a solution similar to your custom route: in the near future I'll know if this may be a good compromise between "using a framework" and "rewriting everything from the ground up" or not. The only problem is that routing DOES NOT work for index.php pages, for example this code:

Route::get('legacy/index.php',function(){ return "This is index"; });

won't be executed as expected when visiting that page. Why this? Is there a solution?

I'd guess that calling anything that ends with index.php is automatically rewritten to go to Laravel's index.php by apache, so from the perspective of the framework, anything that ends with "index.php" just gets treated as if they were the "/" url.

You might want to try using Route::get('legacy/', function() { }); and seeing if that works.

Hm, I just tried a fresh laravel install with the following route:

Route::get('foo/bar/index.php', function(){
   return 'hit foo/bar/index.php';
});

And hitting that url worked as intended. I wonder if it might be your apache or .htaccess that's preventing that from functioning in your case.

For anyone interested in, I think I will slowly refactor my project taking inspiration from some aspects of laravel's design. Trying to switch an already working piece of software on an existing framework platform is probably the wrong approach to the problem. Thanks anyway.

if you using nginx server

you should add

        try_files $uri = 404;

for your nginx config

404 will trigger laravel to catch xxx.php from route

nginx conf example:

server {
    listen 80;
    server_name dev.com.tw;
    set $root /home/vagrant/Code/dev.com.tw/public;
    root $root;

    index index.html index.htm index.php;

    charset utf-8;

    location / {
        try_files $uri $uri/ /index.php?$query_string;
    }


    location = /favicon.ico { access_log off; log_not_found off; }
    location = /robots.txt  { access_log off; log_not_found off; }

    access_log off;
    error_log  /var/log/nginx/dev.com.tw-error.log error;

    error_page 404 /index.php;

    sendfile off;

    location ~ \.php$ {
        try_files $uri = 404;
        fastcgi_split_path_info ^(.+\.php)(/.+)$;
        fastcgi_pass unix:/var/run/php5-fpm.sock;
        fastcgi_index index.php;
        include fastcgi_params;
    }

    location ~ /\. {
        deny all;
    }
}