|
Pollyanna posted:I'm guessing it's like any other conference, but with more people sitting on the floor with their laptops? And all the laptops are Macs. See you there! PM me if you want a New Relic sticker.
|
# ? May 3, 2016 03:50 |
|
|
# ? May 30, 2024 13:46 |
macs are just what they buy us okay
|
|
# ? May 3, 2016 05:24 |
|
aunt jemima posted:And all the laptops are Macs. I wont be at the conf A MIRACLE posted:macs are just what they buy us okay
|
# ? May 4, 2016 03:38 |
|
I'll be at the New Relic party, so I might see you there
|
# ? May 4, 2016 15:41 |
|
Pollyanna posted:I'll be at the New Relic party, so I might see you there Indeed you will. We have like 100+ people wait listed for our lil get-together so it should be fun. Definitely say hi and get a sticker, I'm the tall door-shaped dude in NR swag
|
# ? May 4, 2016 16:44 |
|
Also I should've slept in instead of attending this meandering word soup of a keynote
|
# ? May 4, 2016 16:47 |
|
This is the first railsconf I've missed since 2007, but the last several I'm mostly worked a booth and drank, and didn't go to any talks so it's alright. Have a good everyone
|
# ? May 4, 2016 16:52 |
|
Tickets sold out awwww. Oh well, I'll keep an eye out for door Jemima dude anyway
|
# ? May 4, 2016 23:06 |
|
We have a rails 4 app that uses Devise for logging in, and which can be accessed with an API with cURL. Users can log in with a cURL POST command, download XML data, update certain records, etc. But, I've never been able to enable explicit logging out through cURL - either the cURL command seems to work, but doesn't affect the session, or I get a CSRF error, or something else goes wrong. Then it occurred to me this morning - the user can just delete the cookie on their local machine, which should effectively kill their ability to login. It just seems too simple - is there any problem with this approach? Sessions automatically expire after 30 minutes of inactivity, so I don't think I need to worry about valid session data clogging up the system (though I don't see any session data in the database anyway).
|
# ? May 5, 2016 15:55 |
|
cURL uses cookies?????!
|
# ? May 5, 2016 15:57 |
|
KoRMaK posted:cURL uses cookies?????! Yep. Try this: code:
code:
|
# ? May 5, 2016 16:09 |
|
Peristalsis posted:We have a rails 4 app that uses Devise for logging in, and which can be accessed with an API with cURL. Users can log in with a cURL POST command, download XML data, update certain records, etc. But, I've never been able to enable explicit logging out through cURL - either the cURL command seems to work, but doesn't affect the session, or I get a CSRF error, or something else goes wrong. Then it occurred to me this morning - the user can just delete the cookie on their local machine, which should effectively kill their ability to login. It just seems too simple - is there any problem with this approach? Sessions automatically expire after 30 minutes of inactivity, so I don't think I need to worry about valid session data clogging up the system (though I don't see any session data in the database anyway). By default, rails stores session data in the cookie. So deleting the cookie effectively removes that session from existence.
|
# ? May 5, 2016 18:08 |
|
Shook Michael Hartl's hand and bought him a beer tonight. I had to apologize to him for initially blowing off the TDD part of his book when I first read it. EDIT: my coworker is talking about world of warcraft with him now this is my night guys. this is happening EDIT 2: photobombed him Pollyanna fucked around with this message at 03:37 on May 6, 2016 |
# ? May 6, 2016 02:38 |
|
Are there any decent alternatives to active record that implement a proper data mapping pattern and play nice with the ecosystem. I'm fairly new to rails (Coming from a django background, new jobs uses rails), but was completely dumbstruck that active record doesnt create database constrains on relationships, and the dude who wrote them apparently doesnt believe in them. Thats a pretty bad sign in my books, so whats the alternatives?
|
# ? May 9, 2016 22:39 |
There's DataMapper but it's a piece of poo poo compared to Activerecord imo Also they don't support newer versions of rails If you want foreign key constraints can't you just add those manually?
|
|
# ? May 9, 2016 22:43 |
|
duck monster posted:Are there any decent alternatives to active record that implement a proper data mapping pattern and play nice with the ecosystem. http://edgeguides.rubyonrails.org/active_record_migrations.html#active-record-and-referential-integrity Prior to that anyone who really wanted them was (and still probably are) using a pair of gems named immigrant and foreigner. That being said you could use DataMapper as mentioned or Sequel I guess. Honestly I've worked with a lot of fairly large Rails apps with and without constraints and it's not nearly as bad as I thought it'd be (I had the same hesitations as you do).
|
# ? May 9, 2016 22:46 |
|
duck monster posted:I'm fairly new to rails (Coming from a django background, new jobs uses rails), but was completely dumbstruck that active record doesnt create database constrains on relationships, and the dude who wrote them apparently doesnt believe in them. Thats a pretty bad sign in my books, so whats the alternatives? AR will create foreign key constraints if you tell it to - http://guides.rubyonrails.org/active_record_migrations.html#foreign-keys The only other ORM I've seen any kind of support for in the Rails world is Mongoid, and gently caress that noise.
|
# ? May 9, 2016 22:49 |
|
1. gently caress DataMapper 2. There is a successor to DataMapper, and it's supposed to be nice if you're into that sort of thing. http://rom-rb.org/ 3. ActiveRecord has its faults, but unless you're really sure it doesn't fit your needs, you're best off sticking with it. It absolutely does support FK restraints, among other things, just doesn't do it automatically for Reasons. vv Yeah, ROM-sql uses Sequel under the hood. That part is solid enough. Chilled Milk fucked around with this message at 02:41 on May 10, 2016 |
# ? May 10, 2016 02:04 |
|
I use Sequel, even with rails. It is perhaps the best maintained software project ever. There are never any open issues because Jeremy Evans fixes everything right away. There is one release a month with just small incremental changes. Every month. Use sequel and use postgres. Edit: well, it was a bit of a pain to get it to fit into rails. Not huge but defiantly not drop in. It's worth it for me because it's so much better than AR, but I could see it not being worth it for others. If you do stick with AR do something like this to not get the bad defaults AR uses for data types code:
Pardot fucked around with this message at 02:15 on May 10, 2016 |
# ? May 10, 2016 02:11 |
The Milkman posted:1. gently caress DataMapper Datamapper is a pile of poo poo and I'm currently working on a project that uses it extensively. And there are zero unit tests. Anyone hiring right now? I'm good at javascript too? lol. Sequel is pretty awesome from what I've used it for (one off scripting)
|
|
# ? May 10, 2016 03:23 |
|
Just use Arel and write your own migrations. Youll be so much happier.
|
# ? May 11, 2016 00:58 |
|
I should look into Sequel. Our app is getting unwieldy, and I'll have the chance to do some refactoring soon. What's the current best resource/guidelines for refactoring controllers, models, etc.? Edit: if it helps, all our controller methods tend to look like this and this. Pollyanna fucked around with this message at 15:45 on May 12, 2016 |
# ? May 12, 2016 15:28 |
|
Pollyanna posted:I should look into Sequel. switch to a service pattern. Sequel's probably not going to help you much.
|
# ? May 12, 2016 16:07 |
|
Pollyanna posted:I should look into Sequel. [screams internally]
|
# ? May 12, 2016 16:11 |
|
kayakyakr posted:switch to a service pattern. Sequel's probably not going to help you much. Oh, no, Sequel's not related to our app, it's a personal project thing. A Service pattern sounds much more like what we need. I'll look into that too! KoRMaK posted:[screams internally] Welcome to my past half year. None of the old devs had Ruby or Rails experience when they made this, and in fact it was a manager that first put the thing together under orders (long story). The only other dev was mostly a Java programmer. So, it was put together by a couple Rails newbies, and one non-programmer. I'm now one of two devs (not the originals) on the product team, so I own this thing. I will make it not poo poo or die trying. Pollyanna fucked around with this message at 18:05 on May 12, 2016 |
# ? May 12, 2016 16:12 |
|
Pollyanna posted:I should look into Sequel. Well, I suddenly feel much better about myself.
|
# ? May 12, 2016 16:31 |
|
There is always more, and it is always worse.
|
# ? May 12, 2016 18:03 |
That's quite tidy compared with the Datamapper shitshow I'm wrestling with at my new job. As an added bonus we have 0% test coverage and if something breaks "it's my rear end!"
|
|
# ? May 12, 2016 18:09 |
|
Pollyanna posted:There is always more, and it is always worse. Let us see `rake stats`
|
# ? May 12, 2016 18:09 |
code:
|
|
# ? May 12, 2016 18:12 |
|
Where can I find a style-guide for ruby 2.0.0 and raisl 3.2 era? The github repos don't have tags https://github.com/bbatsov/ruby-style-guide/ https://github.com/bbatsov/rails-style-guide
|
# ? May 12, 2016 18:48 |
|
The Journey Fraternity posted:Let us see `rake stats` haha code:
This is without our Views, which are horrid. Inline JS and styling, comments to the tune of "BEGIN MAIN PAGE SECTION" etc. It's a joke. Edit gently caress oh whateverrrr Pollyanna fucked around with this message at 19:23 on May 12, 2016 |
# ? May 12, 2016 19:20 |
|
^^ code:
|
# ? May 12, 2016 19:34 |
|
code:
|
# ? May 12, 2016 20:01 |
|
^^^ that's some good test numbers. Are they actually useful tests?code:
|
# ? May 12, 2016 20:21 |
|
Today is the first and only time I've ever heard "I miss PHP" and of course it's in the context of this app
Pollyanna fucked around with this message at 21:54 on May 12, 2016 |
# ? May 12, 2016 20:23 |
|
necrotic posted:^^^ that's some good test numbers. Are they actually useful tests? I feel like they are, I don't directly work on that monolith so I don't deal with it code-wise on a daily basis but in general we seem to have very good quality and testing practices overall, especially considering the contribution volume: We have a number of what probably could be best explained as "service gems" (which I do work on) and there are some circa 2009 tests in the monolith that depend on private APIs in the gems, but as we push new releases and notice the breakage we're cleaning up. So pretty much the usual "legacy codebase" story.
|
# ? May 12, 2016 20:40 |
|
Contracting on:code:
code:
|
# ? May 12, 2016 20:50 |
|
aunt jemima posted:I feel like they are, I don't directly work on that monolith so I don't deal with it code-wise on a daily basis but in general we seem to have very good quality and testing practices overall, especially considering the contribution volume: I'm a bit jealous. We've been working on pulling out bits of our monorail that would clearly be a cost savings benefit, but the vast majority of our product still lives (and evolves) in the monorail. Our testing coverage in those services is better than the legacy code, but still not great. At least we're finally moving off of Ruby 1.9.3... next big upgrade is Rails
|
# ? May 12, 2016 21:00 |
|
|
# ? May 30, 2024 13:46 |
|
necrotic posted:At least we're finally moving off of Ruby 1.9.3... next big upgrade is Rails 3.0 to 3.2 took 3 developers 4 months. Good luck!
|
# ? May 12, 2016 21:28 |