dumas + development   23

Caching best practices & max-age gotchas
How to get the most out of caching without nasty race conditions
browser  cache  http  webdev  development  django  via:davidgasperoni 
march 2017 by dumas
Overview · Phoenix
Web framework using Elixir (Erlang)
web  development 
march 2016 by dumas
Deadweight is a CSS coverage tool. Given a set of stylesheets and a set of URLs, it determines which selectors are actually used and reports which can be “safely” deleted.

Handy, and flexible:

deadweight -s styles.css -s ie.css index.html about.html
deadweight -s http://www.tigerbloodwins.com/index.css http://www.tigerbloodwins.com/
deadweight --root http://kottke.org/ -s '/templates/2009/css.php?p=mac' / /everfresh /about
cat styles.css | deadweight index.html

Via Trivium.
css  web  development  from google
september 2012 by dumas
Migrating from VMWare Fusion to VirtualBox: networking
In my previous post on migrating Windows 7 to VirtualBox there were a couple things missing on the networking configuration to make VirtualBox work the same way VMWare does by default.

In VMWare you can just connect to the ip of the guest, the host is by default configured with new virtual network adapters that will route the packages to the guest.

In VirtualBox however by default guests are configured with NAT to allow internet access from the guest through the host, but doesn’t allow connecting from the host to the guest directly, only assigning each port in the host that you want redirected to the guest (which is a PITA).

There are two options to achieve the same result that you had in VMWare:

Change the Network Adapter from NAT to Bridged Adapter. The drawback is that it needs to bridge to a specific hardware adapter (ethernet or airport), so it won’t work if you switch connections.
Add a new Host-Only Network Adapter. First, under VirtualBox global preferences – Network, add a Host-Only network. That will create a virtual interface vboxnet0 in your host machine, and you can customize the ip ranges and DHCP server. Then in the VM settings, under Network, enable Adapter 2 attached to Host-Only adapter and choose the virtual adapter, vboxnet0.

I chose option 2 and works as expected, I just need to connect to (the default assigned ip for the first VM) to get to the host.

The Windows 7 guest gets the ip from DHCP but for some reason it does not get the default gateway. Windows won’t let you assign the network to a Home or Work group without a default gateway, and therefore Windows Firewall will block incoming connections. The default gateway needs to be added by hand to the tcp/ip network configuration by hand (ie. and then you can assign the network to Home/Work and the firewall will allow traffic.
development  virtualbox  windows  from google
august 2011 by dumas

Copy this bookmark: