In the last post I talked about how to create a customer subscription within my application and today I will explain how to deal with a future payment failure for customer subscriptions. This can happen for many reasons such as the card becoming expired for example.
I've covered making payments with Stripe in my recent blog posts and the final part of this is creating and handling customer subscriptions rather than just one off payments.
This is a quick post to discuss the idea of mocks in Rails testing. I demonstrate this using the code I ended up with at the end of my last post:
class ProjectController < ApplicationController
...
def create
@project = Project.new(project_params)
CreditDeduction.new(current_user).deduct_credit
end
...
end
In this post I'm going to talk about how to manage your application as it grows and discuss ways in which you can keep the code base clean.
In my previous post I went over some of the changes I made to receive Stripe payments in my application and today I'm going to go over ways to test this. I had previously used the stripe-ruby-mock gem which saves a lot of time and effort but I also want to learn the skills of how to write tests myself that can be used to test a 3rd party service.
In my previous post I talk about taking payments in your application with Stripe. I've made some changes to this now which I'll go over in this post.
The last part of week three in the Tealeaf Academy course involved implementing another feature that I was excited to learn about - making payments. Show me the money!
One of the things I've been excited to get to in the Tealeaf Academy course is the section on uploading images and saving to Amazon S3. This post will walk through the steps to get this working in a Rails application.
There are parts of your site that you only want certain people to be able to access and I'll use this post to walk through the steps of adding an admin to the MyFLiX site on the Tealeaf Academy Course. I want to give that admin the authority to add a video on the site but regular users should not be able to this.
In my previous post when I talked about the deployment pipeline I discussed using the Paratrooper gem to help automate some of the steps for deployment to the staging and production servers. In this post I'm going to talk about another tool and development practice that can not only replace this but also do a whole lot more.