Show HN: Voxel map of my school, made with WebGL and SDF raymarching https://ift.tt/mjTqgyb

Show HN: Voxel map of my school, made with WebGL and SDF raymarching https://ift.tt/akmRtnl August 8, 2022 at 07:42PM

Show HN: Realtime 3D spectrogram visualization using threejs shaders https://ift.tt/ysWeJOE

Show HN: Realtime 3D spectrogram visualization using threejs shaders https://ift.tt/Wi3Votw August 8, 2022 at 05:58PM

Show HN: Build for any cloud with the same code https://ift.tt/omnE2Aj

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. 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. 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: ``` resource "multy_virtual_network" "vn" { cloud = "aws" // or azure, or gcp name = "multy_vn" cidr_block = "10.0.0.0/16" location = "eu_west_1" } ``` 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. You can see more complex examples in our documentation - https://ift.tt/ibeJPVU . We’re still in early days and looking for feedback from other developers on our approach. Let us know what you think! [1] https://ift.tt/jQ8KPyl [2] https://ift.tt/J9n2es5 https://ift.tt/jQ8KPyl August 8, 2022 at 05:57PM

Show HN: Automatically fill PDF templates per API https://ift.tt/auAK6oL

Show HN: Automatically fill PDF templates per API https://doqs.dev August 8, 2022 at 12:50AM

Show HN: Unblob – accurate and fast extraction suite for 30+ formats https://ift.tt/68N19Hz

Show HN: Unblob – accurate and fast extraction suite for 30+ formats https://unblob.org/ August 7, 2022 at 11:46PM

Show HN: Apprise v1.0.0 – A lightweight all-in-one notification solution https://ift.tt/1yst3K6

Show HN: Apprise v1.0.0 – A lightweight all-in-one notification solution I introduced Hacker News to Apprise back when it was just an experiment (and supported just 30 or so notification services at the time). Now supporting more then 85+ services and with a ton of built in features, I officially created it's first stable v1.0.0 release marking a major milestone for the project. Apprise doesn't compete with other notification services out there; instead it just acts as a proxy (or master switchboard) to support handling messages to them. It's a means of decoupling notification support from the systems that want to provide them. The idea is to adopt Apprise into your environment, and then you no longer have to worry about adding/removing support for new services as the come along and deprecating the ones that go away. The way it works is that every service out there maps to a `schema://credentials/?optional_configuration`. You just need to define the schemas you use, and then you can already use Apprise. Check out the list of the services available today here: https://ift.tt/CyqbTOg Apprise is 100% open source (MIT Licensed). It has an acompanied API I built for those who want to centralize their configuration (found here: https://ift.tt/tXs7mYz ). Some reasons you may also all find it useful: - It works perfectly with legacy servers (supporting even Python 2.7). So this fits system admins using older systems such as CentOS 6+ - It has a complete API that developers, devops, and administrators alike can leverage allowing them to control the notifications in their environments. - It supports configuration files allowing you to securely hide your credentials and map them to simple tags like `family`, `devops`, `marketing`, etc. There is no limit to the number of tag assignments. It supports a simple TEXT (https://ift.tt/5dO3Klj) based configuration, as well as a more advanced and configurable YAML (https://ift.tt/DNcMVXx) based one. - It sends all notifications asynchronously optimizing setups where there are many end-points to deliver to. - It supports inputs are of MARKDOWN, HTML, and TEXT and can easily convert between these depending on the endpoint. For example: HTML provided input would be converted to TEXT before passing it along as a text message. However the same HTML content provided would not be converted if the endpoint accepted it as such (such as Telegram, or Email). - It supports breaking large messages into smaller ones to fit the upstream service. Hence a text message (160 characters) or a Tweet (280 characters) would be constructed for you if the notification you sent was larger. - It supports file attachments too. So feel free to pass along an image, PDF, etc if the destination supports it. - It can easily allow you to write your own custom notifications and/or simply leverage Apprise as routing service to perform admin tasks for you. See here for more details: https://ift.tt/XcSAm0w - It has 100% code based test coverage. :) I hope to continue to add more services (and break 100+ supported services someday). I also hope some of you find it useful for your own project solution! https://ift.tt/kM8cDUh August 7, 2022 at 10:21PM

Show HN: Cronit – Online Cronjobs https://ift.tt/61TnUbe

Show HN: Cronit – Online Cronjobs https://cronit.app August 7, 2022 at 09:54AM