<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ta-Ching Chen on Fission</title><link>https://deploy-preview-295--fission-website.netlify.app/author/ta-ching-chen/</link><description>Recent content in Ta-Ching Chen on Fission</description><generator>Hugo</generator><language>en</language><atom:link href="https://deploy-preview-295--fission-website.netlify.app/author/ta-ching-chen/index.xml" rel="self" type="application/rss+xml"/><item><title>Setting Ingress for your Functions</title><link>https://deploy-preview-295--fission-website.netlify.app/blog/setting-ingress-for-your-functions/</link><pubDate>Mon, 28 Oct 2019 22:09:38 +0800</pubDate><guid>https://deploy-preview-295--fission-website.netlify.app/blog/setting-ingress-for-your-functions/</guid><description>&lt;p&gt;Some exciting updates to ingress host path, annotations, and TLS support.
In Fission version 1.6.0, which was released on Friday 11 October 2019, new features arrived. This blogpost covers the exciting updates to ingress host path, annotations, and TLS support.&lt;/p&gt;
&lt;p&gt;Fission previously supported ingress. However, it lacked support for TLS, host field, and ingress annotations. Now with version 1.6, all three are supported.&lt;/p&gt;
&lt;p&gt;In this blog post, we will cover all three of the new features. But first, let&amp;rsquo;s talk about ingress some more.&lt;/p&gt;</description></item><item><title>Live-Reload in Fission: Instant feedback on your Serverless Functions</title><link>https://deploy-preview-295--fission-website.netlify.app/blog/live-reload-in-fission-instant-feedback-on-your-serverless-functions/</link><pubDate>Tue, 16 Oct 2018 01:04:00 -0700</pubDate><guid>https://deploy-preview-295--fission-website.netlify.app/blog/live-reload-in-fission-instant-feedback-on-your-serverless-functions/</guid><description>&lt;p&gt;Accelerating feedback loops are an important devops
principle: the sooner you find a bug, the cheaper it is
to fix it.&lt;/p&gt;
&lt;p&gt;While developing your application, you’re typically
going through a cycle: write code, build, deploy into a
test environment, run tests, fix, repeat. The build and
deploy stages of this cycle are idle, unproductive time
where you’re simply waiting. As a project grows, these
stages get slower and slower. Once they’re slow enough,
you end up context switching to another task, while
waiting, and that makes it harder to get back into the
right context and fix any bugs you find in testing.&lt;/p&gt;</description></item></channel></rss>