The best Hacker News stories from Show from the past day
Latest posts:
Show HN: Alsa_rnnoise – RNNoise-based noise removal plugin for ALSA
Show HN: Alsa_rnnoise – RNNoise-based noise removal plugin for ALSA
Launch HN: LayerCI (YC S20) - Staging servers that act like (and replace) CI
Hi HN, Lyn & Colin here. We’re co-founders of LayerCI (<a href="https://layerci.com" rel="nofollow">https://layerci.com</a>), which gives you a modern DevOps experience (CI/CD & staging environments) with as little work as writing a Dockerfile.<p>Most teams need CI/CD (run the build and deploy every time a developer pushes) or staging (host a server with my app in it to share), but current approaches always have at least one of these problems:<p>- Simplistic (only run unit tests)<p>- Slow (wait 10 minutes to run the same repetitive setup steps like "npm install")<p>- Complex (cache keys, base images, a slack channel to reserve staging servers, …)<p>We’ve spent over a year iterating with our customers to build a product that solves all of these problems.<p>Our configuration files (Layerfiles) look like Dockerfiles, so regular developers can write and maintain them. Here's one that creates a staging server for create-react-app:<p>FROM vm/ubuntu:18.04<p>RUN curl -sS <a href="https://dl.yarnpkg.com/debian/pubkey.gpg" rel="nofollow">https://dl.yarnpkg.com/debian/pubkey.gpg</a> | sudo apt-key add - &&
curl -fSsL <a href="https://deb.nodesource.com/setup_12.x" rel="nofollow">https://deb.nodesource.com/setup_12.x</a> | bash &&
apt-get install nodejs python3 make gcc build-essential<p>COPY . .<p>RUN npm install<p>RUN npm test<p>RUN BACKGROUND npm start<p>EXPOSE WEBSITE <a href="http://localhost:3000" rel="nofollow">http://localhost:3000</a><p>We charge a flat $42/mo/developer on our paid plan. Because it's a flat fee and not usage based, we're incentivized to make things as fast as possible: Our current margins come from a custom-built hibernating hypervisor that lets us avoid running "npm install" thousands of times per day.<p>We’ve upgraded the free tier to 5GB of memory for new installations this week. It’s perfect for personal projects or small MVPs where you’d like a powerful demo server that will build on every push and automatically hibernate when it’s not being used.<p>The easiest way to try out LayerCI is to follow our interactive tutorial: <a href="https://layerci.com/" rel="nofollow">https://layerci.com/</a> or look at the docs: <a href="https://layerci.com/docs/" rel="nofollow">https://layerci.com/docs/</a><p>We would love to hear your thoughts about CI/CD, staging, and what we’ve built!
Launch HN: LayerCI (YC S20) - Staging servers that act like (and replace) CI
Hi HN, Lyn & Colin here. We’re co-founders of LayerCI (<a href="https://layerci.com" rel="nofollow">https://layerci.com</a>), which gives you a modern DevOps experience (CI/CD & staging environments) with as little work as writing a Dockerfile.<p>Most teams need CI/CD (run the build and deploy every time a developer pushes) or staging (host a server with my app in it to share), but current approaches always have at least one of these problems:<p>- Simplistic (only run unit tests)<p>- Slow (wait 10 minutes to run the same repetitive setup steps like "npm install")<p>- Complex (cache keys, base images, a slack channel to reserve staging servers, …)<p>We’ve spent over a year iterating with our customers to build a product that solves all of these problems.<p>Our configuration files (Layerfiles) look like Dockerfiles, so regular developers can write and maintain them. Here's one that creates a staging server for create-react-app:<p>FROM vm/ubuntu:18.04<p>RUN curl -sS <a href="https://dl.yarnpkg.com/debian/pubkey.gpg" rel="nofollow">https://dl.yarnpkg.com/debian/pubkey.gpg</a> | sudo apt-key add - &&
curl -fSsL <a href="https://deb.nodesource.com/setup_12.x" rel="nofollow">https://deb.nodesource.com/setup_12.x</a> | bash &&
apt-get install nodejs python3 make gcc build-essential<p>COPY . .<p>RUN npm install<p>RUN npm test<p>RUN BACKGROUND npm start<p>EXPOSE WEBSITE <a href="http://localhost:3000" rel="nofollow">http://localhost:3000</a><p>We charge a flat $42/mo/developer on our paid plan. Because it's a flat fee and not usage based, we're incentivized to make things as fast as possible: Our current margins come from a custom-built hibernating hypervisor that lets us avoid running "npm install" thousands of times per day.<p>We’ve upgraded the free tier to 5GB of memory for new installations this week. It’s perfect for personal projects or small MVPs where you’d like a powerful demo server that will build on every push and automatically hibernate when it’s not being used.<p>The easiest way to try out LayerCI is to follow our interactive tutorial: <a href="https://layerci.com/" rel="nofollow">https://layerci.com/</a> or look at the docs: <a href="https://layerci.com/docs/" rel="nofollow">https://layerci.com/docs/</a><p>We would love to hear your thoughts about CI/CD, staging, and what we’ve built!
Launch HN: LayerCI (YC S20) - Staging servers that act like (and replace) CI
Hi HN, Lyn & Colin here. We’re co-founders of LayerCI (<a href="https://layerci.com" rel="nofollow">https://layerci.com</a>), which gives you a modern DevOps experience (CI/CD & staging environments) with as little work as writing a Dockerfile.<p>Most teams need CI/CD (run the build and deploy every time a developer pushes) or staging (host a server with my app in it to share), but current approaches always have at least one of these problems:<p>- Simplistic (only run unit tests)<p>- Slow (wait 10 minutes to run the same repetitive setup steps like "npm install")<p>- Complex (cache keys, base images, a slack channel to reserve staging servers, …)<p>We’ve spent over a year iterating with our customers to build a product that solves all of these problems.<p>Our configuration files (Layerfiles) look like Dockerfiles, so regular developers can write and maintain them. Here's one that creates a staging server for create-react-app:<p>FROM vm/ubuntu:18.04<p>RUN curl -sS <a href="https://dl.yarnpkg.com/debian/pubkey.gpg" rel="nofollow">https://dl.yarnpkg.com/debian/pubkey.gpg</a> | sudo apt-key add - &&
curl -fSsL <a href="https://deb.nodesource.com/setup_12.x" rel="nofollow">https://deb.nodesource.com/setup_12.x</a> | bash &&
apt-get install nodejs python3 make gcc build-essential<p>COPY . .<p>RUN npm install<p>RUN npm test<p>RUN BACKGROUND npm start<p>EXPOSE WEBSITE <a href="http://localhost:3000" rel="nofollow">http://localhost:3000</a><p>We charge a flat $42/mo/developer on our paid plan. Because it's a flat fee and not usage based, we're incentivized to make things as fast as possible: Our current margins come from a custom-built hibernating hypervisor that lets us avoid running "npm install" thousands of times per day.<p>We’ve upgraded the free tier to 5GB of memory for new installations this week. It’s perfect for personal projects or small MVPs where you’d like a powerful demo server that will build on every push and automatically hibernate when it’s not being used.<p>The easiest way to try out LayerCI is to follow our interactive tutorial: <a href="https://layerci.com/" rel="nofollow">https://layerci.com/</a> or look at the docs: <a href="https://layerci.com/docs/" rel="nofollow">https://layerci.com/docs/</a><p>We would love to hear your thoughts about CI/CD, staging, and what we’ve built!
Show HN: Watchpoints, an easy to use watchpoints equivalent library for Python
Show HN: Watchpoints, an easy to use watchpoints equivalent library for Python
Show HN: Collection of deep learning implementations with side-by-side notes
Show HN: Collection of deep learning implementations with side-by-side notes
Show HN: Collection of deep learning implementations with side-by-side notes
Show HN: Wallstreetbets Sentiment Past 24 Hours
Show HN: SleekDB – A NoSQL Database made using PHP
Show HN: SleekDB – A NoSQL Database made using PHP
Show HN: krunvm – Create and run lightweight VMs from OCI images
Show HN: krunvm – Create and run lightweight VMs from OCI images
Launch HN: InpharmD (YC W21) – curated drug information for doctors
Hi HN-<p>My name is Ashish, and I’m the CEO/ co founder of InpharmD (<a href="https://inpharmd.com" rel="nofollow">https://inpharmd.com</a>). We take questions from doctors and return curated, evidence - based answers.<p>I was a clinical pharmacist offering a remote service from a University for 10 years. Ask us anything, we begged, and our team of pharmacists, residents, and students would look it up, get through the paywalls, and provide the answer.<p>I passed out business cards around local hospitals. They were lost over time.<p>Then I passed out business cards with magnets. They stuck around, but there aren’t that many places in the hospital with the magnetic surfaces.<p>Eventually, people stored our number, but we’d ask so many questions when they called, they couldn’t ask theirs: who are you, where are you calling from, what’s your email, spell it, etc, etc, etc. Often, they’d hang up on us, and I don’t blame them. The average doctor now sees five patients an hour.<p>I realized I wasn’t alone, and hundreds of other academicians, all leading their own teams, had the same problem. So, we formed a network and interviewed hundreds of our customers about how they’d ideally interact with us. What we needed to build was simple: one touch request.<p>My co - founder Tulasee built that and since, we learned that AI can transcribe PDFs faster (but not yet better) than our pharmacists. We started with 5,000 of our own study abstracts, assigned weights for corresponding content in their respective PDFs, and now we continuously reassign the weights until the algorithm can completely make our own abstracts. Our latest test revealed 94% accuracy against a matched human control, but with medical information, this will need to be 100% before we can rely on it.<p>We think Watson was a missed opportunity, so we called our algorithm Sherlock. We’re launching a partnership with the American Society of Health-System Pharmacists® (ASHP- <a href="https://ashp.org" rel="nofollow">https://ashp.org</a>), using their database of 1,300 vetted drug monographs, so Sherlock can field questions at the point of care.<p>We’ve been fortunate to find early adopter health systems to pay for our service: WellStar, Ochsner, University of Maryland, Georgia DPH, and St Francis. We’re typically compared to the cost of their healthcare providers manually searching, and we end up cheaper.<p>We love this community and we’d welcome your ideas/ experiences/ feedback on what we’re building!
Launch HN: InpharmD (YC W21) – curated drug information for doctors
Hi HN-<p>My name is Ashish, and I’m the CEO/ co founder of InpharmD (<a href="https://inpharmd.com" rel="nofollow">https://inpharmd.com</a>). We take questions from doctors and return curated, evidence - based answers.<p>I was a clinical pharmacist offering a remote service from a University for 10 years. Ask us anything, we begged, and our team of pharmacists, residents, and students would look it up, get through the paywalls, and provide the answer.<p>I passed out business cards around local hospitals. They were lost over time.<p>Then I passed out business cards with magnets. They stuck around, but there aren’t that many places in the hospital with the magnetic surfaces.<p>Eventually, people stored our number, but we’d ask so many questions when they called, they couldn’t ask theirs: who are you, where are you calling from, what’s your email, spell it, etc, etc, etc. Often, they’d hang up on us, and I don’t blame them. The average doctor now sees five patients an hour.<p>I realized I wasn’t alone, and hundreds of other academicians, all leading their own teams, had the same problem. So, we formed a network and interviewed hundreds of our customers about how they’d ideally interact with us. What we needed to build was simple: one touch request.<p>My co - founder Tulasee built that and since, we learned that AI can transcribe PDFs faster (but not yet better) than our pharmacists. We started with 5,000 of our own study abstracts, assigned weights for corresponding content in their respective PDFs, and now we continuously reassign the weights until the algorithm can completely make our own abstracts. Our latest test revealed 94% accuracy against a matched human control, but with medical information, this will need to be 100% before we can rely on it.<p>We think Watson was a missed opportunity, so we called our algorithm Sherlock. We’re launching a partnership with the American Society of Health-System Pharmacists® (ASHP- <a href="https://ashp.org" rel="nofollow">https://ashp.org</a>), using their database of 1,300 vetted drug monographs, so Sherlock can field questions at the point of care.<p>We’ve been fortunate to find early adopter health systems to pay for our service: WellStar, Ochsner, University of Maryland, Georgia DPH, and St Francis. We’re typically compared to the cost of their healthcare providers manually searching, and we end up cheaper.<p>We love this community and we’d welcome your ideas/ experiences/ feedback on what we’re building!
Launch HN: InpharmD (YC W21) – curated drug information for doctors
Hi HN-<p>My name is Ashish, and I’m the CEO/ co founder of InpharmD (<a href="https://inpharmd.com" rel="nofollow">https://inpharmd.com</a>). We take questions from doctors and return curated, evidence - based answers.<p>I was a clinical pharmacist offering a remote service from a University for 10 years. Ask us anything, we begged, and our team of pharmacists, residents, and students would look it up, get through the paywalls, and provide the answer.<p>I passed out business cards around local hospitals. They were lost over time.<p>Then I passed out business cards with magnets. They stuck around, but there aren’t that many places in the hospital with the magnetic surfaces.<p>Eventually, people stored our number, but we’d ask so many questions when they called, they couldn’t ask theirs: who are you, where are you calling from, what’s your email, spell it, etc, etc, etc. Often, they’d hang up on us, and I don’t blame them. The average doctor now sees five patients an hour.<p>I realized I wasn’t alone, and hundreds of other academicians, all leading their own teams, had the same problem. So, we formed a network and interviewed hundreds of our customers about how they’d ideally interact with us. What we needed to build was simple: one touch request.<p>My co - founder Tulasee built that and since, we learned that AI can transcribe PDFs faster (but not yet better) than our pharmacists. We started with 5,000 of our own study abstracts, assigned weights for corresponding content in their respective PDFs, and now we continuously reassign the weights until the algorithm can completely make our own abstracts. Our latest test revealed 94% accuracy against a matched human control, but with medical information, this will need to be 100% before we can rely on it.<p>We think Watson was a missed opportunity, so we called our algorithm Sherlock. We’re launching a partnership with the American Society of Health-System Pharmacists® (ASHP- <a href="https://ashp.org" rel="nofollow">https://ashp.org</a>), using their database of 1,300 vetted drug monographs, so Sherlock can field questions at the point of care.<p>We’ve been fortunate to find early adopter health systems to pay for our service: WellStar, Ochsner, University of Maryland, Georgia DPH, and St Francis. We’re typically compared to the cost of their healthcare providers manually searching, and we end up cheaper.<p>We love this community and we’d welcome your ideas/ experiences/ feedback on what we’re building!
Launch HN: InpharmD (YC W21) – curated drug information for doctors
Hi HN-<p>My name is Ashish, and I’m the CEO/ co founder of InpharmD (<a href="https://inpharmd.com" rel="nofollow">https://inpharmd.com</a>). We take questions from doctors and return curated, evidence - based answers.<p>I was a clinical pharmacist offering a remote service from a University for 10 years. Ask us anything, we begged, and our team of pharmacists, residents, and students would look it up, get through the paywalls, and provide the answer.<p>I passed out business cards around local hospitals. They were lost over time.<p>Then I passed out business cards with magnets. They stuck around, but there aren’t that many places in the hospital with the magnetic surfaces.<p>Eventually, people stored our number, but we’d ask so many questions when they called, they couldn’t ask theirs: who are you, where are you calling from, what’s your email, spell it, etc, etc, etc. Often, they’d hang up on us, and I don’t blame them. The average doctor now sees five patients an hour.<p>I realized I wasn’t alone, and hundreds of other academicians, all leading their own teams, had the same problem. So, we formed a network and interviewed hundreds of our customers about how they’d ideally interact with us. What we needed to build was simple: one touch request.<p>My co - founder Tulasee built that and since, we learned that AI can transcribe PDFs faster (but not yet better) than our pharmacists. We started with 5,000 of our own study abstracts, assigned weights for corresponding content in their respective PDFs, and now we continuously reassign the weights until the algorithm can completely make our own abstracts. Our latest test revealed 94% accuracy against a matched human control, but with medical information, this will need to be 100% before we can rely on it.<p>We think Watson was a missed opportunity, so we called our algorithm Sherlock. We’re launching a partnership with the American Society of Health-System Pharmacists® (ASHP- <a href="https://ashp.org" rel="nofollow">https://ashp.org</a>), using their database of 1,300 vetted drug monographs, so Sherlock can field questions at the point of care.<p>We’ve been fortunate to find early adopter health systems to pay for our service: WellStar, Ochsner, University of Maryland, Georgia DPH, and St Francis. We’re typically compared to the cost of their healthcare providers manually searching, and we end up cheaper.<p>We love this community and we’d welcome your ideas/ experiences/ feedback on what we’re building!
Launch HN: Arpio (YC W21) – Protect your business from AWS outages, ransomware
Hello HN! We’re Shaw [sterwill] and Doug [doug_neumann] and today we’re very excited to share Arpio with you (<a href="https://arpio.io" rel="nofollow">https://arpio.io</a>). Arpio is a SaaS that protects AWS environments from downtime by making it easy to recover from outages, ransomware, cyber-attacks, and human error.<p>What that means is that when critical AWS services go down (like the Kinesis outage in November [0]), Arpio can launch identical workloads in a healthy region. Or if a bad actor does bad things in an AWS environment (like Codespaces [1] or Webex Teams [2]), Arpio can quickly restore everything to an alternate AWS account.<p>Our story goes back to the big S3 outage of 2017. In February that year an AWS employee made a typo at the command line, and inadvertently took down much of AWS’s Northern Virginia region. That outage lasted 5 hours, and we were among the thousands of companies impacted.<p>All outages suck, but the timing on this one was particularly bad for our business. And worse, we had no control -- all we could do was wait for Amazon to get us back online. As you can imagine, the execs weren’t exactly happy about that...<p>With Arpio, we’re building the solution we wish we’d had back then. Arpio maintains an exact replica of your production AWS environment in a different region (that you choose) and optionally in a locked-down AWS account (that you own).<p>This recovery environment includes your data and your infrastructure, and it’s updated frequently as your environment evolves. It’s also checkpointed, so you can roll back to a prior state to recover from data corruption or ransomware. And when you aren’t using it, it’s dormant, so you don’t have to pay AWS for resources you don’t need.<p>But when you need it (or want to test it), Arpio can have it up and running in a few minutes.<p>Disaster recovery is usually custom-engineered for a given workload. With Arpio, we’re building a general-purpose solution that works for most AWS workloads. We handle the complexity ensuring every route table is rewired, every security group rule is correct, every private IP address is preserved, and every database hostname is aliased. And handling that complexity makes Arpio simple to implement. We can often get new customers onboarded in under an hour.<p>Arpio works today with EC2, EBS, RDS, ECS, ECR, ELB, VPC, IAM, ACM, Autoscaling, Cognito, ElastiCache, and CloudWatch. We’re delivering Beanstalk and EFS support in the coming weeks. If we don’t yet support your environment, drop a comment below - we’d love to get your feedback on what we should build next.<p>We encourage you to take it for a spin. Or if you’re up for a chat, send me a note (doug[at]arpio.io) - I’d love to walk you through it in person.<p>So, HN, what do you think? We’re excited to get your feedback!<p>Thanks,
Shaw & Doug<p>[0] <a href="https://aws.amazon.com/message/11201/" rel="nofollow">https://aws.amazon.com/message/11201/</a>
[1] <a href="https://news.ycombinator.com/item?id=7909791" rel="nofollow">https://news.ycombinator.com/item?id=7909791</a>
[2] <a href="https://news.ycombinator.com/item?id=24319293" rel="nofollow">https://news.ycombinator.com/item?id=24319293</a>