As of Craft 3.5, the useProjectConfig
setting is deprecated, and Craft ignores the setting.
That makes updating to 3.5 a great time to start using Project Config using the steps below.
<aside> 💡 These are the notes I use for my own projects, and may not be 100% accurate for yours.
</aside>
scripts/pull_db.sh
scripts/backup_db.sh
"craftcms/cms": "^3.5.0",
composer update
rm -rf vendor
then composer update
again. This will create a composer.lock file that's compatible with both Composer 1 and 2.$APP_ID
with ./craft setup/app-id
. See Cache Configuration..env
as $ENVIRONMENT_VARIABLES.env
variables you created.env
file on staging and production with the new email settings and generate a unique APP_ID
for each environment"config/project": true,
to .vscode/settings.json
to remove the Project Config files from your Visual Studio Code project"useProjectConfig" => false
from config/general.php
if it's in thereconfig/general.php
, add use craft\\helpers\\App;
above return [
, then change getenv('SECURITY_KEY')
to App::env('SECURITY_KEY')
(or update your general.php file to match the new things added in the latest default Craft install)config/general.php
, add this to the staging and production environment settings: 'allowAdminChanges' => false,
storage/rebrand
from .gitignore
so that it deploys the site login logo and icon with git add storage/rebrand -f