Rather than the structure you suggest, it might be better to think
about your exhibition projects not as django projects, but as django
apps. Replace pyA and pyB with root/pyA and root/pyB (e.g. make your
php directories a peer of the django root...conceptually, of
course...you're Python f
I have what is a very naive question though I didn't find a close
enough post that answered what I think is a very general question.
I work at a museum and inherited a site done in php (the coding is
very problematic but this is not the issue). I will overhaul the site
and would like to use Pytho
2 matches
Mail list logo
