[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Social-mediagoblin] Config branch merged, new server running comman

From: Christopher Allan Webber
Subject: Re: [Social-mediagoblin] Config branch merged, new server running command(s)
Date: Mon, 20 Jun 2011 09:53:11 -0500
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux)

So "server" is the paste server configuration.  This says, "Hey,
mediagoblin is running at this URL (with this middleware), we're serving
some static files here, etc".  It's just for paste's ability to serve
things specifically.

mediagoblin.ini or the application config file is for changing the way
the actual application is configured.  This is stuff like, what email
address are errors sent from?  How many items per page?  Things like
this.  (Celery is also configured here also.)

To prevent confusion and after speaking with Will on the phone, I've
renamed server.ini to paste.ini to indicate that it's only for
./bin/paste's "launching a server"'s sake.

Thanks for bringing this up!

will kahn-greene <address@hidden> writes:

> I don't understand the difference between "server" and "application" here.
> What are "server" and "application" in this context?
> On 06/19/2011 04:39 PM, Christopher Allan Webber wrote:
>> Several things else of note:
>>   - There are now two config files, server.ini and mediagoblin.ini.
>>     Configuring the server launching via paste deploy is the former,
>>     configurating the application is now the latter.
>>   - You now have access to the config data in
>>     mediagoblin.mg_globals.global_config (the whole config file)
>>     mediagoblin.mg_globals.app_config (just the ['mediagoblin'] section)
>>   - We now have auto-type-conversion, validation, and defaults in the
>>     config file.  If you are adding new config parameters, you can do so
>>     in:  mediagoblin/config_spec.ini
>>   - The application is *much* easier to initialize if you are writing
>>     code that initializes the application itself.  All you have to do is:
>>       >>>  from import MediaGoblinApp
>>       >>>  myapp = MediaGoblinApp('path/to/mediagoblin.ini')
>>     ... the application will handle setting up globals in mg_globals and
>>     etc for you.
>> If you have any questions let me know!  Thanks again, Bernard!

𝓒𝓱𝓻𝓲𝓼𝓽𝓸𝓹𝓱𝓮𝓻 𝓐𝓵𝓵𝓪𝓷 𝓦𝓮𝓫𝓫𝓮𝓻

reply via email to

[Prev in Thread] Current Thread [Next in Thread]