Skip to content

angular-cli deploy to ftp with assets #2589

Closed

Description

@dolanmiu

Hi, very simple question here,

I would like to deploy my app via FTP. Which folders do I need to upload after it is built to dist?

I cannot upload just the dist folder because it does not contain my assets.

Do I need to upload my dist AND my src folder? The src folder contains the assets folder

It seems redundant if I have to upload my dist and the source JS files no?

Activity

  1. deebloo commented on Oct 8, 2016

    @deebloo
    Contributor

    @dolanmiu everything you need should be in the dist folder. your assets should also be copied over based on the assets directory you define in your angular-cli.json file

  2. dolanmiu commented on Oct 8, 2016

    @dolanmiu
    Author
  3. dolanmiu commented on Oct 8, 2016

    @dolanmiu
    Author

    Sorry, yeah I'm dumb, forgot to add --prod after ng build

    ng build --prod fixes the issue

  4. dolanmiu commented on Oct 8, 2016

    @dolanmiu
    Author

    Having said that.. the favicon.ico isnt copied over

  5. asaph26 commented on Oct 8, 2016

    @asaph26

    @dolanmiu This an open issue with the angular-cli that is not resolved yet. You have to copy the files manually or through a script.

    More info here. #2137

  6. dolanmiu commented on Oct 9, 2016

    @dolanmiu
    Author

    I think the release today (beta-17) fixes this issue. I haven't used it yet, but from reading the commit history, I can see:

    v1.0.0-beta.17...master#diff-ee1c44b86beb3967c38917e8b61c031aR12

  7. filipesilva commented on Oct 10, 2016

    @filipesilva
    Contributor

    @dolanmiu that commit does fix it, but was not included in beta.17. Should be in the next version.

  8. angular-automatic-lock-bot commented on Sep 6, 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.

  9. locked and limited conversation to collaborators on Sep 6, 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