[ECODP-dev] CKAN 1.8 Greenfield installation NOTES

[Dimitrios Mexis]

Hi John

Yes in deed this. It  happened, because we try to have some kind of
tag-versioning in our updates from git.

Regards


On Wed, Jun 12, 2013 at 10:31 AM, John Glover <john.glover at okfn.org> wrote:

> Hi Dimitrios,
>
> Is this on the build machine? Step 5 should not be required on
> test/production.
>
> Also, is there a way that I can supply CKAN config changes for the
> acceptance server? There will be config changes on the test server before
> the release, does it make sense for you to copy them from there or is there
> a master copy somewhere that I can edit?
>
> Regards,
> John
>
>
> On 12 June 2013 08:35, Dimitrios Mexis <dimitrios.mexis at tenforce.com>wrote:
>
>> Guys take account the following steps that I had to do in order to manage
>> installing CKAN.
>>
>> So we need to see who will adapt what I think:
>>
>> 1)  Edit the file paster.sh in $USERHOME/ckan/bin folder, and adapt the
>> file to point to $USERHOME/ckan/config/ecportal.ini instead of ecodp.ini
>>
>> [ at this stage a new template in principal must be generated , because
>> drupal is not found under /drupal rather under /www/drupal ]
>>
>> 2)  Install the postgresql rpm package   <=====DEPENDENCY RPM
>>
>> 3)  Edit the httpd.conf in order to find the wsgi .py under conf
>>
>> 4)  Assign permissions to ckan folder to ecodp:ecodp
>>
>> 5) *In folder:** **/applications/ecodp/users/ecodp/ckan/ecportal/src*
>>
>> ln -s ckanext-ecportal-release-v1.8.1 ckanext-ecportal
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.okfn.org/mailman/private/ecodp-dev/attachments/20130612/21157a43/attachment.html>