How can it be so difficult to get started with Starter Kits?!?

@jlrdw Cheers for the reply ... Forget about the php stuff - I'm more after a reason/solution as to why, despite having laravel installer, running laravel new my-app comes up with command not found!?!

And BTW - I was doing html/js/php etc. using Notepad!! Yes - hard core coding in those days!! lol

@TrickyDicky have you ran:

composer selfupdate

Also clear composers cache. And do you have the required php version that laravel requires?

I also use netbeans. But for python I use VS. But VS is good for laravel specific intellisense. Not needed if you know what you're doing.

I like netbeans for some smaller jakarta ee apps.

Edit:

You could uninstall composer and install again and tell it where php is located.

Also linux is a steep learning curve, takes a while to get used to it. I would stay away from it, I messed with it for a year, but no good security. Enterprise linux servers has the good security. Desktop is clamav.

Years ago linux was fine, but attackers is now even getting through linux more and more. It's not as secure any longer unless a enterprise server.

For a hobby and playing is one thing, but I don't trust it.

@TrickyDicky Which starter kit?

@jlrdw I can't remember now :-( There's so much "stuff" tagged on to them ... React, Vue, Limevire, Vite ... then the plethora of other options from the CLI.

Just scrolling thru Netbeans terminal window ... that's another hour of therapy I'll need :-(

@TrickyDicky I suggest just install laravel first. You probably don't need a starter kit. If on Linux I suggest use Nginx for the server.

@jlrdw Cheers for the suggestions, but I've already got Apache2 running, can easily (now I've worked it out!!!) set up virtual hosts (literally just done another one 5 mins ago for what I was hoping would be another starter kit - just to play with and find out about!!) but once again I'm presented with the baffling Laravel Installer is installed, yet in terminal ... "laravel: command not found"

I'm almost pulling my hair out!!!

@TrickyDicky just install laravel with composer.

@jlrdw Umm. Several times!!! As if it would make any difference :-/

"/usr/bin/php" "/usr/local/bin/composer" "--ansi" "--no-interaction" "require" "laravel/laravel:* v12.0.3" ./composer.json has been updated Running composer update laravel/laravel Loading composer repositories with package information Updating dependencies Nothing to modify in lock file Writing lock file Installing dependencies from lock file (including require-dev) Nothing to install, update or remove Generating autoload files 52 packages you are using are looking for funding. Use the composer fund command to find out more! Done. No security vulnerability advisories found.

@jlrdw I'm sure you're getting thoroughly bored by now ... Sorry :-) but I've been trawling thru my .bash history (Oh What Joy!!!) and recognised one line from earlier today ;

export PATH="$PATH:$HOME/.config/composer/vendor/bin"

Guess what!?! It worked. Eventually. I couldn't use the directory I'd already created as a virtual host :-( but no biggie.

Documentation on the install process is wrong! It said somewhere you coud choose the dbase ... but it always defaults to sqlite, so I get a "WARN: Could not find driver" blah blah blah.

And also "1 high severity vulnerability" which it says run "npm audit fix".

Texas!! It's still daylight where you are then!?! I'm in north Wales, UK - 2.10am here now :-(

Anyway, thank you for putting up with me ranting!! Cheers ;-)