4 ms·

The flow in the video looks great. Easier to get into than Chef :) Hope it works as well (or better) Signed up for the beta

by collint 16y ago

fcoury 16y ago
Thanks for the words. StackFu, however, is not a replacement for Chef. With Chef you provision and manage your server's configuration, while StackFu is a social place for people to share "recipes" or stacks to be installed on your server. Ideally, this will be the place for linux savvy folks to share their scripts. And for people who just wants to get something installed (like WordPress) to go, search and easily get it up and running.
- timmorgan 16y ago
  Do you have plans for how scripts will be reviewed/flagged? I see from the video that one can see who else has deployed the script (with the assumption that a script deployed many times is most likely "safe"), but I would still feel a bit nervous about running a script blindly -- can one see the script code prior to hitting deploy? Edit to add: I'm certain you don't want to be liable for people hosing their server with a malicious script -- I hope you have plastered all over the place that these scripts are not reviewed for quality nor mal intent (unless of course, they are?). Another edit to add: I think this is a great idea! I could see myself using this -- I didn't mean to be such a negative nancy.
  - fcoury 16y ago
    This is a great point. Let me address your concerns: About being able to see the code: most definitely. Every "script" consist of zero or more requirements, one or more executions and zero or more validations. Each one is, in the end, a shell script with placeholders. You will be able see the scripts source code online and also "clone" the script to your account (not a git clone but an actual hard copy) and dump it locally using our ruby gem that talks to our API. We will record another screencast soon about how we create new scripts and how we upload them. About flagging scripts: we don't want to enforce any formal approval process, but we want the community to be able to flag scripts for malicious code. Another indication of quality may be the number of people who deployed it and/or watched it. We're open to suggestions and feedback on how we could improve it without making it an administrative burden. In the end, you're responsible for what you're installing in your server -- being it manually or through a script. Thanks for such a quality feedback. Please keep'em coming.
- collint 16y ago
  I suppose my point is that, even with the new hosted suff, chef doesn't have the a polished "wow, I feel like I didn't do anything" feel yet. If you can capture that you win in my book. If I run chef, or apt-get, or you-name-it through StackFu, then yes. StackFu is my replacement X. For me the best part is the github-esque "username" / "scriptname", and what I imagine will be the social components behind it. I think the real show-stopper would be a way to dump in my amazon/rackspace/etc. keys and get a real full stack in one click.

The flow in the video looks great. Easier to get into than Chef :) Hope it works as well (or better) Signed up for the beta

by collint 16y ago

The flow in the video looks great. Easier to get into than Chef :) Hope it works as well (or better) Signed up for the beta

fcoury 16y ago

Thanks for the words. StackFu, however, is not a replacement for Chef. With Chef you provision and manage your server's configuration, while StackFu is a social place for people to share "recipes" or stacks to be installed on your server. Ideally, this will be the place for linux savvy folks to share their scripts. And for people who just wants to get something installed (like WordPress) to go, search and easily get it up and running.

timmorgan 16y ago
Do you have plans for how scripts will be reviewed/flagged? I see from the video that one can see who else has deployed the script (with the assumption that a script deployed many times is most likely "safe"), but I would still feel a bit nervous about running a script blindly -- can one see the script code prior to hitting deploy? Edit to add: I'm certain you don't want to be liable for people hosing their server with a malicious script -- I hope you have plastered all over the place that these scripts are not reviewed for quality nor mal intent (unless of course, they are?). Another edit to add: I think this is a great idea! I could see myself using this -- I didn't mean to be such a negative nancy.
- fcoury 16y ago
  This is a great point. Let me address your concerns: About being able to see the code: most definitely. Every "script" consist of zero or more requirements, one or more executions and zero or more validations. Each one is, in the end, a shell script with placeholders. You will be able see the scripts source code online and also "clone" the script to your account (not a git clone but an actual hard copy) and dump it locally using our ruby gem that talks to our API. We will record another screencast soon about how we create new scripts and how we upload them. About flagging scripts: we don't want to enforce any formal approval process, but we want the community to be able to flag scripts for malicious code. Another indication of quality may be the number of people who deployed it and/or watched it. We're open to suggestions and feedback on how we could improve it without making it an administrative burden. In the end, you're responsible for what you're installing in your server -- being it manually or through a script. Thanks for such a quality feedback. Please keep'em coming.
collint 16y ago
I suppose my point is that, even with the new hosted suff, chef doesn't have the a polished "wow, I feel like I didn't do anything" feel yet. If you can capture that you win in my book. If I run chef, or apt-get, or you-name-it through StackFu, then yes. StackFu is my replacement X. For me the best part is the github-esque "username" / "scriptname", and what I imagine will be the social components behind it. I think the real show-stopper would be a way to dump in my amazon/rackspace/etc. keys and get a real full stack in one click.