cassiogo
If they have the US government behind them its much easier
https://thepaypers.com/payments/expert-views/pix-hits-a-wall...
Sure it could be easier/safer to manage, everything can be better.
Over the last couple of years hosting it I had a single issue with an upgrade but that was because I simply ignore the upgrade instructions and YOLOed the docker compose update.
Again, is it perfect? No. Would I expect a non tech savy user to manage their own instance? Again no.
Also, custom actions [https://turbo.hotwired.dev/handbook/streams#custom-actions] are super powerfull, we use it to emmit browser events, update dom classes and attributes and so on, just be careful not to overuse it.
require 'bundler/inline'
gemfile(true) do
source 'https://rubygems.org'
gem 'rails', '~> 7.1'
gem "sqlite3", "~> 1.4"
end
require 'rails'
require 'active_record/railtie'
database = 'app_development.sqlite3'
ENV['DATABASE_URL'] = "sqlite3:#{database}"
ActiveRecord::Base.establish_connection(adapter: 'sqlite3', database: database)
ActiveRecord::Schema.define do
create_table :my_table, force: true do |t|
t.integer :my_table_id
end
end
class App < Rails::Application
routes.append do
root to: 'home#index'
end
end
class HomeController < ActionController::Base
def index
render inline: 'HOME'
end
end
App.initialize!
run App
But then, for someone not deep into react, a magic string like "use server" also does not clarify anything.
Also, he argues that just because you can it does not mean you should scatter sql queries around your views. But again, just because you can do a bunch of implicit stuff on a Rails controller it does not mean you should.
If I understood correctly it does. They are handling promo codes outside of stripe.
I feel like you are missing the point of the article
> This is an extremely trivial bit of JavaScript, but it is made difficult because it is trying to use a JavaScript
Yes, it is trivial javascript, and it was trivially solved by a couple of javascript lines
He does mention running it on a macbook
Not as simple if you are using any "advanced" PG feature. If you testing simple select statements thats probably fine.
But now that I think about it, yeah, even looking only at pattern matching there is a lot of new syntax going on.