#pyramid

guys, what do you use to combine static assets from multiple packages in your app?

config.override_asset can pull things together into a virtual folder if that's what you're asking

raydeo: does that help when you want to serve statics with nginx at one point? I think i should be looking at pyramid_webassets direction, but im not 100% sure yet what I'm looking for

no, it's just for python

if you want an asset pipeline then maybe pyramid_webassets, maybe gulp, lots of options

Is this a valid URL for pyramid? mydomain.com/resource/?query=value

params and query_string don't contain the ?query=value for me.

sure it's a valid url

with that url, I get empty request.params and request.query_string

Hum, maybe it's my bad.

Yea it was my bad

what's appropriate mailing list for Pyramid related job postings?

pylons-discuss is fine, I don't know if there's a better / more popular one

raydeo: thx

stevepiercy: did you mention a deploy recipe that is missing earlier today?

stevepiercy: if that is the case ... what are your expectations? Just write it down how to make gunicorn work with the app?

bind yes, pick any example that is similar from here as a template: http://docs.pylonsproject.org/projects/pyramid-...

raydeo x57 benbangert chrisrossi reading scrollback, i originally branched off master, started making commits, then that massive merge happened on master. i then rebased master on to the docs/...pip branch, merged the two conflicting pages, which wasn't too bad, then pushed it up. i then pooped myself seeing the commit history.

lol

yeah well the original branch didn't have all those commits

i changed my shorts in the meanwhile

hopefully you were wearing depends

now it does... no big deal

you could delete the original branch if you wanted

but that's what happens when master changes a lot in the meantime unfortunately

yeah, i think i'll do that because it is noisy as it is

it's less bad than you think

just make a new branch off of master containing the new commits you want to have

then force push that over the current branch instead of doing a PR

ah, ok

you can futz with that docs branch all you want since no one else is contributing to it yet

yeah, the idea was to set up the branch on both Pylons and my repos so that others could contribute to it easily

stevepiercy: will try to get something onto github then soonish ... I guess it should be based on the master eh? :D

bind you guess correctly! you get a gold :star: