IIRC This was on purpose so the rendering results could be hosted and/or
served by a separate host (or CDN).

I don't think this actually breaks this functionality, but maybe you
should add a comment saying that if RENDERING_RESULT_URL starts as an
URL, it will be used as such to achieve this kind of purpose.

/Max

* [email protected] <[email protected]> [2012-03-27 16:15:48]:

> From: Gael UTARD <[email protected]>
> 
> Signed-off-by: Gael UTARD <[email protected]>
> ---
>  www/settings_local.py-template |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/www/settings_local.py-template b/www/settings_local.py-template
> index e5e0a0d..e3e4855 100644
> --- a/www/settings_local.py-template
> +++ b/www/settings_local.py-template
> @@ -42,7 +42,7 @@ DATABASE_PORT = ''             # Set to empty string for 
> default. Not used with
>  OCITYSMAP_CFG_PATH = None
>  
>  RENDERING_RESULT_PATH = '/path/to/rendering/results/'
> -RENDERING_RESULT_URL = 'http://local.server.name/results/'
> +RENDERING_RESULT_URL = '/results/'
>  RENDERING_RESULT_FORMATS = ['png', 'svgz', 'pdf', 'csv']
>  RENDERING_RESULT_MAX_SIZE_GB = 10
>  
> -- 
> 1.7.5.4
> 
> 
> 

-- 
Maxime Petazzoni <http://www.bulix.org>
 ``One by one, the penguins took away my sanity.''
Writing software in California

Attachment: signature.asc
Description: Digital signature

Reply via email to