Hello again Andre!

On Fri, Jul 1, 2011 at 7:58 AM, Andre Terra <andrete...@gmail.com> wrote:
> The standard really seems to be having a 'templates' folder for each app,
> but I think I did the same in my first 'hello world' project.

That's good to hear! :)

That's what I have been doing for all of my recent apps:

app/
    templates/
        base.html
        app/
            base.html
            foo.html

One of the things I love about the Django templating language is that
I can then put a templates folder at the root level of my project:

project/
    templates/
        base.html
        app/
            base.html
            foo.html

And, for example, the "new guy" can trump my app-specific templates...
Which means I always have a base look/feel tied to my app (sorry to
state the obvious here.)

Django rocks. :)

> I usually put that at the *bottom* of the settings.py file, and give each
> app's settings file a different name which usually follows an
> app_settings.py format.
> So basically something like this should work:

That's cool!

So, putting it at the bottom allows you to trump any setting already
defined in the main settings file... Nice.

I should search DjangoSnippets for a snippet that would dynamically
import any app/appname_settings.py files... Seems like a piece of code
like that would be pretty handy.

> Which brings us to my next point. I recently decided (out of the blue,
> haven't seen anyone else do it) to use the same solution to differentiate
> ...<snip>...
> to the repo, ssh into the server, pull from the repo, kill python and reload
> the production page.

Oooh, now that's cool!!!

At my work, we normally just develop on a dedicated testing server and
then copy/paste code over to our live server...

I really need to start testing on my local machine... Seems like most
people do as you say, and pull/push from GitHub or BitBucket, work
locally, and then push things back up to the main repo.

Ok, so, here's my weekend todo list:

1. Hone Python skills:

* Google's Python Class
http://code.google.com/edu/languages/google-python-class/

* Dive Into Python
http://diveintopython.org/

2. Install (on my local machine)/update/learn more about Macports and VirtualEnv

* Practice using github to push/pull projects/apps.

> Sounds like you might be on your way to writing a truly reusable app, nice!
> I need to do that one of these days. I've never packaged anything for pip,
> but I promise to give it a try next month.

It's nice to have had the experience... Not that I have, or will,
build anything worth sharing (outside of my work)... It's just nice to
know how it's done. Thanks for the inspiration!

> Again, congrats and best of luck!

You too! Thanks again Andre, I really appreciate the help and advice. :)

Cheers,
Micky

-- 
Micky Hulse
Web Content Editor
The Register-Guard
3500 Chad Drive
Eugene, OR 97408
Phone: (541) 338-2621
Fax: (541) 683-7631
Web: <http://www.registerguard.com>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Reply via email to