1

Morning folks. First time doing multi-environment in Craft 3, and separate installations for staging and production is a bit overkill for this particular project. Instead I just want to show a few new bits in templates on the staging subdomain until sign-off.

Staging domain (https://staging.adddress.com) is pointed at the production 'public' directory. So in Craft 2, I'd just let the 'staging' key in my config.php set all the necessary environment variables. But in Craft 3 don't I need to load the correct .env first? Since it's all the same installation, is there a way to switch to .env.staging when on the staging subdomain? Is that the correct/best approach? Thanks.

Improve this question

1 Answer 1

Reset to default
1

Alright, so turns out all I need to do is comment out the following line in index.php:

define('CRAFT_ENVIRONMENT', getenv('ENVIRONMENT') ?: 'production');

Now I can use config.php keys, same way I did in Craft 2. For example:

'*' => [ // My default/production variables 'devMode' => false, etc... ], // Local 'address.test' => [ // Local variables 'devMode' => true, etc... ] // Staging 'staging.address.com' => [ // Staging variables 'devMode' => true, etc... ]

Thanks to Luke James for the assist on Slack.

Improve this answer

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.