These are chat archives for CharlesGust/django-imagr

6th
Nov 2014
Charles Gust
@CharlesGust
Nov 06 2014 05:53

Hi Ben, Thanks for all the info! I'm trying to put it "inline" here so Charlie can read it:

I talked to Jason, he said related_name= doesn't work the way we thought it does -- his understanding is that it allows a single field in the ImagrUser table to double as following and followers (called by the variable name in one direction and the related_name in another), and that it would perform as expected that way. I haven't had time to research it yet.
Also, nobody else got the AWS discount thing to work.
I spoke with Lindy about getting the AWS Activate thing to work, she said she'll speak with the other person, whose name I forgot, who is going to see what's going on with Amazon there.
Also, I added that CharField to the Imagr model and added a commented line to the home_page.html file with a guess about how linking up cover photos is going to work. Probably need an entry in urls.py which redirects to the S3 page for each photo, constructed with that photo's id, via a function in views.py that somehow does that. Maybe.
[...]
Oh, the branch I pushed the stuff I did right after you left to was views_bf

I think we all can still do the boto assignment without the discount. Maybe that's easy for me to say because if I get charged a few bucks for a server I put up and immediately take down, it's no big deal. I also thought we could use "Free Tier" S3 anyway; the discount has meaning when our projects start spanning machines (okay, maybe this one spans two, but that's still only a couple bucks a month, I think)

Charlie
@charlieRode
Nov 06 2014 05:56
Thanks Charles. Did you guys finish the views implementation today? I'm pecking at it--there are a few questions I hope you could answer for me tomorrow
Charles Gust
@CharlesGust
Nov 06 2014 06:00
No, I think we got to the middle of the second view. I think the main problem is that we are writing code that we think will work, but various conditions will always return false. BTW, we started over at migration 0001. We may have to re-initialize our local databases. I don't remember why I did this; I think I was concerned about "identifier" and "id" being mixed up and I thought this would fix it.
Charlie
@charlieRode
Nov 06 2014 06:02
I had an issue with migration too. Something to do with a keyword arg being passed (preserve default=True) that an init function didn't know what to do with
Charles Gust
@CharlesGust
Nov 06 2014 06:03
@charlieRode What Ben and I agreed to (after talking with Dan) is that we can get the code written to handle pictures in the database sooner the sooner we work with Python's boto library. So, we thought we should make that a priority to do tonight, so that we're ready to work on imagr some tomorrow.
Charles Gust
@CharlesGust
Nov 06 2014 20:53
Hey @charlieRode and @BFriedland ; I'll be upstairs very soon. I'm going to have to duck out for a couple of minutes at about 1:15.