Show HN: Eleven – Code sandboxes with automatic HTTPS
2 by jeremylevy | 0 comments on Hacker News.
Hey HN, Eleven is the second project that I've built to learn Go. It lets you create a code sandbox in your cloud provider account easily. What's a "code sandbox"? Just a VM, running in your cloud provider account, with some runtimes pre-installed, your repositories cloned, a way to connect to it with your preferred editor (or via SSH) and a way to serve your apps easily via HTTP (with automatic HTTPS). You could use it to deploy your app, as a remote development environment or even to test some code. It's up to you. For example, to deploy a Node.JS app: $ eleven aws init hello-world --runtimes node@18.7.0 --repositories eleven-sh/hello-world > Success! The sandbox "hello-world" was initialized. $ ssh eleven/hello-world forever node index.js > Forever: command started. Run "forever stop" in current path to stop. $ eleven aws serve hello-world 8000 --as hello.eleven.sh > Success! The port "8000" is now reachable at: https://hello.eleven.sh $ curl https://hello.eleven.sh > Hello World Still learning Go by the way, so I'm open to any suggestions to improve.
Wednesday, 2 November 2022
New Show Hacker News story: latest news
Show HN: Time Travel for Billing Periods
2 by AnhTho_FR | 4 comments on Hacker News.
Hi HN, Lago (YC S21 = Open-source metering and usage-based billing) founder here. Billing cycles are often a source of engineering complexity and confusion, so we made billing periods flexible in Lago: - If you want to migrate existing customers to Lago, you can set a billing period in the past. - If you just signed a new contract that will start in two weeks, you can set a start date in the future Other elements of flexibility: - Switch from 'calendar' to 'anniversary billing periods' within Lago - Assign multiple plans to a customer, and meter and charge usage separately (e.g., if your pricing looks like Heroku, Shopify or Webflow, for instance) Documentation: https://ift.tt/FvofO6n Github: https://ift.tt/4lnDXt3
2 by AnhTho_FR | 4 comments on Hacker News.
Hi HN, Lago (YC S21 = Open-source metering and usage-based billing) founder here. Billing cycles are often a source of engineering complexity and confusion, so we made billing periods flexible in Lago: - If you want to migrate existing customers to Lago, you can set a billing period in the past. - If you just signed a new contract that will start in two weeks, you can set a start date in the future Other elements of flexibility: - Switch from 'calendar' to 'anniversary billing periods' within Lago - Assign multiple plans to a customer, and meter and charge usage separately (e.g., if your pricing looks like Heroku, Shopify or Webflow, for instance) Documentation: https://ift.tt/FvofO6n Github: https://ift.tt/4lnDXt3
Tuesday, 1 November 2022
New Show Hacker News story: latest news
Show HN: Minimax – A Compressed-First, Microcoded RISC-V CPU
63 by gsmecher | 11 comments on Hacker News.
RISC-V's compressed instruction (RVC) extension is intended as an add-on to the regular, 32-bit instruction set, not a replacement or competitor. Its designers intended RVC instructions to be expanded into regular 32-bit RV32I equivalents via a pre-decoder. What happens if we explicitly architect a RISC-V CPU to execute RVC instructions, and "mop up" any RV32I instructions that aren't convenient via a microcode layer? What architectural optimizations are unlocked as a result? "Minimax" is an experimental RISC-V implementation intended to establish if an RVC-optimized CPU is, in practice, any simpler than an ordinary RV32I core with pre-decoder. While it passes a modest test suite, you should not use it without caution. (There are a large number of excellent, open source, "little" RISC-V implementations you should probably use reach for first.)
63 by gsmecher | 11 comments on Hacker News.
RISC-V's compressed instruction (RVC) extension is intended as an add-on to the regular, 32-bit instruction set, not a replacement or competitor. Its designers intended RVC instructions to be expanded into regular 32-bit RV32I equivalents via a pre-decoder. What happens if we explicitly architect a RISC-V CPU to execute RVC instructions, and "mop up" any RV32I instructions that aren't convenient via a microcode layer? What architectural optimizations are unlocked as a result? "Minimax" is an experimental RISC-V implementation intended to establish if an RVC-optimized CPU is, in practice, any simpler than an ordinary RV32I core with pre-decoder. While it passes a modest test suite, you should not use it without caution. (There are a large number of excellent, open source, "little" RISC-V implementations you should probably use reach for first.)
New Show Hacker News story: latest news
Show HN: Wrote a tiny WebAssembly (wat2wasm) compiler in Go
7 by thomscoder | 0 comments on Hacker News.
As a personal project I wrote a really tiny Wat 2 Wasm compiler in Go. Mainly for demonstrative and educational purposes. It was tough: I didn't know anything about WebAssembly internals and I'm a newbie with Go... so I tried to document it as much as I could for anyone that would like to approach the quest in the future! It misses a lot of features (that will be gradually implemented). Any feedback is welcomed!! Demo: https://ift.tt/SuROniv
7 by thomscoder | 0 comments on Hacker News.
As a personal project I wrote a really tiny Wat 2 Wasm compiler in Go. Mainly for demonstrative and educational purposes. It was tough: I didn't know anything about WebAssembly internals and I'm a newbie with Go... so I tried to document it as much as I could for anyone that would like to approach the quest in the future! It misses a lot of features (that will be gradually implemented). Any feedback is welcomed!! Demo: https://ift.tt/SuROniv
Subscribe to:
Posts (Atom)