I am interested mainly in django. I see in the control panel domains, subdomains, applications, and websites, and then django projects and django apps. It seems all of them have choices involved around naming. I have some confusion about how I can useful name these.
domains I get a free call on. subdomains should be simple and meaniful to end users There are some reasons to avoid duplication. If I had multiple operational domains I need to have the subdomains unique anyway because these are also going to be control panel website names. Then I can construct an control panel application name out of the concateation of the subdomain and the * app category*. I think I can away with this since I do not think a control panel website will have more than one app from the same category. For the website name, I guess I reuse the subdomain name, which as you recall was globally unique.
Now the project directory name is located under a directory named after the control panel website name? So its path is unique and will always be *myproject". The django app names will be unique on the internet, and thus have a unique path. But I am confused as to how to think about
manage.py startapp myappname
I know myappname is not to be the name of a python module, because of conflict error messages. I am not sure what startapp does...
So, I wonder if my attempt at naming conventions for myself is taking the correct things into account.
Thank you for your consideration.
asked Feb 08 '11 at 21:43
Thank you for your answer.
I interpret an aspect of it as:
I do not need a tight naming convention even for myself.
If I have a naming convention for myself, there is no reason to socialize it.
So perhaps a matter of taste. Alas, I am used to environments with tight naming conventions, highly socialized.
Now, beyond that, and not addressing character set issues, I tried to identify external constraints on naming. There I note if I have foo.bar.com and foo,cheese.com and name two sites foo then in a flat websites directory structure I think I am in trouble. If I have that tendency to name the site after the subdomain, then I need to pause and think, and here I try a bit to do that.
answered Feb 08 '11 at 22:27
Consider the control panel apps my_drupal and forum. I create them as control panel apps. They are going to default to ~/websites as directories. Okay so far? Now when I do do the control panel website for mysite.com, I will generate some sort of proxy relationship such that https://mysite.com/ serves from my_drupal and https://mysite.com/forum serves from forum. Okay so far? If I was doing the doc, I would make the urls explicit to help the clueless.
An interesting aspect of this is it seems to me the control panel website widgets allow the url that goes to the control panel app forum to be something unrelated in naming such as https://mysite.com/flaming. Okay so far?
Yah, I know I am slow :-)
So instead of the above control panel apps let us create
control panel apps my_django, my_static, my_wsgi and a control panel website that links them up together. It seems to me I sort of need all three? and connected somehow. Now the one I really really never worked with the wsgi app.
But here is a bit of a clue.
Not a lot right in house. And there were a couple challenges.
So I get a screen with a standard html search widget and then there is a fancy search widget on the right. The first does not work at all. Here might be the url:
The fancy "search the documentation" widget returns nice results. I feel they might link to the text quoted rather than an index which is fairly long, much below the fold, and which I have to carefully inspect and then click on an index item to get to the quoted text.
Hmm, this is much too long and is more a usability narrative. Let me here pause and see what tomatoes I need to dodge. :-)
answered Feb 09 '11 at 12:02