Ember CLI - How do I use it in discourse?

Development

AI-generated summary

The discussion revolves around using Ember CLI with Discourse. Initially, drew0101 encountered issues running Ember commands, but sam clarified that Ember CLI is not used for developing Discourse, and instead, Rails should be configured.

drew0101 asked if there was a downside to configuring Rails to use Ember-CLI, to which sam replied that it would be a massive change due to Discourse’s custom asset pipeline.

spirobel inquired about the documentation for the asset pipeline to use Ember code in a plugin. The documentation’s location remains unclear, as andersonmmi also asked for it.

However, codinghorror mentioned that eviltrout is working on getting Discourse up to date with Ember CLI, a challenging task due to the age of the Ember application and the large number of plugins and themes that need to be considered.

1

Hello,

I am about to start hacking away at discourse, but I am confused how ember is used. Running commands such as ‘ember version’ or ‘ember g ’ give the error ‘ember: No such file or directory’. Do I need to install the ember cli separately?

2

We do not use Ember CLI to develop Discourse. You need to configure Rails and run it. To make life easier use our docker dev environment. https://github.com/discourse/discourse/tree/master/bin/docker

3

Is there a downside to configuring Rails to use Ember-CLI?

4

This would be a GIANT Ginormous change. We have a very custom asset pipeline.

5

Le pipeline d’actifs est-il documenté quelque part ? J’aimerais utiliser un code Ember comme celui-ci, par exemple dans un plugin :

Comment procéder ? Dois-je copier le code manuellement ?

6

Avez-vous déjà trouvé la documentation du pipeline d’actifs ?

7

Wow, ce sujet est ancien, mais @eviltrout travaille depuis plusieurs mois à nous faire passer à Ember CLI — c’est un gros travail !

8

Oui, notre application Ember est assez ancienne à ce stade, et nous n’avons pas encore totalement abandonné certaines de nos vieilles habitudes. De plus, la mise à niveau est plus lente car nous avons des centaines de plugins et de thèmes que nous ne souhaitons pas casser dans le processus.

Néanmoins, je m’attends à faire de bons progrès bientôt !