padrino-framework
padrino-framework copied to clipboard
padrino
Release 1.0.0
Here's the roadmap to 1.0 updated. The biggest changes I can see will be the new site (/cc @dariocravero), majorly updated docs, minimum ruby 2.0, and the howl router (/cc @namusyaka). Anyone want to propose other major changes before 1.0 that are not in the roadmap yet? Things like the padrino-auth official release (/cc @ujifgc) will be an important part as well.
I hope this is the right place for this question, and sorry for forgetting to ask a few days ago when you guys were preparing for the RubyRogues podcast
Just out of curiosity. How much is the interest in improving Padrino for projects using gemified apps? I am working on a series of examples about how to do this, but I am finding myself on some rough edges. Maybe it is because I still do not know Padrino well enough.
A workflow fragmenting a big project into multiple gems seems ideal to me, but since I was not able to find examples or blog posts of people taking the same approach, I was wondering if my approach was awfully wrong. In any case, I am quite willing to work in my examples and explain those rough edges, but not sure if that is a minor concern right now or even if it might provide any value.
If there is any interest, I am willing to work more on my demo and even build a library that might help others take my same approach.
@fgarcia :+1: we are interested in hearing more about your rough edges. I think you were not able to find blog posts since gemifying is newer feature and not very well used yet although we want it to be rock solid for 1.0. Would be great if you could be the trailblazer to help us identify some of these issues.
:+1: micro-services FTW! Funny enough, right after the podcast I got thinking that it would be cool to have a way to deploy a gemified app without any extra scaffold too :).I'll try to implement that with Mina whenever I get a chance. Looks like we're on the same path. Thanks for your interest to push this forward :). Let me know if you need any help along the way.
On Sun, Aug 17, 2014 at 1:18 AM, Nathan Esquenazi [email protected] wrote:
@fgarcia https://github.com/fgarcia :+1 Iwe are interested in hearing more about your rough edges. I think you were not able to find blog posts since gemifying is newer feature and not very well used yet although we want it to be rock solid for 1.0. Would be great if you could be the trailblazer to help us identify some of these issues.
— Reply to this email directly or view it on GitHub https://github.com/padrino/padrino-framework/issues/975#issuecomment-52408655 .
I should present myself as the micro-services gemified apps obsessed user! :weary:
It is hard to summarize down the rough edges I encountered. Reading the first section of this README should give you enough context for my rough edges notes :sweat:
That alone might be a bit overwhelming, so let me know if you are interested and I could go on with some questions. You guys are much smarter and experienced than me, so my biggest doubts are related with best practices / configuration.
If there is enough interest I will consider turning the experience into a mini project idea.
after some fixes to my rough edges notes I am realized that a good part of my "rough edges" are more related to my lack of understanding of Padrino!
Please bear with me, hopefully there will be some good idea out of this which could lead to some contribution of my part. I would appreciate if you can point out some possible conflict in the way I layout the gems. No need to discuss anything specific now, I am just curious if the veterans think "that is a good direction". I want to explore further so I can expose better my ideas
Right now I am stuck with my own issue https://github.com/zenbits/pademo/issues/3 and not sure if I found a bug or I am just doing something wrong
Sorry @fgarcia, I don't want to leave this unanswered but I'm not with a steady internet connection so I just wanted to say I'll have a look at those as soon as I can (which might be within the next two weeks unfortunately :/). Sorry if that's too far in time :(
@dariocravero no worries, I was stuck until now because of https://github.com/padrino/padrino-framework/issues/1745 and I do not have too much time. Unfortunately it seems I will be busy bending backwards with some Rails... hard to explain shortly :(
but that will give me motivation to work in my gemified examples/tutorial repo, along the commented project idea!
making a rake routes in Rails makes me miss already Padrino
I agree with you @namusyaka. At this point we might as well go to 1.0. We have the new site launched. Padrino is clearly fairly stable at this point.
Not really. I'm just unhappy about current API and its inline documentation. It's too diverse. 1.0.0 should mean stable beautiful API.
We should discuss the beautiful API. And I want to lay out a concrete road map.
Yeah we can do preview releases with the breaking API changes or do one more major version before 1.0 to work out any kinks. What would you all suggest as the cornerstone breaking changes?
I've thought in the past we might want to simplify the syntax for controller routing. I have a related issue. #747
I want to improve controller ang routing syntax, but i'd like to hear other opinions. With that in mind, we should list-up concreate milestones for releasing v1.0.0.
This was once our working draft, obviously may not be totally relevant now: https://github.com/padrino/padrino-framework/wiki/Roadmap-for-1.0