From 1cc31530c598905ae99d230ed0b84765b61311ea Mon Sep 17 00:00:00 2001 From: Ryan Bigg Date: Sun, 22 May 2016 11:53:42 +1000 Subject: [PATCH] MTWR 2nd ed post --- ...ltitenancy-with-rails-2nd-edition.markdown | 24 ++ .../index.html | 58 +++ _site/atom.xml | 112 ++---- _site/blogography.html | 2 + _site/index.html | 329 +----------------- 5 files changed, 127 insertions(+), 398 deletions(-) create mode 100644 _posts/2016-05-22-multitenancy-with-rails-2nd-edition.markdown create mode 100644 _site/2016/05/multitenancy-with-rails-2nd-edition/index.html diff --git a/_posts/2016-05-22-multitenancy-with-rails-2nd-edition.markdown b/_posts/2016-05-22-multitenancy-with-rails-2nd-edition.markdown new file mode 100644 index 000000000..a5e941cf8 --- /dev/null +++ b/_posts/2016-05-22-multitenancy-with-rails-2nd-edition.markdown @@ -0,0 +1,24 @@ +--- +wordpress_id: RB-372 +layout: post +title: Multitenancy with Rails 2nd Edition +--- + +[Multitenancy with Rails 2nd edition](https://leanpub.com/multi-tenancy-rails-2/c/fin) is now "content complete". I have now finished doing the majority of the work on this book and all that is left is to go through it and "proof" it. + +The book has been updated for Rails 4.2 and uses industry best practices of +building a multitenanted Rails application, and the best practices of using +Braintree or Stripe to add subscription features to that application. + +**If you've read [Rails 4 in Action](http://manning.com/bigg2) or something of a +similar level to that, this book is a perfect "next step" for you. It adds +features which are more complicated than a basic "CRUD" app to an existing +codebase. If that appeals to you, [use the coupon code "fin" to get 50% off](https://leanpub.com/multi-tenancy-rails-2/c/fin).** + +This update has been quite a long time coming: it took me 298 days from when I +started updating Chapter 1 to this current point. Next up, I'll go through the +book and make sure there's as few bugs and typos as possible. Once I'm done +with that, then I will consider the book to be complete. + +Thanks everyone for buying this book, reading it and providing feedback along the way. + diff --git a/_site/2016/05/multitenancy-with-rails-2nd-edition/index.html b/_site/2016/05/multitenancy-with-rails-2nd-edition/index.html new file mode 100644 index 000000000..8086c3cf7 --- /dev/null +++ b/_site/2016/05/multitenancy-with-rails-2nd-edition/index.html @@ -0,0 +1,58 @@ + + + + Blog of Ryan Bigg - Multitenancy with Rails 2nd Edition + + + + + + +

The Life of a Radar

+
+
+
Multitenancy with Rails 2nd Edition
 + 22 May 2016
+

Multitenancy with Rails 2nd edition is now "content complete". I have now finished doing the majority of the work on this book and all that is left is to go through it and "proof" it.

+ +

The book has been updated for Rails 4.2 and uses industry best practices of +building a multitenanted Rails application, and the best practices of using +Braintree or Stripe to add subscription features to that application.

+ +

If you've read Rails 4 in Action or something of a +similar level to that, this book is a perfect "next step" for you. It adds +features which are more complicated than a basic "CRUD" app to an existing +codebase. If that appeals to you, use the coupon code "fin" to get 50% off.

+ +

This update has been quite a long time coming: it took me 298 days from when I +started updating Chapter 1 to this current point. Next up, I'll go through the +book and make sure there's as few bugs and typos as possible. Once I'm done +with that, then I will consider the book to be complete.

+ +

Thanks everyone for buying this book, reading it and providing feedback along the way.

+ +
+
+
+ + + + + blog comments powered by Disqus + + + diff --git a/_site/atom.xml b/_site/atom.xml index 3b130d1db..cc4677ae4 100644 --- a/_site/atom.xml +++ b/_site/atom.xml @@ -4,7 +4,7 @@ The Life of a Radar - 2016-05-12T06:45:43+10:00 + 2016-05-22T11:53:17+10:00 http://ryanbigg.com/ Ryan Bigg @@ -12,6 +12,31 @@ + + Multitenancy with Rails 2nd Edition + + 2016-05-22T00:00:00+10:00 + http://ryanbigg.com/2016/05/multitenancy-with-rails-2nd-edition + Multitenancy with Rails 2nd edition is now "content complete". I have now finished doing the majority of the work on this book and all that is left is to go through it and "proof" it.

+ +

The book has been updated for Rails 4.2 and uses industry best practices of +building a multitenanted Rails application, and the best practices of using +Braintree or Stripe to add subscription features to that application.

+ +

If you've read Rails 4 in Action or something of a +similar level to that, this book is a perfect "next step" for you. It adds +features which are more complicated than a basic "CRUD" app to an existing +codebase. If that appeals to you, use the coupon code "fin" to get 50% off.

+ +

This update has been quite a long time coming: it took me 298 days from when I +started updating Chapter 1 to this current point. Next up, I'll go through the +book and make sure there's as few bugs and typos as possible. Once I'm done +with that, then I will consider the book to be complete.

+ +

Thanks everyone for buying this book, reading it and providing feedback along the way.

+]]> + + Hiring Juniors @@ -1897,90 +1922,5 @@ end ]]> - - Community Management - - 2014-04-02T00:00:00+11:00 - http://ryanbigg.com/2014/04/community-management - I've been the "Community Manager" for Spree for a couple of years now. It's a -job where I answer user support requests wherever they happen: IM, email, IRC, -Stack Overflow. I've been splitting this up with some development on Spree, -building features like the new adjustments system whilst getting some great -feedback about them from the community.

