[ECODP-dev] supervizor & celery

Mon Jun 3 16:17:09 UTC 2013

Hi Bert,

Not having the git files on the testing server will significantly slow down
our development process. Let's discuss this on the call tomorrow.

Best,

Darwin

*Darwin Peltan*

*Project Manager  |  skype: darwinp  |  twitter:
@darwin<http://twitter.com/darwin>
*

*The Open Knowledge Foundation <http://okfn.org/>*

*Empowering through Open Knowledge*

*http://okfn.org/  |  @okfn <http://twitter.com/OKFN>  |  OKF on
Facebook<https://www.facebook.com/OKFNetwork> |
Blog <http://blog.okfn.org/>  |  Newsletter<http://okfn.org/about/newsletter>
*
*
CKAN | http://ckan.org | @ckanproject <http://twitter.com/ckanproject>
|open source data management platform
*

On 3 June 2013 16:48, Bert Van Nuffelen <bert.van.nuffelen at tenforce.com>wrote:

> Hi John,
>
> quick answer:
> https://webgate.ec.europa.eu/publications/jira/browse/ODP-209
>
> Bert
>
> 2013/6/3 John Glover <john.glover at okfn.org>:
> > Hi Bert,
> >
> >>> - The .git folder seems to have been removed from the folders in
> >>> /applications/ecodp/users/ecodp/ckan/ecportal/src, do you know why?
> >>>> We do not want .git folders or svn inside there. It must be a clean
> >>>> system.
> >>>
> >>> I am not sure that I understand how having a .git folder is not clean.
> It
> >>> does however make it considerably harder for us to verify exactly which
> >>> version of CKAN and extensions you are currently running and will
> >>> generally
> >>> slow down the testing process. We also don't want to add the overhead
> of
> >>> bumping a version number somewhere every time we do a commit. This is
> >>> also a
> >>> change from the current system (that has never come up previously) so
> it
> >>> would be good if you could add these back please.
> >>>
> >>This is a security ticket from PO. So sorry no, they will not be
> included.
> >
> > Can you elaborate on this? I was unaware of this item and it's not
> obvious
> > to me how this could be a security issue.
> >
> >>> Are the config files copied here from scratch every time the package is
> >>> built? One of the config files (who.ini) is at the same path as a
> version
> >>> that comes with CKAN, so it a bit dangerous to me to have these files
> in
> >>> this location in case one is accidentally overwritten. I would
> recommend
> >>> placing them directly in the conf directory to avoid any confusion.
> Where
> >>> are there master versions of these config files that I can change if I
> >>> need
> >>> to (I assume on the build server somewhere)?
> >>>
> >>So those conf files can be placed at any location?
> >
> > Yes, although you would need to make sure that:
> > - the apache config is looking for the wsgi.py file in the conf dir
> > - the wsgi.py file is looking for ecportal.ini in the conf dir
> > - the ecportal.ini file is looking for who.ini in the conf dir
> >
> > Thanks,
> > John
> >
> >
> > On 3 June 2013 17:24, Bert Van Nuffelen <bert.van.nuffelen at tenforce.com>
> > wrote:
> >>
> >> Hi John,
> >>
> >> 2013/6/3 John Glover <john.glover at okfn.org>:
> >> > - The .git folder seems to have been removed from the folders in
> >> > /applications/ecodp/users/ecodp/ckan/ecportal/src, do you know why?
> >> >> We do not want .git folders or svn inside there. It must be a clean
> >> >> system.
> >> >
> >> > I am not sure that I understand how having a .git folder is not clean.
> >> > It
> >> > does however make it considerably harder for us to verify exactly
> which
> >> > version of CKAN and extensions you are currently running and will
> >> > generally
> >> > slow down the testing process. We also don't want to add the overhead
> of
> >> > bumping a version number somewhere every time we do a commit. This is
> >> > also a
> >> > change from the current system (that has never come up previously) so
> it
> >> > would be good if you could add these back please.
> >> >
> >> This is a security ticket from PO. So sorry no, they will not be
> included.
> >>
> >>
> >> > - The config files also currently seem to be in the virtualenv folder
> >> > (and
> >> > symlinked from the /applications/ecodp/users/ecodp/ckan/conf), is
> there
> >> > a
> >> > reason that they are not just directly in the conf directory?
> >> >>Probably because as far as I know this was the working configuration.
> >> >> Consult also this with Bert.
> >> >
> >> > Are the config files copied here from scratch every time the package
> is
> >> > built? One of the config files (who.ini) is at the same path as a
> >> > version
> >> > that comes with CKAN, so it a bit dangerous to me to have these files
> in
> >> > this location in case one is accidentally overwritten. I would
> recommend
> >> > placing them directly in the conf directory to avoid any confusion.
> >> > Where
> >> > are there master versions of these config files that I can change if I
> >> > need
> >> > to (I assume on the build server somewhere)?
> >> >
> >> So those conf files can be placed at any location?
> >>
> >> kind regards,
> >>
> >> Bert
> >>
> >>
> >> --
> >> Bert Van Nuffelen
> >>
> >> Semantic Technologies Software Architect at TenForce
> >> www.tenforce.be
> >>
> >> Bert.Van.Nuffelen at tenforce.com
> >> Office: +32 (0)16 31 48 60
> >> Mobile:+32 479 06 24 26
> >> skype: bert.van.nuffelen
> >>
> >> _______________________________________________
> >> Ecodp-dev mailing list
> >> Ecodp-dev at lists.okfn.org
> >> http://lists.okfn.org/mailman/listinfo/ecodp-dev
> >
> >
> >
> > _______________________________________________
> > Ecodp-dev mailing list
> > Ecodp-dev at lists.okfn.org
> > http://lists.okfn.org/mailman/listinfo/ecodp-dev
> >
>
>
>
> --
> Bert Van Nuffelen
>
> Semantic Technologies Software Architect at TenForce
> www.tenforce.be
>
> Bert.Van.Nuffelen at tenforce.com
> Office: +32 (0)16 31 48 60
> Mobile:+32 479 06 24 26
> skype: bert.van.nuffelen
>
> _______________________________________________
> Ecodp-dev mailing list
> Ecodp-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ecodp-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.okfn.org/mailman/private/ecodp-dev/attachments/20130603/39d58219/attachment.html>