3 ms·

Sorry I'm not getting the main value prop from this. I'm mainly an ops person. Can you please explain what that service would look like?

by kim0 6y ago

jedieaston 6y ago
The host would prove that the source available online is the exact same code running on the instance, so you know that it wasn't modified by the developer/bad-guy before it went into production.
t0astbread 6y ago
Netlify (primarily) takes a git repo containing a program to generate a static site and turns that into a live running website that automatically updates when the generator repo changes. You don't have to think about configuration or security or updates and you don't have to maintain a server. Ideally this would be a service with the same ergonomics but the outcome isn't a hosted static website but a machine (somewhere in the cloud) running whatever the user wants. "Tedious" tasks like hardening, monitoring and upgrading (and redeploys) would be handled by the service provider, as opposed to the user. For people who like doing ops this might not sound appealing but developers (especially single devs and small teams) often just wanna focus on their app, not their ops, even more so when it comes to continous maintenance. Addendum: I think Laravel has some of this covered in their ecosystem with tools like Forge and Envoyer. But I've never tried any of them so I can't judge.
- battery_cowboy 6y ago
  Have you heard of platform as a service, like Heroku or gigalixr? That's exactly what that is, pretty much.
  - t0astbread 6y ago
    Oh so that's what that is! I always thought Heroku was just more expensive VPSes.
- manigandham 6y ago
  This is what Platform-as-a-service (PAAS) is and has been around for a long time. Google's Appengine, Heroku, and many others offer it. Since then we've seen "serverless" or functions-as-a-service (FAAS) which is just smaller bits of code (down to a single javascript function) but the same concept of everything else being managed by the provider. This is AWS Lambda, Cloudflare Workers, Google Cloud Functions, etc. The latest offerings now take a Dockerfile or container image that you build, which means you can run anything on any stack while the provider manages the rest. Google Cloud Run, AWS Fargate, Azure Container Instances, Fly.io, Zeit Now, etc.

Sorry I'm not getting the main value prop from this. I'm mainly an ops person. Can you please explain what that service would look like?

by kim0 6y ago

Sorry I'm not getting the main value prop from this. I'm mainly an ops person. Can you please explain what that service would look like?

jedieaston 6y ago

The host would prove that the source available online is the exact same code running on the instance, so you know that it wasn't modified by the developer/bad-guy before it went into production.

t0astbread 6y ago

Netlify (primarily) takes a git repo containing a program to generate a static site and turns that into a live running website that automatically updates when the generator repo changes. You don't have to think about configuration or security or updates and you don't have to maintain a server. Ideally this would be a service with the same ergonomics but the outcome isn't a hosted static website but a machine (somewhere in the cloud) running whatever the user wants. "Tedious" tasks like hardening, monitoring and upgrading (and redeploys) would be handled by the service provider, as opposed to the user. For people who like doing ops this might not sound appealing but developers (especially single devs and small teams) often just wanna focus on their app, not their ops, even more so when it comes to continous maintenance. Addendum: I think Laravel has some of this covered in their ecosystem with tools like Forge and Envoyer. But I've never tried any of them so I can't judge.

battery_cowboy 6y ago
Have you heard of platform as a service, like Heroku or gigalixr? That's exactly what that is, pretty much.
- t0astbread 6y ago
  Oh so that's what that is! I always thought Heroku was just more expensive VPSes.
manigandham 6y ago
This is what Platform-as-a-service (PAAS) is and has been around for a long time. Google's Appengine, Heroku, and many others offer it. Since then we've seen "serverless" or functions-as-a-service (FAAS) which is just smaller bits of code (down to a single javascript function) but the same concept of everything else being managed by the provider. This is AWS Lambda, Cloudflare Workers, Google Cloud Functions, etc. The latest offerings now take a Dockerfile or container image that you build, which means you can run anything on any stack while the provider manages the rest. Google Cloud Run, AWS Fargate, Azure Container Instances, Fly.io, Zeit Now, etc.