I'm apprehensive about introducing the aspect of money, doesn't it always seem to spoil the innocence of things :( But certainly that must be on people's minds when they see Openruko.
With regards to Slotbox (my fork of Openruko), the whole point is that it is a means of crowdfunded hosting, so money is an important factor. I don't think Openruko should ever integrate payment systems, but I do think there's reason to have an economically agnostic crediting system. I'm thinking of something that compliments the heartbeats, so that every time a heartbeat occurs 1 credit is deducted. If an app doesn't have enough credits then certain functionality changes; httprouting returns an "error" page (still 2xx status, not 4/5xx), certain API functions are disabled, scaling for example.
I realise this approach may be too tied to Slotbox and not true to Heroku's functionality, but if there is a way of doing this so that Openruko and Slotbox can both benefit, I'd like to do that.
I'm apprehensive about introducing the aspect of money, doesn't it always seem to spoil the innocence of things :( But certainly that must be on people's minds when they see Openruko.
With regards to Slotbox (my fork of Openruko), the whole point is that it is a means of crowdfunded hosting, so money is an important factor. I don't think Openruko should ever integrate payment systems, but I do think there's reason to have an economically agnostic crediting system. I'm thinking of something that compliments the heartbeats, so that every time a heartbeat occurs 1 credit is deducted. If an app doesn't have enough credits then certain functionality changes; httprouting returns an "error" page (still 2xx status, not 4/5xx), certain API functions are disabled, scaling for example.
I realise this approach may be too tied to Slotbox and not true to Heroku's functionality, but if there is a way of doing this so that Openruko and Slotbox can both benefit, I'd like to do that.