- -

Over time, it's been getting busier and busier and I've ended up doing more -"community management" and less programming and it's been burning me out. When -I'm programming, I know that I'm working towards a goal. When I'm answering -emails, there's always more emails to answer the next day. It just doesn't -feel like progress is happening at all.

- -

We've just passed our busiest time of the year. People have found Spree and -want to either start using it, or port over from their existing ecommerce -platform. These people generally start asking questions at the end of January -and it quietens down around about now, picking up slightly in June (I don't -know why, it just does) and the later months of the year due to Black Friday / -Christmas / people wanting things done "Right Now Or Else" by the end of the -year.

- -

During this extremely busy phase, I've really dialed back on the programming -part of my job and I've been dedicating most of my time to answering user -support requests, mainly in the form of trying to keep my email inbox at an -amount as close to zero as possible. The community benefits from this work -because those people asking the questions get the support they need and they -can continue on doing their own things. That's a great thing. When people are -using something that I helped build and they like using it; that is one of -the best feelings in the world. It's part of the reason why I've stayed here -in this job longer than any other job I've had. It's also a pretty awesome -team to work with.

- -

After SpreeConf (26-27th Feb), I did an email inbox cull and still had 500+ -emails to read through and reply to. This is part of my job, and it seemed -overwhelming. I was occassionally grumpy and short with my words. It's only -last week -- a whole month later -- that I was able to get this inbox number -down to less than 50. As I write this now, it sits at almost 200.

- -

But there's a legitimate reason for that. For the past two days I've been -doing exclusively programming work. I closed Airmail and worked for two days -in Sublime Text, iTerm and Chrome. It felt glorious. It felt like progress.

- -

Last Friday at approximately 4:40pm my time and ridiculous o' clock (1:40am) in DC, -Sean passed on a message from one of our clients who said something to the -effect that Magento's order interface in the admin backend was better than -Spree's order interface. Now, there's not many things Magento is better at -than Spree, but this is (supposedly) one of them. I agreed whole-heartedly with the -message, but it was 4:40pm on a Friday and I was thinking/dreaming of the -weekend.

- -

I've personally been wanting to change the admin backend for quite a while. It -doesn't adjust itself depending on the order's checkout steps, which is a -feature that we implemented about 6 major Spree releases. It just hasn't been -that important to work on as other things have been.

- -

This little comment ate at me all weekend. How could we be worse than -Magento at something? Was that even possible? Yes, it was. The order interface -reloaded the entire page after every single change and it was infuriating. It -felt sluggish. Creating an order in Spree's admin backend shouldn't be -tedious, it should be fast.

- -

Here's a video of the admin order interface

- -

So on Monday I worked on improving this. I rewrote templates from ERB to -Underscore templates. I converted some JavaScript code that was defining top- -level functions into some CoffeeScript+Backbone code that defined those -functions as proper events within Backbone views.

- -

I made it fast. Here's a video of the new admin order interface

- -

This felt like progress, because it is progress. I'm improving something -within Spree rather than answering emails, and I feel really good about it.

- -

So what I'm going to be doing now is devoting at least a day a week to purely -coding on Spree. All the emails can wait an extra day. Hopefully those emails -will be answered by someone else.

- -

You can see the code for these recent changes over on my new-order-interface branch.

-]]> - - \ No newline at end of file diff --git a/_site/blogography.html b/_site/blogography.html index 39784ade7..1533fd29a 100644 --- a/_site/blogography.html +++ b/_site/blogography.html @@ -28,6 +28,8 @@

The Blogography of a Radar

The formatting for earlier posts may be a little skewiff. If you find something like that, patches are very welcome.