gscho

Doesn't that create an opportunity for competition?

I think you already answered the question. You don't need to introduce docker cli, docker daemon, a container registry, etc. Not saying theres anything wrong with docker but having options for application packaging is nice!

I only just discovered foreign data wrappers today but it seems like you can write these in python though right? Might be easier than using Go to interface with C.

This is really cool. I had not heard of Foreign Data Wrappers for Postgres before! Are these used in production commonly or more of a toy thing?

> Also have a look at community cookbooks, most stuff is very old.

A lot of the functionality offered by community cookbooks made it way into the core DSL. Most community cookbooks for installing applications were abandoned for other approaches though.

>I think chef have totally killed their community by doing that stupid EULA move.

I agree. Seems like they tried to move to the "redhat model" without having a centos style OSS version. CINC has come along and filled that gap: https://cinc.sh/

Heroku IS the netlify for backends. This product has good intentions though. Good luck!

> Intentionally murdering possibly thousands of people (or tens of thousands? or what, who knows?!) for some assumed political gain is absolutely, 100% an unreasonable decision for any human to make. Intentionally delaying a vaccine would certainly be a crime, no? Not to mention absolutely abhorrent and completely evil.

You mean delaying the announcement of a vaccine. They didn't delay the process.

What would be cool is a command line util that you could pipe the script to for a safety inspection.

Something like: curl https://ransomeware-encryptor.example.com | script-checker | sh

Can you explain why this is so unacceptable? Couldn't you inspect the contents at the url before you executed the command? What I've seen in some cases is, run the curl command to download the file and then execute it. I don't see much difference. This is a serious question, not arguing that this is the best way.

After reading through some examples, I came away with the same thought. I hope that the roadmap extends this into the CI space further!

We've resolved the issue with all 3 providers, thank you!

Just a quick update. We have disabled oAuth2 logins (Github, GitLab and BitBucket) temporarily while we update our configuration settings.

None taken! This is great feedback.

Thank you for catching this. We are resolving this now

Thanks for the question! Currently you can view what has changed on the pipeline executions page. Having a pre-deployment planning phase is on the roadmap as well.

Hi! ShuttleOps allows you to create workflows for deploying to Kubernetes without writing YAML manifest files. In that way you could consider it a visual/gui for the terraform kubernetes provider, sure!

Supporting pre-existing Helm Charts and k8s manifests as artifacts is still on the roadmap, and that needs to be achieved first before we can achieve a GitOps philosophy like Weave Cloud.

Ps: Hofstadter looks cool!

Hi! Greg from ShuttleOps here. We currently do not support import of existing YAML and helm manifests but that is certainly on our roadmap

...and you need to use their SaaS to make it work, no?

You can't just say helm is garbage without saying why.

Let's all move to serverless!

Moment.js https://momentjs.com/docs/#/-project-status/

I really enjoy using this product for creating architecture diagrams! I would never use it to creat budgets though. I hope it expands to other clouds and frameworks and then I would pay for it over lucidchart.

Self plug: I wrote a simple web app in the same vain as jsonlint and yamllint for toml files. https://toml-lint.com

(There's more than one way to do it)

If everyone thought like this there would only be one language that everyone used. Writing software is creative.

If your 10th clause is an unless then you're using it wrong. I agree that unless and the right hand assignment can be used incorrectly but that's not a reason to omit the feature :)

Perhaps they are looking at Habitat which is a cross-platform package manager that competes with Chocolatey somewhat.

We currently use habitat in production on VMs and have been happy with it.

It helped us solve a few pain points with deploying to VMs:

- dependencies are packaged and shipped with you app (no apt get install) so dev and prod environments are the same - local development happens against a docker container that contain all our prod services running inside of it (redis, postgres, Kafka, etc.) - built in CD and rollbacks via deployment channels

Concourse is a great CI tool. Sounds like the real issue was a lack of understanding how it works. Yes, each step in a pipeline is a container but you can put all logic in one container if you wanted, not just a lint command.