Comes from New installs will default to Ember CLI builds in Production - #36 by david Hi Team, While trying setting EMBER_CLI_PROD_ASSETS to 1, I’m getting the following at the time of precompiling assets (version 2.9.0.beta2 commit: d2de058ff51f204fcf85c86a00750a59505af3bb): yarn run v1.22.17 $ …

Just for the record, and whether it is useful for somebody around. There is at least a way to make ember cli working as expected with a random uid, and it is ensuring that the assigned random uid has an entry under /etc/passwd at the time of running the rake assets:precompile operation. Something l…

Is that a production install using the install guide? Can you try a rebuild?

No success after a rebuild of the instance. I’m more looking for what is causing the uv_os_get_passwd call, or more generally about what is causing this error, does this expect any specific user in the system/setting to be set? Cheers, Ismael

How exactly are you running the Discourse image? Are there any extra flags for security? Following this trace, the problem is that the Ember-CLI build is failing, and while trying to print the error, it is throwing yet another exception and masking the real one. Can you go inside the Discourse ima…

Intersting, this is what I’m getting when executing your suggestion (and makes total sense if the intention is to access any internal library system with a random user other than root): node Welcome to Node.js v16.13.2. Type ".help" for more information. > const os = require('os'); undefined > os.u…

[imagen] trobiyo: Do you have an ETA about abandoning (if that’s the case) precompiling assets the old way? We are removing that EMBER_CLI_PROD_ASSETS in the next few weeks. [imagen] trobiyo: Is there any way to access the os machinery on a different way, or consider a different approach…

[imagen] trobiyo: Is there any way to access the os machinery on a different way, or consider a different approach, so that containerized solutions with random user id’s can still work Note that the error you are seeing is not the actual error. It’s an error that happens when trying to show …

It is exactly the same issue as in Issue with non 'username' defined · Issue #2373 · nodejs/node-gyp · GitHub and os.userInfo throws if no username in docker container · Issue #25714 · nodejs/node · GitHub By using a random user id, node complains at the time of loading os system-related utility me…

Yep, understood after the post above. Unless Team does any special action/checks to allow this, the era of using random user id’s is over imho. Cheers, Ismael

[imagen] trobiyo: Just to confirm, old way will be totally deprecated/removed, right? Yes, exactly. We’ve been slowly releasing this new asset pipeline over years, so we can track what the EmberJS project recommends and be less of a snowflake. We are in the final phase of the rollout already. …

Excellent, all clear. As usual, many thanks for your detailed info, much appreciated. Cheers, Ismael

EMBER_CLI_PROD_ASSETS a 1 bloquea la precompilación de assets

Soporte del producto

Falco (Falco) 18 Febrero, 2022 13:48 10

Sí, exactamente. Hemos estado lanzando lentamente este nuevo pipeline de assets durante años, para poder seguir lo que recomienda el proyecto EmberJS y ser menos un caso aislado. Ya estamos en la fase final del despliegue.

Tema		Respuestas	Vistas
New installs will default to Ember CLI builds in Production Announcements ember	36	4374	17 Junio 2022
Excessive consumption of memory due to precompiling assets Product Support unsupported-install	11	403	5 Mayo 2026
Clean install of discourse resulting in failure Self-hosting	8	565	23 Febrero 2024
New Install Bootstrap Fail in 'bundle exec rake themes:update assets:precompile' Self-hosting	7	596	21 Febrero 2024
Discourse Assets Missing Self-hosting unsupported-install	17	2473	22 Febrero 2020

EMBER_CLI_PROD_ASSETS a 1 bloquea la precompilación de assets

Temas relacionados