Statamic 3 - the flat-first, Laravel + Git powered CMS designed for building beautiful, easy to manage websites

This pull request includes the changes for upgrading to Laravel 9.x. Feel free to commit any additional changes to the shift-55082 branch.

Before merging, you need to:

• Checkout the shift-55082 branch
• Review all pull request comments for additional changes
• Run composer update (if the scripts fail, add --no-scripts)
• Clear any config, route, or view cache
• Thoroughly test your application (no tests?, no CI?)

If you need help with your upgrade, check out the Human Shifts. You may also join the Shifty Coders Slack workspace to level-up your Laravel skills.

This pull request includes the changes for upgrading to Laravel 9.x. Feel free to commit any additional changes to the shift-55082 branch.

Before merging, you need to:

• Checkout the shift-55082 branch
• Review all pull request comments for additional changes
• Run composer update (if the scripts fail, add --no-scripts)
• Clear any config, route, or view cache
• Thoroughly test your application (no tests?, no CI?)

If you need help with your upgrade, check out the Human Shifts. You may also join the Shifty Coders Slack workspace to level-up your Laravel skills.

This pull request includes the changes for upgrading to Laravel 8.x. Feel free to commit any additional changes to the shift-55057 branch.

Before merging, you need to:

• Checkout the shift-55057 branch
• Review all pull request comments for additional changes
• Run composer update (if the scripts fail, add --no-scripts)
• Clear any config, route, or view cache
• Thoroughly test your application (no tests?, no CI?)

If you need help with your upgrade, check out the Human Shifts. You may also join the Shifty Coders Slack workspace to level-up your Laravel skills.

Statamic doesn't use a database by default, if you use queues but have no database, Laravel tries to put those failed jobs inside a database that doesn't exist.

Hi all,

I think it would be nice to ignore the .idea folder.

Reason: As a developer who uses PHPStorm, I always find myself adding it when starting a blank project.

I would assume that most Statamic projects won't use a DB, as this is a main feature of Statamic.

This is why I suggest, to remove those from the Statamic default .env.example file.

I'm kind of still new to composer and stuff. I always start new sites from statamic/statamic and everytime I updated via cli I got this message saying "Package fzaninotto/faker is abandoned, you should avoid using it. No replacement was suggested."

I wondered if it was an issue. I learned that it really isn't but then I wondered how I could get rid of that message. Turns out Taylor and others are maintaining a new version: https://github.com/fakerphp/faker and https://laravel-news.com/changes-coming-to-php-faker

So I updated the composer.json to use this new forked version and "abandoned notification" went away while updating. I think this will help rookies that worry way too much when they see stuff like this.

The Laravel skeleton has received some changes since 9.0 release that are not yet present in this repo.

Same deal as #39, just updating some files to match a new Laravel install. It just feels better to know that everything's in sync, you know? You know.

NOTE! The config/ignition.php contains a lot of changes. This is because the old one was still using stuff from the Facade package, which changed to Spatie with Laravel 9.

Consider looking into how to best handle that file, the others should be fine with only small changes.

I took the latest Laravel Skeleton v8.6.9 (laravel/laravel) and applied it to this repo and went through the diffs. Looks like a lot of changes, but a good chunk are just docblocks and type hints.

Let me know if I can break it down better.

This is quite a personal feeling, so feel free to reject it 🙃

Personally, I would suggest moving the license key and revision to the top. Those will be needed in much more cases for a common Statamic project then the pusher, AWS and redis settings.