<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Development Environment on Nalar</title>
    <link>https://nalar.dev/tags/development-environment/</link>
    <description>Recent content in Development Environment on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 19 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/development-environment/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How GitHub Codespaces Uses Core-Hours, Port Forwarding, and CI</title>
      <link>https://nalar.dev/how-github-codespaces-uses-core-hours-port-forwarding-and-ci/</link>
      <pubDate>Sat, 19 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/how-github-codespaces-uses-core-hours-port-forwarding-and-ci/</guid>
      <description>&lt;p&gt;A GitHub Codespace is a development machine running in the cloud, not a CI runner with an editor attached. It stays interactive while a developer edits files, runs commands, starts servers, debugs processes, and commits changes. That distinction explains three behaviors that are easy to confuse: how compute quota is measured, how &lt;code&gt;localhost&lt;/code&gt; becomes reachable from a browser, and where CI begins after code is pushed.&lt;/p&gt;&#xA;&lt;h2 id=&#34;core-hours-measure-machine-capacity-multiplied-by-active-time&#34;&gt;Core-hours measure machine capacity multiplied by active time&lt;/h2&gt;&#xA;&lt;p&gt;Codespaces compute usage is measured in core-hours. The accounting model is straightforward:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
