@waghanza Well... yeah, RPG and Modula2 has a future, out of the question. I mean as a main language for web development, with an strong community and an updated gemset covering all the new technologies. That's my wish, but I'm not sure.
I'm watching how the new thins are created for nodejs and go, even they are replicated in python, but I don't see the same response in ruby.
Understand me, please, just sharing my thoughts, I'm not sure and I'm not abandoning ruby or padrino.
@jorgefuertes questioning ... is a safe and sane way to go to the future, but not very about technologies or frameworks. I mean each language is more or less suitable for various needs, and every frameworks has feature for future, for example, https://rubyonrails.org/ has https://stimulusjs.org/ or https://github.com/rails/webpacker allowing that we can use some technologies for what they fit for.
ruby fit more for backend and vue/react for frontend.
I don't think we have to talk about end of road, but how we can adapt :heart:
I'm paranoic? May I be, I want to hear that.
at least more gems you use, more you are frightened
I understand
@waghanza Haha, thank you.
I would be very disappointed in humanity (even more than now) if Ruby would go away. Developing both in Python and Ruby I must say that Ruby is the only language not getting in my way. I've tried NodeJS/JS and that's even worse than Python. Nah… Ruby needs to stay. Or I'll switch jobs to something with wood and flowers.
I'm having an issue with params expansion in routes with mustermann. With the old router I have no issues. With mustermann a call like
absolute_url(:posts, :index) resolves to a more specific route like /posts/:year/:monthand errors out with Mustermann::ExpandError: cannot expand with keys [], possible expansions: [:year, :month]. Apologies if there is some documentation/migration guide out there that I missed that addresses this. Thank you for your time.
Because previously I could name all routes
:index and the old router it seems would disambiguate based on request method and params?
Because I could have , for example
Demo::App.controllers :posts do
get :index do; end # /posts
get :index, with: :id do; end # /posts/:id
get :index, with: [:year, :month] do; end # /posts/:year/:month
post :index do; end # /posts
patch :index, with :id do; end # /posts/:id
delete :index, with: :id do; end # /posts/:id
end
And there was no issue for
absolute_url(:posts, :index) to resolve to /posts
Where Can I find that information?
I have created a trailer for my YouTube Channel about Padrino under https://youtu.be/9ZEykhzDjfA - would be great if you like the video to help me with the channel.
I am new to ruby (like couple weeks new) and trying to implement omniauth-okta but getting the following error "OmniAuth::Strategies::OAuth2::CallbackError at /auth/okta/callback
csrf_detected | CSRF detected" I have know clue as how to proceed
@nolyoi welcome on board. Haven' worked with omniauth-okta (prefer my own authentication system), but as you mentioned should https://github.com/padrino/padrino-framework/issues/1258#issuecomment-20269121 give you the solution.
I need each log line to have a trace_id prepended which will continually update with every request. I'm hoping I don't have to install a new logger and update throughout the entire application
Hey, there NoMethodError error for generated mailers with latest padrino 0.15.0, issue request created under padrino/padrino-framework#2232.
Hey guys, I just upgraded an old project from 13.1 to 15.0, and when trying to boot up, I am getting the message "NoMethodError - undefined method 'mailer' for StudentPortal::App:Class:". I have checked and under "module StudentPortal
class App < Padrino::Application" I do have "register Padrino::Mailer" as the next line. Any ideas?
class App < Padrino::Application" I do have "register Padrino::Mailer" as the next line. Any ideas?
Ah, sorry, just saw the conversation above about #2322 - Looks like that is the problem. Is upgrading the Sinatra gem the best solution here?
Good morning. I really need some help. My Padrino App has a sub-app, I'd like to share the layout from the main-app with the sub-app, I got it working with render 'index', :layout => AppX::AppX.layout_path('application'), locals: { all: all } but when I start padrino with -e production that doesn't work anymore. :-(
Hi @okleinschmidt, I found with my sub-apps, it was far easier to include the line
set :public_folder, PADRINO_ROOT + '/public' in the app.rb file in each sub-app - then the sub-app looks at the same 'public' folder as the main app, and I don't have to specify a hard path to the :layout each time.
@CyberFerret By now I’ve copied this file to project/subapp/views/layouts/application.rb - not pretty, but works.
According to the source it should be possible https://github.com/padrino/padrino-framework/blob/c8473a12068678b03482fc1247bfeba32cef843f/padrino-core/lib/padrino-core/application/routing.rb#L79-L83
I am looking at an app that has a
before route_regex do ... end inside of a configure block in app.rb. It appears to set up stuff to do before going to routes that match the regex in any of the controllers, but I'm not clear on how this works. Can anyone point me to the documentation on that, or shed some light on it for me?