- Resource Collections
- Tutorials
- Opinions
- GUI
- VagrantX: the Vagrant GUI client for Mac OS X
- Vagrant Manager for OS X
- smurfy / vagrantGui: Written with QT currently working and tested on: Windows, Linux, MacOsx
- Docker Host
- Images
Attention: the list was moved to
https://github.com/dypsilon/frontend-dev-bookmarks
This page is not maintained anymore, please update your bookmarks.
| #!/usr/bin/env bash | |
| # ~/.macos — https://mths.be/macos | |
| # Ask for the administrator password upfront | |
| sudo -v | |
| # Keep-alive: update existing `sudo` time stamp until `.macos` has finished | |
| while true; do sudo -n true; sleep 60; kill -0 "$$" || exit; done 2>/dev/null & |
Strongly opinionated set of guides to quickly setup OS X Mavericks for web development. By default OS X hides stuff that normal people don't need to see. These settings are better defaults for developers.
I don't want: any sounds, annoying confirmation dialogs, hidden extensions, superflous animations, unnecessary things running like Dashboard, Notification center or Dock(Alfred/spotlight works better for me).
These are my opinions. Read this document through and pick up the good parts to your preferences.
| --- | |
| ip: "192.168.10.10" | |
| memory: 2048 | |
| cpus: 1 | |
| authorize: ~/.ssh/id_rsa.pub | |
| keys: | |
| - ~/.ssh/id_rsa |
| // paths | |
| var combine_dir = 'resources/assets'; | |
| var build_dir = 'resources/assets/build'; | |
| var less_file = 'main'; | |
| var less_output = combine_dir + '/css'; | |
| // set scripts to combine | |
| var scripts = [ | |
| 'vendor/jquery/jquery.js', | |
| 'js/main.js' |
| echo 'export PATH=$HOME/local/bin:$PATH' >> ~/.bashrc | |
| . ~/.bashrc | |
| mkdir ~/local | |
| mkdir ~/node-latest-install | |
| cd ~/node-latest-install | |
| curl http://nodejs.org/dist/node-latest.tar.gz | tar xz --strip-components=1 | |
| ./configure --prefix=~/local | |
| make install # ok, fine, this step probably takes more than 30 seconds... | |
| curl https://www.npmjs.org/install.sh | sh |
NOTE I'm trying to find the most optimal fav/touch icon setup for my use-cases. Nothing new here. Read Mathias Bynens' articles on re-shortcut-icon and touch icons, a FAQ or a Cheat Sheet for all the details.
I'd like to hear how you approach this: @valuedstandards or comment on this gist.
You have to include a boatload of link elements pointing to many different images to provide (mobile) devices with a 'favicon' or 'touch icon':