You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Feature Request: Production Build into Separate Directory #801
OS? Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
Windows 10
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
Repro steps. Was this an app that wasn't created using the CLI? What change did you
do on your code? etc.
n/a
The log given by the failure. Normally this include a stack trace and some
more information.
n/a
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)?
@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.
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.
Activity
JonCubed commentedon May 18, 2016
I dont think this is currently possible
Brocco commentedon May 24, 2016
@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.
rkralston commentedon May 25, 2016
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.
[-]Production Build into Separate Directory[/-][+]Feature Request: Production Build into Separate Directory[/+]filipesilva commentedon Jun 4, 2016
Related #682
filipesilva commentedon Jun 4, 2016
Workaround in #804
filipesilva commentedon Jun 4, 2016
Closed in favor of #817
angular-automatic-lock-bot commentedon Sep 5, 2019
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.