8
You can create a script to use the craft executable to sync your project config file
./craft project-config/sync
5
System Settings don't support rebranding via Project Sync, however if you place your assets in the following locations and commit to GIT you can get similar results.
Login Page Logo -> <project_root>/storage/rebrand/logo/<filename>.svg
Site Icon -> <project_root>/storage/rebrand/icon/<filename>.svg
By placing the images in the ...
2
The best I could find was searching thru a plugin's changelog in the Craft Plugin Store for something like "Added support for Craft 3.1 project config."
Super Table version 2.1.1:
Added support for Craft 3.1 project config.
Redactor version 2.2.0:
Redactor for Craft CMS now requires Craft 3.1.
Improved Project Config compatibility.
2
According to P&T this is expected behavior. Their solution is to put this in config/app.php:
'components' => [
'projectConfig' => function() {
$config = craft\helpers\App::projectConfigConfig();
$config['readOnly'] = false;
return Craft::createObject($config);
},
],
(Thanks Oli, Brandon, Andris!)
Since I do all ...
2
I'm not familiar with this plugin, but could probably do this in your template where the plugin is called:
// Get the environment
{% set env = getenv('ENVIRONMENT') %}
// If anything but dev, then load the plugin
{% if env != 'dev' %}
{% include ['_recaptcha/frontend'] %}
{% endif %}
You can also get the environment from the config:
{% set env = ...
2
No, you would not check these files into Git.
I have a .gitignore rule to just ignore everything in storage/ and so I treat it as a cache directory.
Which it is... except for the unfortunate fact that any rebrand (logo, icon) files are stored in storage/ as well. But I just manually add them in via git add -f
2
Based on your comment that you get an error saying Craft is not installed, to me that suggests the bash script does not have access to your environment variables, (this can also be a problem when running cron jobs).
To remedy this, create an env text file to export all the same values as those in your production env variables. For this example name it ...
2
I have just setup a Craft 3 boilerplate and got it working great. So yeah... this does work.
1
Even if useProjectConfig was set to false, it's not a good idea to update Craft on a live site because, as you've discovered, errors sometimes happen.
There's even an allowUpdates config setting that we recommend people setting to false on the live site just so someone doesn't accidentally update Craft from the control panel.
The safer workflow is to have ...
1
I think P&T changed the behavior in Craft 3.1.0 and newer. Before 3.1.0 it was necessary to have 'allowAdminChanges' => true with updates in/to project config.
To be 100% safe you can always enable admin changes when you're on the command line by using this config line in production environments:
'allowAdminChanges' => (php_sapi_name() === 'cli'),...
1
solved it with a rebuilded project file locally.
1
As far as I know the craft_info table should only have one row.
This would mean that either:
You have something installed / configured wrongly somewhere causing it to insert a 2nd row into the table
Or it's actually a craft bug, I'd advise you to search through The CraftCMS Github Issues and check if there's any issue resembling yours, if not create an ...
1
If I create a folder assets at that location it works. I don't know what this asset folder is about.
1
You can rebuild your project.yaml by running ./craft project-config/rebuild.
In terms of workflow here's a good article that discusses it.
1
P&T recently released an update with a new console command:
project-config/rebuild
This does exactly what it sounds like, it rebuilds the config ...
Only top voted, non community-wiki answers of a minimum length are eligible
