Re: issues upgradubg laravel/php apps.

Hi All...

Update on my testing of the github process..

It actually appears that laravel packages can change over time, in terms of
function, as well as even being abandoned, or having the function absorbed
in other packages. Ok, if you're immersed within laravel, you develop an
understanding of these nuances. If, on the other hand, you are "new", or
trying to test, you can wind up going down a bunch of rabbit holes trying
to get to a reasonable end point. The primary issue, while the 'net, is
full of stuff, there's no place where one can be guaranteed of the
"right/best" answers with a knowledge that you can feel is valid. In other
words, lots of knowledge, but how does one know it's any good!

That said, I decided to create new test app/shell, get it to "compose
install" with no errs, and then back fill the items from my test github
app. I followed this process, and came up with upgraded/versions of some
apps, and a few that appeared to "no longer be needed". So the process then
proceeded to the post autoload/dump testing (i guess). Which is where I
find myself now.

        "post-autoload-dump": [
            "Illuminate\\Foundation\\ComposerScripts::postAutoloadDump",
            "@php artisan package:discover --ansi"
         (this one works from the new base laravel12 project

        "post-autoload-dump": [
            "Illuminate\\Foundation\\ComposerScripts::postAutoloadDump",
            "@php artisan package:discover"
        (this is the one from the orig github app...  it seems to err out..)

 Right now, I have 0 clue or pointers to how this process gets setup, or
works, or what it does..or why?

thoughts/pointers...

thanks


On Fri, Apr 25, 2025 at 8:32 AM bruce <[email protected]> wrote:

> hi..
>
> to begin.. this might be "toppost".. using gmail.. can't yet figure out
> how to "insert" my reply within the body!
>
> that said..
>
> After rethinking a bit on what Ashley had mentioned, I've found a few
> random repos/apps with laravel 12/php 8.3. my goal to be able to get them
> to "install" -- composer install with no errs..
>
> This would give me a "starting basis" (hopefully), and I can build from
> there, adding additional packages that I have in my "test" apps..
>
> This might/should help to narrow down potential issues..
>
> Keep in mind, my only reason for doing this.. to be able to actually
> build/run/view potential apps that have items that I can copy/use in my
> actual test project that I want to create..
>
> If i get to this point, I'd actually have something I could then discuss
> with devs to refactor/make better for the initial testing..
>
> thoughts!
>
>
> On Thu, Apr 24, 2025 at 4:34 PM bruce <[email protected]> wrote:
>
>> Hi,
>>
>> Looking to do a local install of different php/laravel apps, and find a
>> number of the apps are old, and have issues with m teste server.
>>
>> Running ubuntu 22 with php 8.3.
>>
>> The issue seems to occur with incompatibilities beyeen the "old" packages
>> in the app (composer.json) files.
>>
>> So, I'm looking to talk to anyone that might have insight ijnto steps to
>> resolve this issue in the apps.
>>
>> I've left msgs to the issue forums, as well as emails to the authors were
>> possible.
>>
>> the test server.. standard digital ocean, ubuntu, etc..
>>
>> thanks
>>
>>