No, it doesn't match anything on the list:
After filing this request, the documentation has been improved to more clearly state that this is, in fact, an exhaustive list.
I have update the screenshot above accordingly.
You should have a look into project config if you haven't already.
It allows you to sync just the structural changes of your development, staging and live sites, without affecting the content/users.
This way you can still sync your production database to staging, but then you can just sync the structural changes back to production – no freezing necessary.
I believe you need to use tweak the config/general.php file in order to have a baseUrl for a site that is a different domain name.
'siteUrl' => [
'english' => 'https://www.mysite.com/',
'japanese' => 'https://www. myjapanesesite.com/',
See documentation at: https://docs.craftcms.com/api/v3/craft-config-generalconfig.html#siteurl
I know this is an old question, but just an update:
If you're on Craft CMS v3+, craft.config.[setting-name] has been deprecated.
Use craft.app.config.general.[setting-name] instead.
So if you wanted to check if you were in dev environment, you'd do craft.app.config.general.devMode, this returns a boolean value.
"After pushing the exec widget all the codebase changes, fields, sections are moved to the Staging environment."
You skipped a step...
Assuming you are properly using Project Config, you'll want to run craft up after deploying your files.
The error you're seeing is probably caused by this:
./.env.sh: line 128: $'\r': command not found
This error indicates that your OS doesn't recognise the line endings in this file. This means the file isn't parsed correctly, which in turn means your environment variables are wrong (for example, the GLOBAL_DB_DRIVER might include a control character at the ...
I manage to fix the issue after numerous of research, for those who are interested, here is the solution,
Check output of docker ps command and look for running mysql
containers. If you find one then use mysql command like this: mysql -h
127.0.0.1 -P <mysql_port> (you will find port in docker ps output). If you can't find any running mysql container ...
Your production website shouldn't have been complaining about a different website using the same license key, as long as the license key is bound to the production websites domain name...
To get rid of the error, you can clear your Data caches. You can do this by navigating to Utilities > Caches in your Control Panel, and there you can unselect all but ...