WEBCode.run Reviews

Rancher Reviews

WEBCode.run mentions (5)

• Blog-cells: Interactive code cells for static sites

  Oh this would be such a good fit for my dream of serving federated backend code from web readable hosting https://webcode.run/. - Source: Hacker News / over 1 year ago

• WICG/direct-sockets: Direct Sockets API for the web platform

  This would be so amazing. In order to access most vanilla services like redis, postgres etc. You need to deploy a bridge https://github.com/zquestz/ws-tcp-proxy -- somewhat abandoned at this point but it is still running), and a big problem with the approach was the web's inability to make TCP connections. - Source: Hacker News / about 2 years ago

• Show HN: I made a local development, debugging and hotreload tool for AWS Lambda

  Yeah, you are right. I made https://webcode.run also for this reason (also hot code reload and debugging but for JavaScript computational notebooks). - Source: Hacker News / over 2 years ago

• I Miss the Programmable Web

  This was why I created https://webcode.run the elimination of all tooling and a fast development loop even for backend. - Source: Hacker News / almost 3 years ago

• WebAssembly: The New Kubernetes?

  I am building a compute layer for Observablehq which enables services to brought up using nothing other than a web browser. It's a bit too soon to call it a K8s replacement but the motivation was the complexity and laggyness of bringing up services on cloud or k8s. The WEB + on demand infrastructure is the distributed replacement of K8S https://webcode.run/ WEBCode is about eliminating environments and the... - Source: Hacker News / over 3 years ago

Rancher mentions (24)

• Terraform code for kubernetes on vsphere?

  I don't know in which extend you plan to use Kubernetes in the future, but if it is aimed to become several huge production clusters, you should looks into Apps like Rancher: https://rancher.com. Source: over 2 years ago

• I want to provide some free support for community, how should I start?

  But I think once you have a good understanding of K8S internal (components, how thing work underlying, etc.), you can use some tool to help you provision / maintain k8s cluster easier (look for https://rancher.com/ and alternatives). Source: over 2 years ago

• Don't Use Kubernetes, Yet

  A few years, I would have said no. Now, I'm cautiously optimistic about it. Personally, I think that you can use something like Rancher (https://rancher.com/) or Portainer (https://www.portainer.io/) for easier management and/or dashboard functionality, to make the learning curve a bit more approachable. For example, you can create a deployment through the UI by following a wizard that also offers you... - Source: Hacker News / almost 3 years ago

• Building an Internal Kubernetes Platform

  Alternatively, it is also possible to use a multi-cloud or hybrid-cloud approach, which combines several cloud providers or even public and private clouds. Special tools such as Rancher and OpenShift can be very useful to run this type of system. - Source: dev.to / almost 3 years ago

• Five Dex Alternatives for Kubernetes Authentication

  Rancher provides a Rancher authentication proxy that allows user authentication from a central location. With this proxy, you can set the credential for authenticating users that want to access your Kubernetes clusters. You can create, view, update, or delete users through Rancher’s UI and API. - Source: dev.to / almost 3 years ago