So as I’m trying to sort out licensing at my job, I’m curious how everyone has done it. This should really be a poll, but everywhere I’ve worked has had a couple disconnected spreadsheets. Is there a reasonable solution without creating your own database, or going with some large companies enterprise asset tracking software?
Recent Posts
- Stubbing class constants with rspec and Ruby
- Downloading All The Github Repositories
- Generating entropy in the cloud
- Disabling Firefox shortcuts on OS X
- Recreating the Opscode Chef validation key
- require-rubygems.overrides and gem2deb 0.2.2
- locale errors on debian
- Creating a Debian sid emi for Eucalyptus
- LVM errors with sbuild
- munin-cgi-graph with fcgid on ubuntu lucid
Archives
What I'm Doing...
- @tomasczt dude, did you see that commercial? Broderick? Brodercik? in reply to tomasczt 8 hrs ago
- @cemerick source dependencies? -- Each cookbook must list its dependencies in its metadata. Knife can/will walk these for you. in reply to cemerick 10 hrs ago
- @cemerick @opscode I'm not familiar with Pallet. Commenters do not sound familiar with current versions of Chef or common knife workflows. in reply to cemerick 11 hrs ago
- More updates...
Posting tweet...
Powered by Twitter Tools
0 Responses to “License Management”