GitLab Repository Management (book)

imageI’ve been reading GitLab Repository Management lately [disclaimer: courtesy of packtpub]. It’s a nice book, well organised and easy to follow instructions to setup your environment, plus some basic details for a complete workflow. The book is very nice and well worth it. If I had to choose weak points I would say:

  • More examples. Never enough of these.
  • More on Hooks. I’m a bit biased here, ok. I’ve had some troubles with post-receive hook (somewhere between gitlab 4 and 6 the default post-receive hook was lost in newly created repos, don’t know who to blame here, but I expected the book to acknowledge the fact, at least, when mentioning the post-receive hook).
  • More info on sidekiq. Sorry, any info on background processes, there is none.

As I said, the book is very worth reading. Good work and thanx for sending the book for review!

Sass, Compass and source maps in Webkit Devtools

If you want to use the awesome source maps for Sass in Devtools, you will have to:

  1. Go to chrome://flags/ and Enable Developer Tools experiments, then restart Chrome.
  2. Open Devtools and check Enable source maps in General tab and Support for Sass in Experimental tab.
  3. Download latest Sass from the console: gem install sass --pre (you might need sudo)
  4. Just adding sass_options = {:sourcemap => true} to config.rb in Compass won’t work (just yet) and you can even get Compass conflicts with the aforementioned Sass alpha version. In my case, Compass 0.12.2 (Alnilam) does not get on very well with Sass 3.3.0.alpha.103 (Bleeding Edge), though it might be some other gem conflict.
  5. For that reason, we will have to watch changes using Sass directly, using sourcemap option: sass --watch --sourcemap sources/compass:public/css which generates a .map file for each source. This is the information Devtools will use to let you trace/edit original Sass files directly in the browser.