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

Is this asset pipeline documented some where? I would like to use an ember code like this for example in a plugin:
https://github.com/shipshapecode/ember-flatpickr
How would I go about that? do I have to manually copy the code?

6

Did you ever find the asset pipeline documentation?

7

Wow this topic is old, but @eviltrout is working on getting us up on Ember CLI over the last few months – it’s a big job!

8

Yup, our Ember application is quite old at this point, and we haven’t fully gotten away from some of our old habits. It’s also slower to upgrade because we have hundreds of plugins and themes that we don’t want to break in the process.

Still, I expect to make some good progress soon!