Suppose that you were going to do this again, how might you do it?

[faddat]

A minimal PAAS interests me a great deal. Fleet seemed to make sense for the uses I've been dreaming up for it. My question is basically about the stack: What would you use to do this, if you were going to reboot the thing in fall of 2015?

Thaks!

-Jake

[Xe]

• Start with a clear goal and work around that. This really started as me wanting to turn what I do into something repeatable that other people could use too. I wanted to codify how I make a middle ground between dokku and something more comprehensive like deis.
• Don't worry about authentication on flitter's side. There's ldap. There's Oauth2. There's XMLRPC into my personal stuff. There's options.
• Better build on top of wheels that exist, only augmenting them or adding functionality where it is actually missing.
• Don't bitrot so easily. (I'd be amazed if this works out of the box on modern CoreOS without significant modifications)
• I'd write a lot of it in Haskell instead of Go so that testing and ensuring correctness is easier.
• I'd try to get financial backing somehow (kickstarter, found a startup, black market, etc) so that my life needs would be covered while working on the core of this. Part of the reason this stopped being updated is because I had lost my job and needed to find a new one quickly. And then when I did find a new job it was mentally taxxing to the point where I couldn't get the energy to work on it or keep up with the breaking changes in CoreOS.
• Don't do it alone. A lot of how I work is by having people tell me where I am screwing things up.
• Actually have tests. No really. Actually have them. Tests are absolutely VITAL.

[faddat]

Thank you!

On 10/3/15 1:17 PM, Christine Dodrill wrote:

• Start with a clear goal and work around that. This really started as me wanting to turn what I do into something repeatable that other people could use too. I wanted to codify how I make a middle ground between dokku and something more comprehensive like deis.
• Don't worry about authentication on flitter's side. There's ldap. There's Oauth2. There's XMLRPC into my personal stuff. There's options.
• Better build on top of wheels that exist, only augmenting them or adding functionality where it is actually missing.
• Don't bitrot so easily. (I'd be amazed if this works out of the box on modern CoreOS without significant modifications)
• I'd write a lot of it in Haskell instead of Go so that testing and ensuring correctness is easier.
• I'd try to get financial backing somehow (kickstarter, found a startup, black market, etc) so that my life needs would be covered while working on the core of this. Part of the reason this stopped being updated is because I had lost my job and needed to find a new one quickly. And then when I did find a new job it was mentally taxxing to the point where I couldn't get the energy to work on it or keep up with the breaking changes in CoreOS.
• Don't do it alone. A lot of how I work is by having people tell me where I am screwing things up.

— Reply to this email directly or view it on GitHub https://github.com/Xe/flitter/issues/39#issuecomment-145209435.