Bumps [github.com/gohugoio/hugo](https://github.com/gohugoio/hugo) from 0.151.2 to 0.152.2. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/gohugoio/hugo/releases">github.com/gohugoio/hugo's releases</a>.</em></p> <blockquote> <h2>v0.152.2</h2> <p>In <code>v0.152.0</code> we tightened the source validation for <a href="https://gohugo.io/configuration/module/#mounts">file mounts</a>. We always said that <em>project mounts can mount with absolute file/directorynames, modules/themes are restricted to relative</em>. In <code>v0.152.0</code> we narrowed module/themes mounts to be local, which made the setup in the bug report listed below fail:</p> <pre lang="toml"><code>[[module.mounts]] source = '../../node_modules/bootstrap' target = 'assets/vendor/bootstrap' </code></pre> <p>One part of this is security. But the construct above is <em>usually</em> very odd (the project uses files in a theme/module, not the other way around) and not very portable. But the example above demonstrates a valid exception, that we now have added support for in a portable way. The above example now works as it did before <code>v0.152.0</code>, but going forward you can also write:</p> <pre lang="toml"><code>[[module.mounts]] source = 'node_modules/bootstrap' target = 'assets/vendor/bootstrap' </code></pre> <p>We now have the <code>node_modules</code> as a special case: For themes/modules we first check if the mounted source exists locally, if not we try relative to the project root.</p> <h2>What's Changed</h2> <ul> <li>deps: Update github.com/tdewolff/minify v2.24.4 => v2.24.5 1c8c21e45 <a href="https://github.com/jmooring"><code>@jmooring</code></a> <a href="https://redirect.github.com/gohugoio/hugo/issues/14086">#14086</a></li> <li>hugofs: Make node_modules a "special case" mount 809ebe01f <a href="https://github.com/bep"><code>@bep</code></a> <a href="https://redirect.github.com/gohugoio/hugo/issues/14089">#14089</a></li> <li>github: Fix typo in stale PR message 08a0679a8 <a href="https://github.com/jordelver"><code>@jordelver</code></a></li> </ul> <h2>v0.152.1</h2> <p>These fixes are are all related to the YAML library upgrade in <a href="https://github.com/gohugoio/hugo/releases/tag/v0.152.0">v0.152.0</a>.</p> <ul> <li>Expand the numeric conversions to template funcs/methods e08278d16 <a href="https://github.com/bep"><code>@bep</code></a> <a href="https://redirect.github.com/gohugoio/hugo/issues/14079">#14079</a></li> <li>Fix where with uint64 df4f80d54 <a href="https://github.com/bep"><code>@bep</code></a> <a href="https://redirect.github.com/gohugoio/hugo/issues/14081">#14081</a></li> <li>Fix it so YAML integer types can be used where Go int types are expected d4c78885a <a href="https://github.com/bep"><code>@bep</code></a> <a href="https://redirect.github.com/gohugoio/hugo/issues/14079">#14079</a></li> <li>tpl/compare: Fix compare/sort of uint64s 29e2c2fa9 <a href="https://github.com/bep"><code>@bep</code></a> <a href="https://redirect.github.com/gohugoio/hugo/issues/14078">#14078</a></li> <li>Fix "assignment to entry in nil map" on empty YAML config files 0579afc3c <a href="https://github.com/bep"><code>@bep</code></a> <a href="https://redirect.github.com/gohugoio/hugo/issues/14074">#14074</a></li> </ul> <h2>v0.152.0</h2> <p>The big new thing and the motivation behind this release is the upgrade to a more modern YAML library in <a href="https://github.com/goccy"><code>@goccy</code></a> 's <a href="https://github.com/goccy/go-yaml">github.com/goccy/go-yaml</a>. It's been a surprisingly long and winding road to get here. <strong>Note that this upgrade comes with some minor breaking changes, most notably that the old YAML 1.1 spec listed a set of strings that, when unquoted, were treated as boolean <code>true</code> or <code>false</code>.</strong> So if you're using any of the values in the table below as booleans, you need to adjust your YAML, but I suspect that fixing this very surprising behavior will fix more issues than it introduces. A big new thing with this new YAML library is the support for <a href="https://www.linode.com/docs/guides/yaml-anchors-aliases-overrides-extensions/">YAML anchors and aliases</a> which helps to reduce duplication in e.g. your configuration. There are some examples in Hugo's <a href="https://github.com/gohugoio/hugo/blob/master/hugoreleaser.yaml">release build configuration</a> and in the <a href="https://github.com/gohugoio/hugo/blob/master/.circleci/config.yml">Hugo's CI release setup</a>.</p> <table> <thead> <tr> <th align="left">Values</th> <th align="left">Old meaning</th> <th align="left">New meaning</th> </tr> </thead> <tbody> <tr> <td align="left"><code>yes</code>, <code>Yes</code>, <code>YES</code>, <code>y</code>, <code>Y</code>, <code>on</code>, <code>On</code>, <code>ON</code></td> <td align="left"><code>true</code> (bool)</td> <td align="left"><code>yes</code>, <code>Yes</code>, <code>YES</code>, <code>y</code>, <code>Y</code>, <code>on</code>, <code>On</code>, <code>ON</code> (string)</td> </tr> <tr> <td align="left"><code>no</code>, <code>No</code>, <code>NO</code>, <code>n</code>, <code>N</code>, <code>off</code>, <code>Off</code>, <code>OFF</code></td> <td align="left"><code>false</code> (bool)</td> <td align="left"><code>no</code>, <code>No</code>, <code>NO</code>, <code>n</code>, <code>N</code>, <code>off</code>, <code>Off</code>, <code>OFF</code> (string)</td> </tr> </tbody> </table> <h2>Note</h2> <ul> <li>Replace to gopkg.in/yaml with github.com/goccy/go-yaml (note) a3d954846 <a href="https://github.com/bep"><code>@bep</code></a> <a href="https://redirect.github.com/gohugoio/hugo/issues/8822">#8822</a> <a href="https://redirect.github.com/gohugoio/hugo/issues/13043">#13043</a> <a href="https://redirect.github.com/gohugoio/hugo/issues/14053">#14053</a></li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/gohugoio/hugo/commit/6abdacad3f3fe944ea42177844469139e81feda6"><code>6abdaca</code></a> releaser: Bump versions for release of 0.152.2</li> <li><a href="https://github.com/gohugoio/hugo/commit/1c8c21e45eb7d87c1038b3f3b9ea87b82a11c867"><code>1c8c21e</code></a> deps: Update github.com/tdewolff/minify v2.24.4 => v2.24.5</li> <li><a href="https://github.com/gohugoio/hugo/commit/809ebe01fa954a44a48c265f0c9a4e4845b9a0f8"><code>809ebe0</code></a> hugofs: Make node_modules a "special case" mount</li> <li><a href="https://github.com/gohugoio/hugo/commit/08a0679a895678b38f1324ae78503fd32ec22996"><code>08a0679</code></a> github: Fix typo in stale PR message</li> <li><a href="https://github.com/gohugoio/hugo/commit/524b98665b64f206f14879ffe29c64f413592a2f"><code>524b986</code></a> releaser: Prepare repository for 0.153.0-DEV</li> <li><a href="https://github.com/gohugoio/hugo/commit/5869cbddd88590563c2b7b400e804ccc7d2cb697"><code>5869cbd</code></a> releaser: Bump versions for release of 0.152.1</li> <li><a href="https://github.com/gohugoio/hugo/commit/e08278d165399bd2d7d7331d966129a2faa268b2"><code>e08278d</code></a> Expand the numeric conversions to template funcs/methods</li> <li><a href="https://github.com/gohugoio/hugo/commit/df4f80d54f389407d935a0388707be2bf888d882"><code>df4f80d</code></a> Fix where with uint64</li> <li><a href="https://github.com/gohugoio/hugo/commit/d4c78885ae4cb7c488ea2ed399aa57f0861f44cb"><code>d4c7888</code></a> Fix it so YAML integer types can be used where Go int types are expected</li> <li><a href="https://github.com/gohugoio/hugo/commit/29e2c2fa92b10c1250376913558448e838e390fe"><code>29e2c2f</code></a> tpl/compare: Fix compare/sort of uint64s</li> <li>Additional commits viewable in <a href="https://github.com/gohugoio/hugo/compare/v0.151.2...v0.152.2">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Coder enables organizations to set up development environments in their public or private cloud infrastructure. Cloud development environments are defined with Terraform, connected through a secure high-speed Wireguard® tunnel, and automatically shut down when not used to save on costs. Coder gives engineering teams the flexibility to use the cloud for workloads most beneficial to them.
- Define cloud development environments in Terraform
- EC2 VMs, Kubernetes Pods, Docker Containers, etc.
- Automatically shutdown idle resources to save on costs
- Onboard developers in seconds instead of days
Quickstart
The most convenient way to try Coder is to install it on your local machine and experiment with provisioning cloud development environments using Docker (works on Linux, macOS, and Windows).
# First, install Coder
curl -L https://coder.com/install.sh | sh
# Start the Coder server (caches data in ~/.cache/coder)
coder server
# Navigate to http://localhost:3000 to create your initial user,
# create a Docker template and provision a workspace
Install
The easiest way to install Coder is to use our
install script for Linux
and macOS. For Windows, use the latest ..._installer.exe file from GitHub
Releases.
curl -L https://coder.com/install.sh | sh
You can run the install script with --dry-run to see the commands that will be used to install without executing them. Run the install script with --help for additional flags.
See install for additional methods.
Once installed, you can start a production deployment with a single command:
# Automatically sets up an external access URL on *.try.coder.app
coder server
# Requires a PostgreSQL instance (version 13 or higher) and external access URL
coder server --postgres-url <url> --access-url <url>
Use coder --help to get a list of flags and environment variables. Use our install guides for a complete walkthrough.
Documentation
Browse our docs here or visit a specific section below:
- Templates: Templates are written in Terraform and describe the infrastructure for workspaces
- Workspaces: Workspaces contain the IDEs, dependencies, and configuration information needed for software development
- IDEs: Connect your existing editor to a workspace
- Administration: Learn how to operate Coder
- Premium: Learn about our paid features built for large teams
Support
Feel free to open an issue if you have questions, run into bugs, or have a feature request.
Join our Discord to provide feedback on in-progress features and chat with the community using Coder!
Integrations
We are always working on new integrations. Please feel free to open an issue and ask for an integration. Contributions are welcome in any official or community repositories.
Official
- VS Code Extension: Open any Coder workspace in VS Code with a single click
- JetBrains Toolbox Plugin: Open any Coder workspace from JetBrains Toolbox with a single click
- JetBrains Gateway Plugin: Open any Coder workspace in JetBrains Gateway with a single click
- Dev Container Builder: Build development environments using
devcontainer.jsonon Docker, Kubernetes, and OpenShift - Coder Registry: Build and extend development environments with common use-cases
- Kubernetes Log Stream: Stream Kubernetes Pod events to the Coder startup logs
- Self-Hosted VS Code Extension Marketplace: A private extension marketplace that works in restricted or airgapped networks integrating with code-server.
- Setup Coder: An action to setup coder CLI in GitHub workflows.
Community
- Provision Coder with Terraform: Provision Coder on Google GKE, Azure AKS, AWS EKS, DigitalOcean DOKS, IBMCloud K8s, OVHCloud K8s, and Scaleway K8s Kapsule with Terraform
- Coder Template GitHub Action: A GitHub Action that updates Coder templates
Contributing
We are always happy to see new contributors to Coder. If you are new to the Coder codebase, we have a guide on how to get started. We'd love to see your contributions!
Hiring
Apply here if you're interested in joining our team.
