greptilian logo

IRC log for #sourcefu, 2015-07-06

http://sourcefu.com

| Channels | #sourcefu index | Today | | Search | Google Search | Plain-Text | plain, newest first | summary

All times shown according to UTC.

Time S Nick Message
00:15 pdurbin prologic: yep. I just read your blog post and that part is still missing :) . Also, please watch your its vs. it's. :)
00:18 pdurbin I messed around a bit with the list of topics for this channel yesterday: https://github.com/sourcefu/sourcefu.github.com/commit/aca44a5
00:18 prologic ahh cool
00:18 prologic hmm
00:19 prologic where did I use its vs. it's incorrectly? :P
00:19 prologic I guess I'll go over it
00:19 prologic but yeah going to complete the other part of it tonight
00:19 prologic what do you think so far anyway? can I elaborate or improve upon anything (besides its vs it's)
00:19 prologic ?
00:20 pdurbin basically, search for "it's" and every time you see it, figure out if you can expand it to "it is". you'll find it :)
00:20 pdurbin prologic: the post is a little rambly. readers might not care if circuits isn't up to date on pypi
00:20 pdurbin but otherwise so far so good
00:24 prologic isn't: it's == it is?
00:24 prologic and its' is possessive?
00:24 prologic :)
00:24 prologic re circuits/pypi; good point; thanks
00:24 prologic anything else a bit rambly?
00:26 pdurbin possessive is his, her, its
00:26 pdurbin maybe not rambly but people might not know wtf crux is
00:29 prologic I don't think I even mentioned that
00:29 prologic I couldn't rebase that so I could remove it's history
00:29 prologic so was stuck with a commit/fix
00:29 prologic :P
00:29 prologic oh and yes you are quite right
00:29 prologic its not its'
00:29 prologic blah
00:32 pdurbin huh, I must haved clicked on http://nanomsg.org at some point because it's purple. describe as the "spiritual successor of zeromq" at https://changelog.com/163/ which I'm really enjoying.
00:34 prologic fixed the incorrect it's usage
00:34 prologic thanks
00:34 prologic and removed the rambling
00:34 prologic it's unimportant :)
00:39 pdurbin +1
00:39 prologic anything else? :)
00:40 prologic I want to be as engaging as possible
00:40 prologic my intention was to really left out the development of the app as such and assume the reader is quite experienced in web development already
00:40 prologic so it's less of a tutorial on how to write a todo web app
00:41 pdurbin sure. your "hook" is about quick and easy deployment
00:57 prologic precisely
00:57 prologic and also about repeatability
00:57 prologic have I not made that obvious enough?
00:57 prologic I suppose it'll become apparent in the next section
00:59 pdurbin it better
00:59 pdurbin ;)
01:06 prologic hehe
01:06 prologic lastly how does a final section on how to apply this to your own app
01:06 prologic be it a java app, ruby or whatever
01:10 pdurbin yep. sounds good
01:11 pdurbin prologic: https://docs.djangoproject.com/en/1.8/intro/tutorial01/ is written for Python 3. If I'm going to create a Django example for https://github.com/pdurbin/addressbookmvc should it be in Python 2 or 3?
01:12 prologic IHMO both
01:13 prologic But that's just me; a lot of folk don't share this opinion
01:13 prologic There is *very* good reasoning behind my stance though
01:13 prologic A lot of lirbary authors and large software systems still use and rely quite heavily on Python 2.6 (in some cases) and many more on Python 2.7
01:14 prologic you can push and shove all you like but the reality is Python 2.x isn't going away any time soon (not yet)
01:14 prologic 2.7.10 was released only a short while ago
01:14 prologic so I think even the core Python devs know this
01:14 prologic it's like the whole IPV4/IPv6 thing :)
01:15 prologic I *always* develop for both Python 2/3 (2.6+ atm)
01:15 pdurbin prologic: I mean just for the addressbookmvc example. what did you do for the circuits example?
01:18 prologic written for both
01:18 prologic which I'll have to rewrite now :)
01:20 pdurbin yeah, sorry about that. miscommunication :)
01:20 pdurbin prologic: ok, so your code is backwards compatible you're saying, maybe even back to python 2.6
01:21 pdurbin http://railslide.io/virtualenvwrapper-python3.html seems helpful if I want to try python 3 on my ubuntu box
01:22 prologic normally it is yeah
01:22 prologic oh doing Python2/3 isn't really that hard IHMO
01:23 prologic mkvirtualenv -p /usr/bin/python3.4 py34
01:23 prologic I have Python 2.6, 2.7, 3.2, 3.3, 3.4 and PyPy on my desktop at home :)
01:24 pdurbin huh. interesting. maybe that -p is all i need
01:25 prologic it should be
01:25 prologic sudo apt-get install python-3.4
01:25 prologic and mkvirtualenv -p
01:25 prologic develop in regular Python 2.x virtualenvs
01:25 prologic and switch to py34 for testing Python3 compat
01:25 prologic use the six library where appropriate
01:26 * pdurbin looks at https://pypi.python.org/pypi/six
01:27 pdurbin yeah, -p seems to have worked, thanks!
01:30 prologic nps!
01:30 prologic if you're doing to do this too btw
01:31 prologic and +1 for you taking up Python and a django version
01:31 prologic stick in the scaffolding mentione din my draft blog
01:31 prologic so it's ready for production dpeloyment :)
01:31 prologic you can even make life eaiser on yourself and do development that way too
01:31 prologic shove in whatever db you want to use
01:32 prologic link it against the django app
01:32 prologic etc
01:32 prologic just use the django-admin.py service
01:32 prologic it'l be good enough
01:32 pdurbin oh, I was going to follow https://github.com/twoscoops/django-twoscoops-project
01:32 prologic and if you point a wildcard dns at your host
01:32 prologic and use autodock
01:32 prologic you can do full production-like testing on your ddv machine
01:34 prologic I think that's fine
01:34 prologic but you can combine the two
01:34 prologic one's more about setting up the dev enviornment
01:34 prologic what I'm suggesting is also setup the build/deploy/integration environment too
01:34 prologic so still develop locally against your virtualenv
01:34 prologic then do things like: docker-compose up
01:34 prologic for full testing
01:35 pdurbin or vagrant :)
01:39 prologic no!
01:39 prologic :P
01:40 prologic I mean it's "okay" if you follow the same approach as "immutable infrastructure"
01:40 prologic and not fall back into the habit of provisioning a machine :P
01:40 prologic this is your chance to really give Docker a go :P
01:40 prologic I've already very carefully documented 1/2 the steps :)
01:46 pdurbin :)
01:47 pdurbin really I'm just trying to compare JSF to Wicket to Django (and someday circuits when the UI is server-side))
01:50 prologic alright :P
01:51 pdurbin possibly rails or node or whatever else
01:51 pdurbin I'll see what gets contributed. :)
01:53 prologic sure sure
01:53 prologic nps
01:53 prologic perhaps can we do something else then
01:53 prologic as a compromise
01:53 prologic as part of the spec
01:53 prologic I know I haven't commented on the citkets of late (been quite busy and overwhelemd with other things)
01:53 prologic sometimes just chatting is eaiser/quicker
01:53 prologic we should describe what it should expose/etc
01:54 prologic so every example exposes a little web server on port 8000
01:54 prologic or something
01:54 prologic any database used has to have a shell script that sets up whatever it needs to get the database going (assuming a fresh db)
01:55 prologic just something that would make my life eaiser for when I go ahead and Dockerize all the examples and deploy them all somewhere
01:55 prologic something I can apply a blanket thing over
02:05 pdurbin you want some standardization
02:06 pdurbin sure. this can all be fodder for the spec discussion: https://github.com/pdurbin/addressbookmvc/issues/4
02:07 pdurbin heh. "If all of this is gibberish to you, just use Python 3."
02:17 prologic hah
02:18 prologic yeah just a couple of standard things is all that's needed
02:18 prologic 1. Expose the app on 8000/tcp
02:18 prologic 2. Clear state or have a script to install dependencies
02:18 prologic 3. Clearly state or have a script to setup any dependent dadtabase (if any).
02:19 prologic scripts are preferable obviously
02:26 pdurbin I'd say scripts are required for this stuff, since it's optional and free hosting anyway. :)
02:27 pdurbin anyway, started a django branch but I only pushed because I got to the end of the first page of the tutorial and need to get some sleep: https://github.com/pdurbin/addressbookmvc/tree/django
02:27 pdurbin the new database migration stuff seems nice. I think I last did this tutorial for django 1.4
02:32 prologic yeah
02:32 prologic I agree
02:32 prologic let's make that mandatory
02:32 prologic otherwise it'll make my job too hard :)
02:32 prologic yeah django-south (I think it is) is quite nice
02:32 prologic similar to SA's migration stuff
05:06 sivoais joined #sourcefu
11:45 aditsu joined #sourcefu
12:20 pdurbin I'm not sure if the native stuff is based on south or not.
12:20 pdurbin prologic: SA? what's that?
16:13 dotplus pdurbin: api de-emphasized.
16:14 dotplus The point of the API section is (merely) documentation about how the app should behave. Not that an API must be implemented.
16:15 dotplus I'm assuming that the significance of the capitalization of SHOULD/MUST is not lost?
17:56 aditsu joined #sourcefu
19:22 aditsu joined #sourcefu
19:44 aditsu joined #sourcefu
20:35 aditsu joined #sourcefu
21:33 prologic pdurbin, SA == SQL Alchemy
21:33 prologic a Python database agnostic ORM
21:33 prologic one of the most widely used next to Django's ORM itself
21:47 pdurbin oh
21:55 pdurbin I've heard of it.
21:55 pdurbin dotplus: sounds like there's a commit for me to check out.

| Channels | #sourcefu index | Today | | Search | Google Search | Plain-Text | plain, newest first | summary

http://sourcefu.com