The best Hacker News stories from Show from the past day
Latest posts:
Show HN: Recode – Free, open-source, community-driven Codespaces alternative
Hey HN,<p>As most of you (I think?), I cannot learn something without having a project, on the side, to implement what I’ve just learned.<p>Recode is the project that I've used to learn Go. It lets you create a development environment in your cloud provider account easily.<p>You can think of it as a desktop version of Gitpod / Coder / GitHub Codespaces less polished and with less features but 100% free, 100% open-source and 100% community-driven.<p>At the time of writing, it only works with Visual Studio Code and AWS.<p>In order to let you configure your development environments easily, I’ve chosen to use Docker with some Dockerfiles:<p><pre><code> - One for your user configuration.
- One for your project.
</code></pre>
The user configuration corresponds to the tools / settings that you use in all your projects like your timezone / locale, your preferred shell or your dotfiles.<p>The project configuration corresponds to the tools / settings that you use in a specific project like Go >= 1.18 and Node.js >= 14.<p>As you may have guessed, the project configuration inherits from the user one.<p>> Why Docker and not something like NixOS, for example?<p>I know that containers are not meant to be used as a VM like that, but, at the time of writing, Docker is still the most widely used tool among developers to configure their environment (even if it may certainly change in the future :-)).<p>> Given that my dev env will run in a container does it mean that it will be limited?<p>Mostly not.<p>Given the scope of this project (a private instance running in your own cloud provider account), Docker is mostly used for configuration purpose and not to "isolate" the VM from your environment.<p>As a result, your development environment container runs in privileged mode in the same network than the host.<p>----<p>I post this here, because, you know, even learning project could be useful to someone.<p>Still learning Go by the way, so I'm open to any suggestions to improve.
Show HN: Recode – Free, open-source, community-driven Codespaces alternative
Hey HN,<p>As most of you (I think?), I cannot learn something without having a project, on the side, to implement what I’ve just learned.<p>Recode is the project that I've used to learn Go. It lets you create a development environment in your cloud provider account easily.<p>You can think of it as a desktop version of Gitpod / Coder / GitHub Codespaces less polished and with less features but 100% free, 100% open-source and 100% community-driven.<p>At the time of writing, it only works with Visual Studio Code and AWS.<p>In order to let you configure your development environments easily, I’ve chosen to use Docker with some Dockerfiles:<p><pre><code> - One for your user configuration.
- One for your project.
</code></pre>
The user configuration corresponds to the tools / settings that you use in all your projects like your timezone / locale, your preferred shell or your dotfiles.<p>The project configuration corresponds to the tools / settings that you use in a specific project like Go >= 1.18 and Node.js >= 14.<p>As you may have guessed, the project configuration inherits from the user one.<p>> Why Docker and not something like NixOS, for example?<p>I know that containers are not meant to be used as a VM like that, but, at the time of writing, Docker is still the most widely used tool among developers to configure their environment (even if it may certainly change in the future :-)).<p>> Given that my dev env will run in a container does it mean that it will be limited?<p>Mostly not.<p>Given the scope of this project (a private instance running in your own cloud provider account), Docker is mostly used for configuration purpose and not to "isolate" the VM from your environment.<p>As a result, your development environment container runs in privileged mode in the same network than the host.<p>----<p>I post this here, because, you know, even learning project could be useful to someone.<p>Still learning Go by the way, so I'm open to any suggestions to improve.
Show HN: Recode – Free, open-source, community-driven Codespaces alternative
Hey HN,<p>As most of you (I think?), I cannot learn something without having a project, on the side, to implement what I’ve just learned.<p>Recode is the project that I've used to learn Go. It lets you create a development environment in your cloud provider account easily.<p>You can think of it as a desktop version of Gitpod / Coder / GitHub Codespaces less polished and with less features but 100% free, 100% open-source and 100% community-driven.<p>At the time of writing, it only works with Visual Studio Code and AWS.<p>In order to let you configure your development environments easily, I’ve chosen to use Docker with some Dockerfiles:<p><pre><code> - One for your user configuration.
- One for your project.
</code></pre>
The user configuration corresponds to the tools / settings that you use in all your projects like your timezone / locale, your preferred shell or your dotfiles.<p>The project configuration corresponds to the tools / settings that you use in a specific project like Go >= 1.18 and Node.js >= 14.<p>As you may have guessed, the project configuration inherits from the user one.<p>> Why Docker and not something like NixOS, for example?<p>I know that containers are not meant to be used as a VM like that, but, at the time of writing, Docker is still the most widely used tool among developers to configure their environment (even if it may certainly change in the future :-)).<p>> Given that my dev env will run in a container does it mean that it will be limited?<p>Mostly not.<p>Given the scope of this project (a private instance running in your own cloud provider account), Docker is mostly used for configuration purpose and not to "isolate" the VM from your environment.<p>As a result, your development environment container runs in privileged mode in the same network than the host.<p>----<p>I post this here, because, you know, even learning project could be useful to someone.<p>Still learning Go by the way, so I'm open to any suggestions to improve.
Show HN: 1024, a 2048 Puzzle Game
Show HN: 1024, a 2048 Puzzle Game
Show HN: 1024, a 2048 Puzzle Game
Show HN: 1024, a 2048 Puzzle Game
Show HN: Yare 2 – Programmable RTS game
Hi HN! About a year ago I showed my side project Yare here (<a href="https://news.ycombinator.com/item?id=27365961" rel="nofollow">https://news.ycombinator.com/item?id=27365961</a>) and was overblown by the feedback and support. Since then a lot has changed and I'm excited to share the beta of 'Yare 2' (<a href="https://www.yare.io/" rel="nofollow">https://www.yare.io/</a>).<p>The simple programming game has evolved into something a little more complex with the ability to not only control the units with code, but now practically anything is programmable. E.g. the players can build their own UI elements to play the game with (when you choose 'play with mouse and keyboard' on the homescreen, it showcases what is possible to create).<p>This is a passion project that I don't plan to anyhow excessively monetize and will be always free to play, but I'm worried that it's perhaps growing into a too chaotic/confusing game and losing its initial simplicity.
Show HN: Yare 2 – Programmable RTS game
Hi HN! About a year ago I showed my side project Yare here (<a href="https://news.ycombinator.com/item?id=27365961" rel="nofollow">https://news.ycombinator.com/item?id=27365961</a>) and was overblown by the feedback and support. Since then a lot has changed and I'm excited to share the beta of 'Yare 2' (<a href="https://www.yare.io/" rel="nofollow">https://www.yare.io/</a>).<p>The simple programming game has evolved into something a little more complex with the ability to not only control the units with code, but now practically anything is programmable. E.g. the players can build their own UI elements to play the game with (when you choose 'play with mouse and keyboard' on the homescreen, it showcases what is possible to create).<p>This is a passion project that I don't plan to anyhow excessively monetize and will be always free to play, but I'm worried that it's perhaps growing into a too chaotic/confusing game and losing its initial simplicity.
Show HN: Yare 2 – Programmable RTS game
Hi HN! About a year ago I showed my side project Yare here (<a href="https://news.ycombinator.com/item?id=27365961" rel="nofollow">https://news.ycombinator.com/item?id=27365961</a>) and was overblown by the feedback and support. Since then a lot has changed and I'm excited to share the beta of 'Yare 2' (<a href="https://www.yare.io/" rel="nofollow">https://www.yare.io/</a>).<p>The simple programming game has evolved into something a little more complex with the ability to not only control the units with code, but now practically anything is programmable. E.g. the players can build their own UI elements to play the game with (when you choose 'play with mouse and keyboard' on the homescreen, it showcases what is possible to create).<p>This is a passion project that I don't plan to anyhow excessively monetize and will be always free to play, but I'm worried that it's perhaps growing into a too chaotic/confusing game and losing its initial simplicity.
Show HN: Build for any cloud with the same code
We have been working on Multy, an open-source[1] tool that enables developers to deploy and switch to any cloud - AWS, Azure and GCP for now.<p>We realized that, even when using Terraform, writing infrastructure code is very different for each cloud provider. This means changing clouds or deploying the same infrastructure in multiple clouds requires rewriting the same thing multiple times. And even though most core resources have the same functionality, developers need to learn a new provider and all its nuances when choosing a new cloud. This is why we built Multy.<p>Multy is currently available as a Terraform provider. You can write cloud-agnostic code and then just choose which cloud you want to deploy to. Multy will then call the cloud provider APIs on your behalf. For example, the following Terraform code deploys a virtual network in AWS and can be easily changed to deploy to Azure or GCP:<p>```
resource "multy_virtual_network" "vn" {<p><pre><code> cloud = "aws" // or azure, or gcp
name = "multy_vn"
cidr_block = "10.0.0.0/16"
location = "eu_west_1"</code></pre>
}
```<p>Our goal is to expose any configuration that is common across all clouds, but there’s always specific features that are not available in all of them. For example, if you want a very specific AWS CPU for your Virtual Machine or use a region that is only available in GCP. To enable this, we implemented overrides [2] - a way to configure the underlying infrastructure for cloud-specific purposes. You can also mix other Terraform code that uses the cloud-specific providers with Multy. While this makes you somewhat locked in, having your 80% or 90% of your infrastructure cloud-agnostic is still very powerful.<p>You can see more complex examples in our documentation - <a href="https://docs.multy.dev/examples/" rel="nofollow">https://docs.multy.dev/examples/</a>.<p>We’re still in early days and looking for feedback from other developers on our approach. Let us know what you think!<p>[1] <a href="https://github.com/multycloud/multy" rel="nofollow">https://github.com/multycloud/multy</a><p>[2] <a href="https://docs.multy.dev/overrides" rel="nofollow">https://docs.multy.dev/overrides</a>
Show HN: Build for any cloud with the same code
We have been working on Multy, an open-source[1] tool that enables developers to deploy and switch to any cloud - AWS, Azure and GCP for now.<p>We realized that, even when using Terraform, writing infrastructure code is very different for each cloud provider. This means changing clouds or deploying the same infrastructure in multiple clouds requires rewriting the same thing multiple times. And even though most core resources have the same functionality, developers need to learn a new provider and all its nuances when choosing a new cloud. This is why we built Multy.<p>Multy is currently available as a Terraform provider. You can write cloud-agnostic code and then just choose which cloud you want to deploy to. Multy will then call the cloud provider APIs on your behalf. For example, the following Terraform code deploys a virtual network in AWS and can be easily changed to deploy to Azure or GCP:<p>```
resource "multy_virtual_network" "vn" {<p><pre><code> cloud = "aws" // or azure, or gcp
name = "multy_vn"
cidr_block = "10.0.0.0/16"
location = "eu_west_1"</code></pre>
}
```<p>Our goal is to expose any configuration that is common across all clouds, but there’s always specific features that are not available in all of them. For example, if you want a very specific AWS CPU for your Virtual Machine or use a region that is only available in GCP. To enable this, we implemented overrides [2] - a way to configure the underlying infrastructure for cloud-specific purposes. You can also mix other Terraform code that uses the cloud-specific providers with Multy. While this makes you somewhat locked in, having your 80% or 90% of your infrastructure cloud-agnostic is still very powerful.<p>You can see more complex examples in our documentation - <a href="https://docs.multy.dev/examples/" rel="nofollow">https://docs.multy.dev/examples/</a>.<p>We’re still in early days and looking for feedback from other developers on our approach. Let us know what you think!<p>[1] <a href="https://github.com/multycloud/multy" rel="nofollow">https://github.com/multycloud/multy</a><p>[2] <a href="https://docs.multy.dev/overrides" rel="nofollow">https://docs.multy.dev/overrides</a>
Show HN: Build for any cloud with the same code
We have been working on Multy, an open-source[1] tool that enables developers to deploy and switch to any cloud - AWS, Azure and GCP for now.<p>We realized that, even when using Terraform, writing infrastructure code is very different for each cloud provider. This means changing clouds or deploying the same infrastructure in multiple clouds requires rewriting the same thing multiple times. And even though most core resources have the same functionality, developers need to learn a new provider and all its nuances when choosing a new cloud. This is why we built Multy.<p>Multy is currently available as a Terraform provider. You can write cloud-agnostic code and then just choose which cloud you want to deploy to. Multy will then call the cloud provider APIs on your behalf. For example, the following Terraform code deploys a virtual network in AWS and can be easily changed to deploy to Azure or GCP:<p>```
resource "multy_virtual_network" "vn" {<p><pre><code> cloud = "aws" // or azure, or gcp
name = "multy_vn"
cidr_block = "10.0.0.0/16"
location = "eu_west_1"</code></pre>
}
```<p>Our goal is to expose any configuration that is common across all clouds, but there’s always specific features that are not available in all of them. For example, if you want a very specific AWS CPU for your Virtual Machine or use a region that is only available in GCP. To enable this, we implemented overrides [2] - a way to configure the underlying infrastructure for cloud-specific purposes. You can also mix other Terraform code that uses the cloud-specific providers with Multy. While this makes you somewhat locked in, having your 80% or 90% of your infrastructure cloud-agnostic is still very powerful.<p>You can see more complex examples in our documentation - <a href="https://docs.multy.dev/examples/" rel="nofollow">https://docs.multy.dev/examples/</a>.<p>We’re still in early days and looking for feedback from other developers on our approach. Let us know what you think!<p>[1] <a href="https://github.com/multycloud/multy" rel="nofollow">https://github.com/multycloud/multy</a><p>[2] <a href="https://docs.multy.dev/overrides" rel="nofollow">https://docs.multy.dev/overrides</a>
Show HN: Build for any cloud with the same code
We have been working on Multy, an open-source[1] tool that enables developers to deploy and switch to any cloud - AWS, Azure and GCP for now.<p>We realized that, even when using Terraform, writing infrastructure code is very different for each cloud provider. This means changing clouds or deploying the same infrastructure in multiple clouds requires rewriting the same thing multiple times. And even though most core resources have the same functionality, developers need to learn a new provider and all its nuances when choosing a new cloud. This is why we built Multy.<p>Multy is currently available as a Terraform provider. You can write cloud-agnostic code and then just choose which cloud you want to deploy to. Multy will then call the cloud provider APIs on your behalf. For example, the following Terraform code deploys a virtual network in AWS and can be easily changed to deploy to Azure or GCP:<p>```
resource "multy_virtual_network" "vn" {<p><pre><code> cloud = "aws" // or azure, or gcp
name = "multy_vn"
cidr_block = "10.0.0.0/16"
location = "eu_west_1"</code></pre>
}
```<p>Our goal is to expose any configuration that is common across all clouds, but there’s always specific features that are not available in all of them. For example, if you want a very specific AWS CPU for your Virtual Machine or use a region that is only available in GCP. To enable this, we implemented overrides [2] - a way to configure the underlying infrastructure for cloud-specific purposes. You can also mix other Terraform code that uses the cloud-specific providers with Multy. While this makes you somewhat locked in, having your 80% or 90% of your infrastructure cloud-agnostic is still very powerful.<p>You can see more complex examples in our documentation - <a href="https://docs.multy.dev/examples/" rel="nofollow">https://docs.multy.dev/examples/</a>.<p>We’re still in early days and looking for feedback from other developers on our approach. Let us know what you think!<p>[1] <a href="https://github.com/multycloud/multy" rel="nofollow">https://github.com/multycloud/multy</a><p>[2] <a href="https://docs.multy.dev/overrides" rel="nofollow">https://docs.multy.dev/overrides</a>
Show HN: SaveSlack – create searchable knowledgebase from your Slack community
Show HN: SaveSlack – create searchable knowledgebase from your Slack community
Show HN: Automatically fill PDF templates per API
Show HN: Automatically fill PDF templates per API
Show HN: Automatically fill PDF templates per API
Show HN: Dungeons and Business Cards