On Wed, Jun 25, 2008 at 2:13 AM, MOD Films <[EMAIL PROTECTED]> wrote:
>
>
> OK, I found the script in /usr/bin (not /usr/local as per doco). And
> running this with or without prod.cfg doesn't work as below...
>
> I also don't know why the /usr/lib/python2.4/site-packages/
> remixabletv-1.0-py2.4.egg dir doesn't actually contain a prod.cfg so
> how is it supposed to be referenced

You need to copy the prod.cfg to your production server.
Read below.
http://lucasmanual.com/mywiki/TurboGears#head-de467aa25a5591a3b2826a2728342c3c242a3606
Normally you copy sample-prod.cfg to prod.cfg and move over your settings.


Lucas

>
> seed:/# start-remixabletv
> TurboGears requires autoreload.package to be set. It can be an empty
> value, which will use CherryPy's default behavior which is to check
> every module. Setting an actual package makes the check much faster.
> Unhandled exception in thread started by
> Error in sys.excepthook:
>
> Original exception was:
>
>
> I put the autoload lines into prod.conf (although apparently not
> needed) but still no luck. Some threads suggest you need to provide
> prod.cfg as argument...
>
> This is my prod.cfg below.
>
>
>
>
> [global]
> # This is where all of your settings go for your production
> environment.
> # You'll copy this file over to your production server and provide it
> # as a command-line option to your start script.
> # Settings that are the same for both development and production
> # (such as template engine, encodings, etc.) all go in
> # remixabletv/config/app.cfg
>
>
> # DATABASE
>
> # driver://username:[EMAIL PROTECTED]:port/database
>
> # pick the form for your database
> # sqlalchemy.dburi="postgres://[EMAIL PROTECTED]/databasename"
> # sqlalchemy.dburi="mysql://username:[EMAIL PROTECTED]:port/
> databasename"
> # sqlalchemy.dburi="sqlite:///file_name_and_path"
>
> # If you have sqlite, here's a simple default to get you started
> # in development
> sqlalchemy.dburi="sqlite:///%(current_dir_uri)s/proddate.sqlite"
>
>
> # SERVER
>
> autoreload.on = True
> autoreload.package="remixabletv"
>
> server.socket_host="127.0.0.1"
> server.socket_port=8081
>
> server.environment="production"
>
> # Sets the number of threads the server uses
> server.thread_pool = 1
>
> # if this is part of a larger site, you can set the path
> # to the TurboGears instance here
> # server.webpath=""
>
> # Set to True if you are deploying your App behind a proxy
> # e.g. Apache using mod_proxy
> base_url_filter.on = True
>
> # Set to True if your proxy adds the x_forwarded_host header
> base_url_filter.use_x_forwarded_host = True
>
> # If your proxy does not add the x_forwarded_host header, set
> # the following to the *public* host url.
> # (Note: This will be overridden by the use_x_forwarded_host option
> # if it is set to True and the proxy adds the header correctly.
> #base_url_filter.base_url = "http://staging.remixable.tv:";
>
> # Set to True if you'd like to abort execution if a controller gets an
> # unexpected parameter. False by default
> # tg.strict_parameters = False
>
> # LOGGING
> # Logging configuration generally follows the style of the standard
> # Python logging module configuration. Note that when specifying
> # log format messages, you need to use *() for formatting variables.
> # Deployment independent log configuration is in remixabletv/config/
> log.cfg
> [logging]
>
> [[handlers]]
>
> [[[access_out]]]
> # set the filename as the first argument below
> args="('server.log',)"
> class='FileHandler'
> level='INFO'
> formatter='message_only'
>
> [[loggers]]
> [[[remixabletv]]]
> level='ERROR'
> qualname='remixabletv'
> handlers=['error_out']
>
> [[[access]]]
> level='INFO'
> qualname='turbogears.access'
> handlers=['access_out']
> propagate=0
>
>
>
>
>
> On Jun 24, 11:27 pm, "Lukasz Szybalski" <[EMAIL PROTECTED]> wrote:
>> On Tue, Jun 24, 2008 at 4:48 AM, Florent Aide <[EMAIL PROTECTED]> wrote:
>>
>> > On Tue, Jun 24, 2008 at 9:34 AM, MOD Films <[EMAIL PROTECTED]> wrote:
>>
>> >> Hi
>>
>> >> Some issues with this page
>> >>http://docs.turbogears.org/1.0/DeployWithAnEgg
>>
>> > No you don't need to unpack the egg manually.
>>
>> > Which script are you searching for ? If this is for tg-admin is is in
>> > you python script dir. (on windows generaly "c:\python25\scripts").
>>
>> > If you are speaking of your own application the script should be
>> > along-side the tg-admin script.
>>
>> > On windows you should use the .exe files in the script dir (ie:
>> > start-yourproject.exe, not start-yourproject-script.py).
>>
>> > If the script name for your own app does not suit your taste you can
>> > always change it by editing setup.py in your application source code
>> > and changing the relevant console_scripts entry in the entry_points
>> > dictionnary.
>>
>> Or you can switch to mod_wsgi, and let the apache control when the app
>> should be 
>> started/killed/reloaded...etc.http://lucasmanual.com/mywiki/TurboGears#head-36b7eef1526da4fe58c7373...
>>
>> Lucas
> >
>



-- 
Where was my car manufactured?
http://cars.lucasmanual.com/vin
TurboGears Manual-Howto
http://lucasmanual.com/pdf/TurboGears-Manual-Howto.pdf

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to