1

I would like to deploy an app to Parse.com Hosting which uses the public folder to serve a website, and therefore I would like to make my dist folder the public folder, and rename the public folder.

However, Ember-CLI requires putting assets in that folder, and I cannot figure out how or if this can be changed?

blisstdev
  • 633
  • 4
  • 13
  • Why do you care what the name of the folder is? Copy what you need to the public folder on your hosting – Patsy Issa Feb 17 '15 at 15:00
  • possible duplicate of [Ember-cli moving files to an external folder](http://stackoverflow.com/questions/28363120/ember-cli-moving-files-to-an-external-folder) – Patsy Issa Feb 17 '15 at 15:01
  • I guess I can make a Git submodule or some symlinks or something but I'd like to have just one folder of files and not have to do manual copying everytime I want to deploy the code. This is also not a duplicate so please remove that status. They are two different ideas. The "duplicate" answer addresses where ember-cli puts files on build. My question is about specifying a different folder for where ember-cli looks for public assets. – blisstdev Feb 17 '15 at 17:40
  • 1
    When you deploy you don't need to copy your entire ember app, all you need is the contents of dist – Patsy Issa Feb 17 '15 at 17:44
  • Which is exactly why I want want to change the name of my dist/ folder to public/, as I said in the question. I would like to version control my whole Ember app as well as the required Parse.com folder structure (config/,cloud/,public/) and am simply wondering if there is a way to change what folder is used for public assets in ember-cli. Appreciate your help thus far though – blisstdev Feb 17 '15 at 17:51

2 Answers2

1

The answer is essentially "changing the public assets folder is within Ember-CLI's internals and you don't really need to change it anyway, so just set something else up."

Per @Basement Keyboard Hero's suggestion I just made another folder ember-app/parse/public, which I made my output path:

ember build --environment production --output-path parse/public

blisstdev
  • 633
  • 4
  • 13
-1

You only need to copy the contents of dist/ folder to your hosting, so you won't have to worry about output paths too much. Just upload the local dist directory contents under the remote public directory, and that should do it.

The whole ember-cli structure is only used in development. The build process takes care of compiling all your dependencies in the vendor.js file, plus the custom yourappname.js file. Also true for stylesheets. So dist is your compiled, production-ready app, containing everything you need.

Anything keeping you from trying/using this method?

Victor Nițu
  • 1,485
  • 13
  • 18