#pyramid

/

      • hvelarde has quit
      • dfee has quit
      • dfee joined the channel
      • dfee has quit
      • dstufft joined the channel
      • tiwula joined the channel
      • dfee joined the channel
      • tiwula has quit
      • dfee has quit
      • Wu joined the channel
      • atomekk joined the channel
      • nmcbride joined the channel
      • dfee joined the channel
      • nmcbride has quit
      • betabug joined the channel
      • benbangert joined the channel
      • ztane
        raydeo: yea I am not commenting as much about the needed complexity.
      • btw just noticed that it supports both 'composit' and 'composite' as spellings for the composites
      • what is worse it uses both internally :(
      • crooksey joined the channel
      • brokencycle joined the channel
      • waveform joined the channel
      • mage_ joined the channel
      • waveform has quit
      • waveform joined the channel
      • econoraptorman has quit
      • mamalos joined the channel
      • mamalos
        hey all!
      • I have a question regarding session factories. I know that there are plenty out there, and three of them are metioned in pyramid's documentation (nacl, redis, beaker as backends). In my case, I'm using mongo as my backend, I don't necessarilly need my sessions to be sync'ed among app servers, so I could use the nacl backend, but then again I would like to try some backend that is based on a data storage,
      • and ideally mongo.
      • (since that's what I'm using in my app)
      • what session factory would you suggest for this?
      • ztane
        the one that's not yet written... :F
      • it depends on the needs
      • I wouldn't use *any of those*
      • as such,
      • or alone.
      • for example if you consider a high-security application, then the user must be able to enumerate the sessions they've logged in to and none of these readily support them.
      • also "not being sync'd among app servers" sounds like a potential scalability issue
      • mage_
        couldn't you switch from MongoDB to Redis and use the Redis one ?
      • it works great, and that's what we use here
      • ztane
        redis one cannot enumerate the sessions a user has.
      • also, redis is ram only.
      • it sucks when you have X gigabytes of sessions and you just need to have that much RAM just because
      • dfee has quit
      • mage_
        ztane: what do you use instead?
      • we don't store that much data in the session here
      • maybe an SQLAlchemy session would be a good thing too
      • mamalos
        thanks both for your suggestsions. I'm thinking about the redis as well, but hoped that there would exist one for mongo too so as not to just have an additional service running only for my sessions.
      • and as far as SQLAlchemy is concerned, I suppose it needs an RDB backend to work with.
      • mage_
        of course
      • mamalos: you could maybe take a look at Beaker and pyramid_beaker
      • there is a mongodb factory
      • mamalos
        OK, is it considered "safe" in terms of session handling, enumeration, highjacking, etc.?
      • wiggy has quit
      • mage_
        I would say that as long as the session cookie is marked "secure" and http only, and that you use SSL/TLS it should be safe
      • and use json (not pickle or something similar) on the server-side storage
      • mamalos
        mage_: sorry, in terms of the server-side storage, I thought you meant that beaker also "supports" a mongo backend via the mongodb factory? Or did I misunderstand you?
      • mage_
        I think so yes
      • mamalos
        cool, will try it out. Thanks!
      • mage_
        from what I read you can provide a mongodb connection string or an already existing MongoClient instance.
      • wiggy joined the channel
      • hvelarde joined the channel
      • hvelarde is now known as hvelarde|brb
      • mtvee joined the channel
      • stevepie_
        Anyone know how to format ${val} or ${num} in deform error messages when they are dates?
      • Ergo joined the channel
      • Ergo
        are there any documents on raven intergraion with exception views in pyramid?
      • i don't want to use logging module, is there a way to do this, maybe some api to send exceptions directly?
      • the docs on their site are really bad
      • stevepiercy
        Ergo we're using a local installation of Sentry
      • Ergo
      • this seems to be a reasonable approach
      • stevepiercy
        the sentry docs are stupid easy, too
      • Ergo
        stevepiercy: those docs are completly useless for me
      • I don't want to use logging module
      • btw. this is new sdk - the project has Raven client currently
      • stevepiercy
        Ergo i won't be much help cuz i didn't set it up
      • and the client didn't document how they set it up
      • wiggy
      • Ergo
        wiggy: i was worried that i will end up with pile of code like that :(
      • wiggy
        that code adds a couple of nifty things though
      • celery integration, a request.raven object so you can pass extra data to sentry, with a mock-version if SENTRY_DSN is not set
      • and an event system so you can pass extra data to raven
      • you can trim it down quite a bit if you don't need everything I added
      • Ergo
        yeah, well ideally I want just to send the data that wsgi middleware + exception view
      • thanks, i will grab what i need
      • it seems, that my implementation is enough
      • I wonder how client gets the request info from just sentry_client.captureException(), probably some threadlocal tricks
      • frispete_ joined the channel
      • stevepiercy: btw. my approach works it seems
      • Wu has quit
      • frispete has quit
      • hvelarde|brb is now known as hvelarde
      • mtvee has quit
      • erasmas joined the channel
      • tiwula joined the channel
      • wiggy has quit
      • crooksey has quit
      • dude-x joined the channel
      • dude-x joined the channel
      • utek joined the channel
      • econoraptorman joined the channel
      • cguardia joined the channel
      • eatkin joined the channel
      • dh has quit
      • dh joined the channel
      • eatkin joined the channel
      • eatkin joined the channel
      • hvelarde is now known as hvelarde|away
      • blaflamme joined the channel
      • waveform has quit
      • brokencycle has quit
      • tiwula has quit