#django

Throwing code away is the best bit of programming.

yeah I'm not worried about throwing code away, but effort

throw away your boss

+1

chasonchaffin: do it anyway... get s'more experience

well the alternative is just to work on my own projects :D

how is that different... really? :)

working on an API to create ruby-ized Japanese text right now

the ruby markup is so crazy ugly

this is my first stab at writing a conversion function: https://github.com/chason/ruby-converter/blob/m...

not very pretty but it works

chasonchaffin: This one? https://developer.mozilla.org/en-US/docs/Web/HT...

hackvana yeah

I have used it for Chinese

I wanted to see what the cross browser support was like, but typing out an entire paragraph of ruby text was kind of a nightmare so I decided to program something to do it for me

<ruby><rb>旧<rb>金<rb>山<rt>jiù<rt>jīn<rt>shān<rtc>San Francisco</ruby>

yeah lovely isn't it

also that does not render well in Chrome :(

the jiù appears above the　金　but everything else appears in tiny script to the side of the 山.

unfortunately the rtc tag isn't supported by Chrome at all but this markup style gets a bit closer to what it should look like (I think, no experience with Chinese) https://codepen.io/chasontherobot/pen/YePKQK

That uses ruby extensions: http://darobin.github.io/html-ruby/

yeah I really need Jukugo to be supported well which... well, it isn't

browser support for ruby markup is suprisingly bad

chasonchaffin: https://codepen.io/anon/pen/ZrYzxj

A django templatetag may help

ah probably wouldn't be a bad idea either

FunkyBob: I did the quick start for uwsgi and have something working for django based on the tut, now wondering how to serve https and if I need nginx at all?

anyway looking at the docs

nix64bit: no, you don't need nginx to do https...

there's also a handy http-to-https option

and performance scalability? I image adding threads would help

I will read the docs

bonjello

foxmask: you well?

nix64bit: FunkyBob wrote it, so you know it's good: http://ugu.readthedocs.io/en/latest/

hackvana: I read that thanks, thats why I was pestering him

FunkyBob: That'll learn you

:)

nix64bit: scalability is in the doc... it can go a LONG way

and if you fill up one box, there's a design pattern in that doc for spreading across many boxen

just in case one day you know :)

aye

nix64bit: I have VPSs using the emperor to run many sites... each site with up to 4 workers, 4 threads per, and offload workers

thats sounds great, as a one man circus that sounds like a simple plan

I am a one man circus, I wasn't insinuating anything about you btw ;)

well, I do that hosting as a one man show, too

It appears that if I specify a 'TEST' with an alternate 'NAME' in my DATABASES, Django still expects the prior existence of the non-test database.

(when running `manage.py test`)

Why should it care that the non-test database exist when running tests? It already knows it should use a different database.

Wow, it is, in fact trying to query the non-test database. This is really messed up.

oh?

do you have code somewhere that queries on import?

In one of my test files, yes.

don't

The DB connection won't be changed yet when you do that.