Skip to content

Is there a way to exclude a file from being merged during build (IE keep the file separate from bundles) #11441

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
pain0486 opened this issue Jul 3, 2018 · 2 comments

Comments

@pain0486
Copy link

pain0486 commented Jul 3, 2018

Bug Report or Feature Request (mark with an x)

- [ ] bug report -> please search issues before submitting
- [x ] feature request

Area

- [ ] devkit
- [x ] schematics ??

Desired functionality

OK so here is what I am trying to solve, perhaps there is a better way.
I have a config file that will provide and organization code and server code (among other things) to the rest of my application. The organization code will be a will be unique per client using the site while the sever code will be something representing live or demo. Each client will have their own site on a sub domain. For example

  • client1.mysite.com,
  • client2.mysite.com.

What I would like to do is build the application 1 time using ng build and deploy the site to each client site that has their own config file. Then have the built code reference the config file in the folder of the client site.

So instead of taking config.orgCode and inserting the value in the consuming file I want the consuming file to import ./config and use the orgCode property.

Mention any other details that might be useful

I know I could probably do this via multiple application support, but rebuilding each application and only changing a few small values in a handful of files seems very wasteful use of the CI server's resources.

@clydin
Copy link
Member

clydin commented Jul 6, 2018

Please see this issue (#7506) for details on how this can be accomplished.

@clydin clydin closed this as completed Jul 6, 2018
@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants