Skip to content

Is there a way I can just build for production without using gh-pages? #564

Closed

Description

@NullVoxPopuli

I want to upload my minified project to a different hosting service, like s3. :-\

Activity

  1. filipesilva commented on Apr 29, 2016

    @filipesilva
    Contributor

    There is, yes! You can just do ng build -prod, and the dist/ folder will contain a self sufficient production ready project.

    You can then deploy the contents of that folder to wherever you choose.

  2. NullVoxPopuli commented on Apr 29, 2016

    @NullVoxPopuli
    Author

    Ah ha! I tried production instead of -prod. Thanks!

  3. filipesilva commented on Apr 29, 2016

    @filipesilva
    Contributor

    Yeah that happened to me a couple of times as well. Not really sure why those aren't alias really, it's something carried over from ember-cli.

  4. etkirsch commented on Apr 29, 2016

    @etkirsch

    Nice, this helps me too. Thanks!

  5. NullVoxPopuli commented on Apr 29, 2016

    @NullVoxPopuli
    Author

    ok, so -- I just tried it, and there are still all of the files (js, html, e2e, etc per component). Shouldn't there be just:

    • index.html
    • appName.js
    • appName.css
    • vendor.js
    • vendor.css
      ?
  6. filipesilva commented on Apr 29, 2016

    @filipesilva
    Contributor

    At the moment, bundling isn't in yet. It's soon to be merged though: #549

    The files should be uglified though, and the config used is the production one (eg no Angular 2 is running in the development mode. Call enableProdMode() to enable the production mode. message).

  7. NullVoxPopuli commented on Apr 29, 2016

    @NullVoxPopuli
    Author

    cool, thanks for the link to that!

  8. added a commit that references this issue on May 31, 2016
  9. angular-automatic-lock-bot commented on Sep 5, 2019

    @angular-automatic-lock-bot

    This issue has been automatically locked due to inactivity.
    Please file a new issue if you are encountering a similar or related problem.

    Read more about our automatic conversation locking policy.

    This action has been performed automatically by a bot.

  10. locked and limited conversation to collaborators on Sep 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions