202 karma · joined July 24, 2013
https://www.lewagon.com
[ my public key: https://keybase.io/ssaunier; my proof: https://keybase.io/ssaunier/sigs/X02XyDr7LDDvPJWMBeS5f9L1elaQfMQskrbMZQgRgBA ]
- Solid Queue & Cache by default (no need for Redis)
- Propshaft as default asset pipeline (retiring Sprockets)
- Basic auth generator (will Devise still be useful for new apps?)
- Kamal by default for new applications
Simplifying Web Development and even more sane defaults in Rails makes me really happy!
Life-changing!
An other way is to use something like Faktory (https://contribsys.com/faktory/) on top of Redis. You push jobs from Rails and then you pull them from Python to execute. Then Python can enqueue another job with the result which gets consumed by Rails (async callback).
You can view Front as a shared Gmail Inbox where you can assign messages to teammates and have private discussions on top of email threads.
They recently added Front Chat which we used to replace the Intercom Chat on https://www.lewagon.com - This way the team only uses one tool (Front) to handle incoming chats or emails.
We've been a customers for 3+ years and are really happy! Congrats on the Series B!
More details here: https://github.com/lewagon/rails-templates
So true.
For the first point, we had a debate on wether we should expose the tests to the student as it would:
1. Maybe help them to find the solution 2. Allow them to change the tests just to make their solution pass
In practise, we realized that error messages from specs do not necessary reveal the solution (point 1), and for point 2, we decided to trust the students (they are adults, in a paying bootcamp), and it works actually. So no need to put spec overwriting / hiding.
For the second question, we are running a simple rake runner (see https://gist.github.com/ssaunier/9713130), launching the tests in a specific folder and parsing the result. We are not doing isolated environments with ruby install / bundle install like TravisCI does, so it is suited for our simple use case only.
Hope that answers your question!
You could go for a trip while working as you are now free.
https://api.github.com/users?since=0
And iterate on. They even give you a HTTP header for the next URI:
Link: <https://api.github.com/users?since=135>; rel="next"
There is a rate limit of 60 (per hour), but if you use oauth then it's 5000. See http://developer.github.com/v3/#rate-limiting