On 11/5/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
about the CatWalk part. it's a little *feature* it was, i have notice
that table also it's call catwalkstate or something. and it's use to
hold the default cols values. as in show id, or column name,etc.
Anyway what i wanted to say is
One more thing. I have my app installed in the target machine (.egg)
using prod.cfg. TG assumes that the path to the database (file) exists
(e.g. you have taken care of creating it using tg-admin) or it rather
creates it if it doesn't exist? I had some problems when not creating
the database a
On 11/4/05, Aggelos Orfanakos [EMAIL PROTECTED] wrote:
One more thing. I have my app installed in the target machine (.egg)
using prod.cfg. TG assumes that the path to the database (file) exists
(e.g. you have taken care of creating it using tg-admin) or it rather
creates it if it doesn't
my quick and dirty way:
use the none-root installation for Turbogears
Then just tarball the whole directory of it and send to the target
machine. So long the base system is relatively compatible(x86 won't
work on PPC), this is the easiest. It also has the advantage of self
contained and don't
I did it! I didn't use mod_rewrite (I've never managed to learn how to
use this module), just mod_proxy. It can also serve static content. My
mistake was using /static/css/blah.css in my templates, instead of
static/css/blah.css (notice the initial '/' missing). Although I
don't know *why* it
That works for me too. In fact, this is what I do (with the difference
that I don't make a tarball and use scp -- I have an SVN repository on
the host machine and execute svn checkout on the target machine).
Anyway, after *a lot* of effort, I got the whole thing running. I don't
know if it's me,
I don't know what system you are using but debian(which I run) has some
standard deamon helper things which should make daemonizing arbitary
program relatively easy.
Beside, I don't mind the manual procedures of setting apache proxy and
the like as I would like to know what I am doing rather
(I meant install TG in the target machine and transfer my app directory
there.)
Aggelos,
While I have not deployed a TG app myself, there are a few ways to go
about it. It seems, so far, that you have 2 options in deployment:
Mod_python or Lighttpd.
Take a look here:
http://trac.turbogears.org/turbogears/wiki/DocumentationPlayground
What I meant was, is there an easy way to _move_ my app between
systems. Like, move a single file and then install it on the target
system? For example, many packages only require that you do: $ python
setup.py install
And what about the TG components? How can I make a machine in which TG
isn't
Aggelos Orfanakos wrote:
It worked like a charm. Thanks for your help.
Note also that as long as the setup.py lists TurboGears as a
requirement, it should be possible for somebody to install your
application with just the .egg and easy_install - including the
installation of TurboGears itself,
I've managed to get to my app through Apache and mod_proxy (in fact,
using mod_rewrite with a rule flagged as [P]). The only problem now
seems handling static files. For example, CSS and images files included
and showing up in my development environment, do not show up in the
target machine
12 matches
Mail list logo
