Live data from Hacker News

Ask HN: How do you install developer tools on a fresh system?

news.ycombinator.com

91–100 of 129 posts

Re: Ask HN: How do you install developer tools on a fresh system?

#91
post #64

Earlier quoted context omitted.

Have you tried the beta for OSX or Windows yet? I haven't needed vagrant in the slightest since it was released.

If they can get xhyve based VMs stable when co-existing with VirtualBox, then yeah, that will go a long way towards replacing Vagrant for me. That said, I'm not a huge fan of Docker's feature churn; having to re-install, reconfigure, and re-learn tooling that is central to my workflow every other month gets old pretty quickly.

That's currently blocker #1 for us when it comes to the new Docker for Mac/Win. VirtualBox works as a nice abstraction layer on top of 3 OSes (Mac/Win/Linux) which simplifies things with Vagrant. Unfortunately it seems VirtualBox has been in maintenance mode as of lately so that might have contributed to Docker's decision to go with HyperV/xhyve.

Re: Ask HN: How do you install developer tools on a fresh system?

#92

I don't do fresh installs very often, but when I do, it's generally because I want it to be a genuine fresh install. As such, I don't install a tool until I need it. I find that tools I once thought I absolutely needed are not tools or libraries that I use anymore. I have three exceptions to this: Vim (my editor of choice), dotfiles (which I store in a git repository and put in place using stow, installed via a simpl…

I hadn't come across stow before. I might integrate that into my dotfiles.

Right now I use a bash script I wrote to deploy my dotfiles into ~/, via symlink, including renaming existing files (after prompting the user).

I get what you mean about using that opportunity to do some spring cleaning. I find I need to do that to my Vim installation periodically too. I'll add a new plugin that looks like it will be useful, or add something for a new language or template system, then not use it enough to justify it.

Re: Ask HN: How do you install developer tools on a fresh system?

#93

As a rails developer, I've used and recommended https://github.com/thoughtbot/laptop :)

We've adapted this at 18F. It's not a fork but it is based on and inspired by Thoughtbot's original project. Strong recommend. https://github.com/18f/laptop

Re: Ask HN: How do you install developer tools on a fresh system?

#94
I use bash+rpm.

RPM's are insanely easy to create, and the work helps with deployment/version tracking on the end machine. For example I have an .spec that downloads a given version of codeIgniter, unzips it, tweaks some permissions, and then rolls it into an RPM and tosses it into a network accessible repo. The RPM has a pretty complete list of dependencies, so they automatically get pulled in.

So my devel script looks something like:

  cat  /etc/yum.repos.d/local-repo.repo
  [local-repo]
  name=local-repo
  baseurl=http://xxxx
  enabled=1
  gpgcheck=...
  EOF

  PACKAGES="codeigniter otherstuff"

  for PKG in $PACKAGES; do
   sudo yum install -y $PKG;
  done

Re: Ask HN: How do you install developer tools on a fresh system?

#95
post #17

I've found ansible to be okay at setting up my environment. I'm able to configure everything from my zsh themes, terminal font size, window manager shortcuts, thunderbird logins, and so forth. The playbook takes about 30 minutes to run and after that I have almost everything ready. Unfortunately I don't have a public GH repo I can point at as I don't want to expose everything I use to the internet. However the princi…

Have you considered using Gitlab? I really like GitHub, but can't justify the prices right now (just starting out in my career). But while Gitlab isn't as popular, or maybe quite as polished (though it's getting there fast), it does have free private repos. I've used this to store private data like this.

Check it out if you haven't already.

Re: Ask HN: How do you install developer tools on a fresh system?

#96
post #4

The question asks only about *nix systems, I assume, but it worth mentioning that there is a great tool for Windows too, just in case if someone needs it - https://chocolatey.org/

Automating from-scratch setup with chocolatey: http://www.boxstarter.org/

Re: Ask HN: How do you install developer tools on a fresh system?

#98
post #37

That's a very good reason to only install apps with a real package installer. On OSX, this is a no-brainer with brew[1] and brew cask[2] # On my old mac $ brew list $ brew cask list => then I save relevant parts for future references brew install npm brew install zsh brew cask install sublime-text brew cask install google-chrome brew cask install intellij-idea [1] http://brew.sh/ [2] https://caskroom.github.io/

>brew list Protip: "brew list" will list all installed packages, including dependencies, which you might not want. What you probably want is "brew leaves", where it lists all installed packages that are not dependencies of another installed package . This makes a difference in cases where a dependency is no longer needed in the latest version. On a related note, why does the majority of package managers make the comm…

For Ubuntu, look no further: http://askubuntu.com/a/492343/145754

Re: Ask HN: How do you install developer tools on a fresh system?

#99

I use a ShutIt script: https://github.com/ianmiell/shutit-home-server/blob/master/S... it's platform independent and automates the install of everything I need.

More info:

https://github.com/ianmiell/shutitfile/blob/master/README.md

https://github.com/ianmiell/shutitfile/blob/master/CheatShee...

http://ianmiell.github.io/shutit/

Re: Ask HN: How do you install developer tools on a fresh system?

#100
post #25

Question: why are you doing a fresh install? If you install everything through your package manager, you don't need a fresh install to clean things up. My operating system has lived through several different machine upgrades. I just do a `cp -a` to copy the files from one hard drive to another, set up the bootloader and go.

Theoretically that may be the case, but its far from reality.

It's not the same hard drive, but the files in /var/log/installer/ show I installed Ubuntu 10.10 on 24 October 2010. It's been upgraded since, and copied to a new drive at least once.

/etc/popularity-contest.conf has the same timestamp, so I'm curious whether Ubuntu (or Debian) keep any statistics on the lifetime of a system.

Post reply on HN