<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="/assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>حمزہ شیخ عرف ایکچار (salt کے بارے میں تحاریر)</title><link>https://www.aikchar.me/</link><description></description><atom:link href="https://www.aikchar.me/ur/categories/salt.xml" rel="self" type="application/rss+xml"></atom:link><language>ur</language><copyright>Contents © 2024 &lt;a href="mailto:@aikchar"&gt;حمزہ شیخ&lt;/a&gt; لائیسنس</copyright><lastBuildDate>Tue, 17 Sep 2024 05:03:37 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Follow Conventions to Build Infrastructure</title><link>https://www.aikchar.me/ur/blog/follow-conventions-to-build-infrastructure.html</link><dc:creator>Hamza Sheikh</dc:creator><description>&lt;div&gt;&lt;p&gt;Any sufficiently large software system depends on a lot of third-party
artifacts, from operating systems to libraries to pre-built packages and
everything else in between. For example, to deploy a single web server running
a Django application requires a developer to pull in a Linux OS, Python,
Django, Gunicorn, nginx, etc. Whether this complete package is deployed on
a VM under your control or your customers', you want to follow conventions
in the entire lifecycle of the application.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://www.aikchar.me/ur/blog/follow-conventions-to-build-infrastructure.html"&gt; Read more …&lt;/a&gt; (4 منٹ کا مطالعہ باقی)&lt;/p&gt;&lt;/div&gt;</description><guid>https://www.aikchar.me/ur/blog/follow-conventions-to-build-infrastructure.html</guid><pubDate>Tue, 30 Aug 2016 05:00:16 GMT</pubDate></item></channel></rss>