Skip to content

Feature Request: Production Build into Separate Directory #801

Closed

Description

@rkralston

Please provide us with the following information:

  1. OS? Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
    Windows 10
  1. Versions. Please run ng --version. If there's nothing outputted, please
    run in a Terminal:
    node --version
    And paste the result here.
    angular-cli: 1.0.0-beta.2-mobile.3
    node: 6.1.0
    os: win32 x64

  2. Repro steps. Was this an app that wasn't created using the CLI? What change did you
    do on your code? etc.
    n/a

  3. The log given by the failure. Normally this include a stack trace and some
    more information.
    n/a

  4. Mention any other details that might be useful.


    Thanks! We'll be in touch soon.
    Currently, dev and prod both are built to /dist. I am developing and pushing drafts to a site for teams (multiple geographical locations) to evaluate.

Is it possible to have the dev and prod builds go to separate directories (/dev and /prod)?

Activity

  1. JonCubed commented on May 18, 2016

    @JonCubed
    Contributor

    I dont think this is currently possible

  2. Brocco commented on May 24, 2016

    @Brocco
    Contributor

    @rkralston Can you please provide a possible use case for this functionality? It will become quite a bit more complicated when other environments are added beyond the current dev & prod.

  3. rkralston commented on May 25, 2016

    @rkralston
    Author

    The Use Case is in support of UAT: constant builds to a UAT server pushed by git.

    I have an online UAT server to which I push stable builds for testing and approval. I am pushing to that server using git to allow for the full functionality of updates and rollbacks.

    Currently, I have a prod directory at the same level as dist. My prod directory is ignored. The directory has its own git configuration. I build a prod build and manually copy dist to that prod directory. This gives me full git functionality to incrementally push stable builds to UAT.

    It would be nice if ng build -prod could target that build directory saving me a few steps and allowing me to automate pushing stable builds to UAT.

  4. changed the title [-]Production Build into Separate Directory[/-] [+]Feature Request: Production Build into Separate Directory[/+] on May 25, 2016
  5. filipesilva commented on Jun 4, 2016

    @filipesilva
    Contributor

    Related #682

  6. filipesilva commented on Jun 4, 2016

    @filipesilva
    Contributor

    Workaround in #804

  7. filipesilva commented on Jun 4, 2016

    @filipesilva
    Contributor

    Closed in favor of #817

  8. 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.

  9. 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

    P5The team acknowledges the request but does not plan to address it, it remains open for discussioneffort1: easy (hours)

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions