Thanks for the thorough email. Hopefully somebody else can tell you more about what you did bc I'm not that familiar with the Django internals, but shared hosting is just hard to navigate. (I assume you are using a shared hosting account, thus the sudo command - run as administrator - doesn't work.) I don't think it's possible to give comprehensive instructions on how to install Django on a shared hosting account. In my experience, they all work pretty differently. I'd open a support ticket with your hosting provider, and see if they have advice on how to install Django.
That said, I agree that somebody with your experience should be able to go to djangoproject.com and learn how to install a dependent app. On Fri, Sep 17, 2010 at 1:51 PM, Thomas <t...@jumpingrock.net> wrote: > My first post on this list. I wish to try out a blogging app developed > in Django, called Mango, and according to its instructions I just need > to get Django installed. I'm looking for a little guidance with this. > Also, I'd like to determine just what kind of mess I've created with > my attempts at installation so far. > > I'm essentially a non-programmer, though I don't mind using the > Terminal in OS X now and then, and I've learned a little PHP. I heard > Mango mentioned on the Markdown discussion list. > > Steps taken so far: > > 1. Per instructions at mango.io/docs/, I downloaded > Django-1.2.3.tar.gz (to my desktop, since no destination was > mentioned). > > 2. Uploaded it to my domain via FTP. Again, since the docs mention no > destination, I put it in the same directory as my home page. I know > this is probably not the location the developers intended, but, > finding no mention of what they DO intend, I figured this location > would either cause the subsequent steps to work or harmlessly fail. > > 3. Consulted my host's instructions on how to open an SSH connection, > and, using Terminal, navigated to the Django file I'd uploaded. > > 4. Per instructions at djangoproject.com for "Installing an official > release", I ran "tar xzvf Django-1.2.3.tar.gz", changed to the new > Django directory, and ran "sudo python setup.py install". When > authentication failed (and for what reason, I have no idea, as I used > the same password), I ran "python setup.py install" instead. > > 5. A lot of stuff went by on the screen, and I saw that one of the > last lines said that the command to modify "python/site-packages" (OR > SOMETHING LIKE THAT, SO PLEASE DON'T QUOTE ME) had failed due to > denial of permission. > > Well, my home page still is up, and I haven't received any calls or > emails from my ISP (the always-excellent Tiger Technologies, at > tigertech.net). So even though the install command made SOMETHING > happen, it appears harmless for now. But I'd really like to know what > I just did to my server and its files, not to mention my bits of MySQL > database left over from playing with WordPress and Sphider. > > If nothing else comes of this, I'd like to at least point out that the > Django documentation assumes a lot of prior knowledge about these > things. It may be common knowledge for programmers, but not for > everyone who might wish to try out a Django-dependent app. > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to django-us...@googlegroups.com. > To unsubscribe from this group, send email to > django-users+unsubscr...@googlegroups.com<django-users%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
