Chocolatey & Boxstarter, program management for windows

acidie

A=A
May 27, 2008
1,063
33
0
Chocolatey

Chocolatey NuGet is a Machine Package Manager, somewhat like apt-get, but built with Windows in mind.

You install the command line/gui and then use it to install/update/remove programs on your pc.

It's cool and extremely useful, but that doesn't make my cock hard, it only gives me half a chub.

Boxstarter

Repeatable, reboot resilient windows environment installations made easy using Chocolatey packages.

When its time to repave either bare metal or virtualized instances, locally or on a remote machine, Boxstarter can automate both trivial and highly complex installations.

Boxstarter on the other hand does give me full wood. With Boxstarter you create a deployment/install script of programs from Chocolatey and it will go off and install them on the machine while handling reboots, configurations setting, etc for you.

Basically if you have a set of programs you need installed after a format or on every computer you use, you create a script and when you need to setup a pc, you execute the script and go do something more productive with your time while Boxstarter handles it all for you.
 


Or you can just use LINUX with a quick bash script for deployment of additional servers. That works too.
 
Or, y'know...

QrMU6tO.jpg
 
camelCase variable names isn't pep8 compatible. also, i and numberofLines seems like a bunch of bugs waiting to happen, why not:

for form_data, proxy in zip(file_data(), proxy_data()): ?

Then do username, email = form_data.split(':')
 
camelCase variable names isn't pep8 compatible. also, i and numberofLines seems like a bunch of bugs waiting to happen, why not:

for form_data, proxy in zip(file_data(), proxy_data()): ?

Then do username, email = form_data.split(':')

i have problems if i don't assign variable names to the functions, it's a requests thing, sometimes it works sometimes it doesn't for whatever reason.

also i already tried a for loop but it was being FUCKED. i'll try it the way you said it but i've always had the best results with a while loop. the amount of lines is enumerated beforehand and not while the process is running so it's fairly stable. i'm also not making mass accounts, just enough for the day and switching them out when they die.
 
do you detect if an apt-get / yum install fails in deployment?

Yes, that's why God invented logging.

New CentOS box, vanilla install. One bash script installs all necessary packages, configures them as needed, hardens servers in terms of generating SSH keys, IP restrictions, etc. Then downloads the latest tarball from backup server, unpacks it, creates & imports databases, and sets everything else up.

Obviously, everything that happens is logged. If there's an issue, we'll know about it, and handle it manually.

How else do you propose we do this?