[image] Upgrade from 3.2.0.beta3-dev to 3.2.0.beta3 failed due to out of memory $ /var/www/discourse/app/assets/javascripts/node_modules/.bin/ember build Environment: development BTW honest question - what is the idea behind not running ember in production mode with -prod ?

We use the EMBER_ENV environment variable instead of the -prod flag. The result should be the same. I certainly see a production build running here on Meta and other sites. I’m not sure what’s printing Environment: development to the build log… we should investigate :eyes: lib/tasks/assets…

I’m also showing environment development when upgrading discourse.

Rebuild is showing "Environment: development" during ember-cli build

Support Self-hosting

david (David Taylor) March 25, 2024, 4:38pm 5

It shouldn’t make any functional difference… but here’s a PR to use -prod and therefore fix up the logging:

https://github.com/discourse/discourse/pull/26344

Topic		Replies	Views
New installs will default to Ember CLI builds in Production Announcements ember	36	3655	June 17, 2022
Ember in debug mode at production Development	3	1840	May 17, 2016
Upgrade from 3.2.0.beta3-dev to 3.2.0.beta3 failed due to out of memory Self-hosting server-resources	20	1584	March 7, 2024
Meta is running our Ember CLI build Development ember	1	728	August 9, 2021
Problem running bin/ember-cli Development	6	596	January 20, 2023

Rebuild is showing "Environment: development" during ember-cli build

Related topics