<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Config &#8211; Christian Lüdemann</title>
	<atom:link href="https://christianlydemann.com/tag/config/feed/" rel="self" type="application/rss+xml" />
	<link>https://christianlydemann.com</link>
	<description>Advanced Angular Training Made Simple</description>
	<lastBuildDate>Fri, 14 Sep 2018 07:34:54 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.7.5</generator>

<image>
	<url>https://i0.wp.com/christianlydemann.com/wp-content/uploads/2019/06/cropped-logo-3.png?fit=32%2C32&#038;ssl=1</url>
	<title>Config &#8211; Christian Lüdemann</title>
	<link>https://christianlydemann.com</link>
	<width>32</width>
	<height>32</height>
</image> 
<site xmlns="com-wordpress:feed-additions:1">147954794</site>	<item>
		<title>Implementing Dynamic Environment Configuration in Angular for Avoiding One Build per Environment</title>
		<link>https://christianlydemann.com/implementing-dynamic-environments-in-angular-for-avoiding-one-build-per-environment/</link>
					<comments>https://christianlydemann.com/implementing-dynamic-environments-in-angular-for-avoiding-one-build-per-environment/#disqus_thread</comments>
		
		<dc:creator><![CDATA[Christian]]></dc:creator>
		<pubDate>Thu, 13 Sep 2018 18:00:14 +0000</pubDate>
				<category><![CDATA[Angular]]></category>
		<category><![CDATA[Config]]></category>
		<category><![CDATA[Environment]]></category>
		<guid isPermaLink="false">https://christianlydemann.com/?p=627</guid>

					<description><![CDATA[One big flaw of the Angular CLI&#8217;s way of handling environments, according to the build once, deploy many DevOps principle, is that out-of-the-box Angular CLI wants you to create one separate build per environment. Why should you only build once and reuse that build in all environments? The reason why you don&#8217;t want to create a separate build for &#8230;<p class="read-more"> <a class="" href="https://christianlydemann.com/implementing-dynamic-environments-in-angular-for-avoiding-one-build-per-environment/"> <span class="screen-reader-text">Implementing Dynamic Environment Configuration in Angular for Avoiding One Build per Environment</span> Read More »</a></p>]]></description>
		
					<wfw:commentRss>https://christianlydemann.com/implementing-dynamic-environments-in-angular-for-avoiding-one-build-per-environment/feed/</wfw:commentRss>
			<slash:comments>21</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">627</post-id>	</item>
	</channel>
</rss>

<!--
Performance optimized by W3 Total Cache. Learn more: https://www.boldgrid.com/w3-total-cache/

Object Caching 0/1326 objects using Memcache
Page Caching using Disk: Enhanced 
Minified using Disk
Database Caching using Disk (Request-wide modification query)

Served from: christianlydemann.com @ 2026-03-11 14:03:17 by W3 Total Cache
-->