I am looking for some guidance with migrating 30+ websites I have written in CI 2.1.x. These sites use HMVC, Sparks and a custom developed CMS Library that is rather complex.
I have spent a few hours running through the instructions for migrating provided by CI, however I am unable to get anything to work properly with HMVC or Sparks. From what I can tell Sparks is not supported anymore and it's recommended to use Composer, however this is not really an option when these libraries are not maintained anymore and may not be available through composer with any instructions on how to install via composer.
Luckily I am only using a few sparks..
https://github.com/philsturgeon/codeigniter-template
https://github.com/darkhouse/codeigniter-message
I am contemplating even bothering with this migration, from what I can tell after CI 3.x the move to CI 4 will be a complete re-write regardless, and from the looks of it even if I am able to the HMVC working with my apps (which has been a nightmare thus far) I am still left without a solution to sparks without needing to re-write all of the code I am using for the template engine and just using something like the blade templating engine.
Does anyone have any advice on this scenario I am in? I am considering just re-doing these applications in Laravel as it appears like I am going to have to re-write a large chunk of my code anyways. Even after I upgrade i am going to be left with a framework that is essentially still dead because no one is actively coding websites in 2018 with CI. However I am worried in doing so I will be left with a much bigger task with re-writing these apps in Laravel as opposed to battling through and trying to get something working with the newest CI version & all of the custom stuff insides my apps.
I have spent a few hours running through the instructions for migrating provided by CI, however I am unable to get anything to work properly with HMVC or Sparks. From what I can tell Sparks is not supported anymore and it's recommended to use Composer, however this is not really an option when these libraries are not maintained anymore and may not be available through composer with any instructions on how to install via composer.
Luckily I am only using a few sparks..
https://github.com/philsturgeon/codeigniter-template
https://github.com/darkhouse/codeigniter-message
I am contemplating even bothering with this migration, from what I can tell after CI 3.x the move to CI 4 will be a complete re-write regardless, and from the looks of it even if I am able to the HMVC working with my apps (which has been a nightmare thus far) I am still left without a solution to sparks without needing to re-write all of the code I am using for the template engine and just using something like the blade templating engine.
Does anyone have any advice on this scenario I am in? I am considering just re-doing these applications in Laravel as it appears like I am going to have to re-write a large chunk of my code anyways. Even after I upgrade i am going to be left with a framework that is essentially still dead because no one is actively coding websites in 2018 with CI. However I am worried in doing so I will be left with a much bigger task with re-writing these apps in Laravel as opposed to battling through and trying to get something working with the newest CI version & all of the custom stuff insides my apps.