You need to keep it. It manages the configuration. 👍
Posted in Reopen ActionCable after login?
Jumpstart modifies form submits to be AJAX requests using turbolinks_render.
Your default Rails form submission is a POST request, so the page would fully reload and ActionCable would connect.
I never thought about it, but that is probably something that can/should be triggered after login. A Stimulus controller for this would make sense. It can just check fi the connection is open and, if not, issue the connect. It would probably need to be on every page, unless there's a way to do it after login. I need to think on a good way to do that.
Like I mentioned before, CF is a proxy so it passes the requests to Rails. Rails serves up files just like it always does. Nothing special.
That's the cool part. When you configure the backend, it will accept all requests and then ask your app (the backend) for the files and send them back. It saves them in the CDN so that next request, it doesn't have to ask your app again and can serve it up immediately. It just sits in between the user and the app as a proxy.
Uploaded it to YouTube so you could see it early. 😎
Recorded a video on it. I'll be publishing it in the next week or two. 👍
I may have accidentally missed a little bit of that as I was trying to prepare for the episode. 😬
You can usually just call the
sanitize method and that'll do what you need.
Yep! Push notifications would be an API call (similar to Slack, Twilio, and Vonage are). 👍
Well, notifications are a complicated subject. Basic ones like sending an email are easy, but this is a full-featured notification system like you'd see on Facebook or Twitter. I'll talk more about it and show a very basic use case of Noticed soon.
Also for the frontend, I usually build my own helpers to generate the two fields for me. Saves a lot of time and I can just make a small change to each field with a find & replace to call the new helper instead of having to edit each one.
This would make a great screencast talking about the tradeoffs of both approaches.
You can definitely strip out the commas or periods when the user submits the data if you want by overriding the setter methods. That would let any value be submitted and cleaned up before storing it in the model.
def population=(value) super(value.gsub(/[.,]/, '') end
Something like that should do the trick.
Since it's just formatting, it's usually best if that just happens on the client side. That becomes even more useful in other languages that might use a period as thousands separators instead of commas. They can change their locale and the backend data would not have to change for that. Plus, the backend doesn't have to worry about modifying the formatting, just validating it.
Either way will probably work fine though.
Fake form fields can accomplish what you want.
You can use formatting in the visible form field, but convert to the number in a hidden field. The visible field is not given a
name field which means the browser does not submit them to the server.
Rails has several helpers for numbers.
number_with_delimiter(population) # outputs 422,334 number_with_precision number_to_currency
All part of the NumberHelper: https://api.rubyonrails.org/classes/ActionView/Helpers/NumberHelper.html
Numbers should always be saved without formatting in the database and then you'll use a helper like the above to format it.
We're using the acts_as_tenant gem in JumpstartRails.com for row-level multitenancy. It works pretty well and will automatically set your tenant ID when querying and saving records. You end up building your app like a regular app that way which is nice.
I wouldn't recommend Apartment anymore because it's not row-level tenancy. It's far more common to see row-level being used.
It's not intended to be a full WYSIWYG which is what you're after. I know several people like using https://imperavi.com Article and Redactor and they're really well made.
Posted in A Look Into Routing Discussion
He loves running around and being noise when I'm trying to record. 😺
Posted in Active-storage creating/uploading folder
I would say, don't think of it as folders on S3 or the file server. Use database records to group and organize them in your app. They don't have to exactly mirror the files on disk.