jtimberman

8 ms·

1.
by jtimberman 1y ago
The Chef-branded distribution is still built from the same open source repositories that the CINC project is built from; it isn't proprietary. It has an additional EULA that requires people to accept and thus [presumably] pay for. It&#
2.
Single Sign On – Okta vs. AWS(compliance.dev)
1 points by jtimberman 5y ago|0 comments
3.
VPN or VPC: Which One Do You Need?(compliance.dev)
3 points by jtimberman 5y ago|0 comments
4.
Intro to JIT Access(compliance.dev)
5 points by jtimberman 5y ago|1 comments
5.
by jtimberman 14y ago
With Chef 11 Server, the CouchDB component is removed for PostgreSQL. RabbitMQ is still there. Opscode provides a single package with everything above libc required to run the server. http://www.opscode.com/chef/install - "Chef Server"
6.
Process Supervision is a Solved Problem(jtimberman.housepub.org)
2 points by jtimberman 14y ago|0 comments
7.
by jtimberman 14y ago
"ruby_block" is a Chef resource that allows you to execute your favorite ruby code as a separate resource. You can always drop to regular, plain Ruby, anywhere you like.
8.
by jtimberman 14y ago
What the generated rayburst.sh script does: 1. Writes out configuration for the chef client. 2. Generates a node on the chef server with the specified "run list" (recipes selected in the rayburst site). 3. Install Ruby and Chef RubyGem 4. R
9.
by jtimberman 14y ago
If you write such awesome well tested code you won't mind being primary on-call to support it, since it won't break and you won't get paged.
10.
MultiVM Vagrantfile for Chef(jtimberman.housepub.org)
14 points by jtimberman 15y ago|0 comments
11.
by jtimberman 15y ago
I never said this is a security vulnerability in Rails. I said it is a bug (and a serious one). A bug, as you may be aware, is a mistake, fault, failure, problem or other unintended or surprising behavior in software. See updates to my post
12.
by jtimberman 15y ago
My point is that Rails does not take the high road of providing better, sane, secure defaults for people to build their applications. While the proposed solutions in the issues I linked to were denied, it doesn't mean there shouldn't be so
13.
by jtimberman 15y ago
1. Yeah, the stop-gap "solution" is to white list a number of attributes in order to reduce the data set, because in the most common use case we see, there's only a few attributes that people actually care about in the chef-client context
14.
by jtimberman 15y ago
Cookbooks are accessible via your private key, which Opscode Hosted Chef does not have a copy. You can choose to encrypt the contents of a data bag using a locally generated (on your hardware, nothing we control) key.
15.
by jtimberman 15y ago
1. We are working on making the search more performance and use less memory. 2. Chef definitely does not discourage declarative configuration. Chef recipes include declarative resource for configuring your infrastructure. Since recipes are
16.
by jtimberman 15y ago
(disclosure, I work for Opscode.) To be clear, those dependencies are required for running your own open source chef server. You can use chef without the server, as chef-solo, or let Opscode run it for you in the form of Opscode Hosted Chef
17.
by jtimberman 16y ago
Hi! Actually in an upcoming release of Chef, you'll be able to do exactly that - manage Rackspace cloud nodes with the knife command-line tool. What that means is, you can launch new RS Cloud servers with knife, passing in the validation ce