[ckan-dev] [ckan-discuss] How to install extensions for a package installation?

Thu Sep 8 16:31:49 UTC 2011

I just installed ckan from source on the same machine and tried to add
the admin extension but it threw errors that it can not find such a
module. So I tried another extension, disqus. This seemed to work. So
I believe the admin extension is broken. I went on with the disqus
extension and set up a disqus account and so on. When I finally ran
the server (no errors) and went on a data package page, there was no
disqus comment box. I don't know what's wrong there. I tried the
wordpress extension, too. Same result. Nothing. I can't provide any
error messages or stuff because there is none.

I'm really lost here.

2011/9/7 Florian Marienfeld <florian.marienfeld at fokus.fraunhofer.de>:
> +1 for the confusion :-)
>
> for me installing plugins into the deb-installation worked, as long as I
> ignored the virtual environment bit. and ignored the mild terror
> stemming from running the plugin's $(python setup.py develop) as sudo.
>
> But for developing and testing it would be nice to have a separate ckan
> instances on the same machine, but honestly - and I think this is Max's
> problem, too - I dont understand how all the bits and pieces are bolted
> together to form one instance:
>
> - ckan-python-code
> - python libraries
> - .ini
> - apache
> - ckan-extensions
>
> Maybe this is clear to people who installed ckan in the early days, for
> us APT-kiddies it is confusing.
>
> Apart from that, thanks for the great work, it's a pleasure to use and
> hack CKAN.
>
> Best regards,
>
> FLO
>
>
>
> On 07.09.11 18:22, Max Ludwig wrote:
>> Hey,
>>
>> thanks for this really fast response!
>>
>> I did everything what is said under "Prepare to Use Extensions". What
>> I don't understand: I installed the package (the DEB from your source
>> using apt-get). It runs very fine using apache+wsgi (I didn't even
>> have to deploy it). And now I have to create a python environment
>> somewhere else (in my case: /home/max/ckan)? How is that supposed to
>> work? I mean, how can ckan (installed using DEB package and lying
>> somewhere in /usr/share and /usr/lib and having its config files in
>> /etc/ckan) find these plugins installed in a virtual environment owned
>> by my user?
>>
>> 2011/9/6 David Read <david.read at okfn.org>
>>> Ok, I can help! Is it the wording that is the problem? Or maybe it's
>>> one of the steps:
>>> 1. Can you find the extension's "setup.py" file?
>>
>> No. In step 1 it says /home/ubuntu/pyenv for the virtual environment
>> but in step 2 its ~/var/srvc/ckan.net/pyenv. I don't understand.
>>
>>> 2. Can you find the name of the extension in the setup.py?
>>
>> No.
>>
>>> 3. Do you know which is your "CKAN config file"?
>>
>> Yes. It is /etc/ckan/std/std.ini
>>
>>> 4. Can you edit the "ckan.plugins" line to include the name of the extension?
>>
>> Yes. But when I did this, the server crashes giving me a
>> "PluginNotFoundException: admin".
>>
>>
>> Maybe we can play the whole thing through using ckanext-admin (
>> https://bitbucket.org/okfn/ckanext-admin ) as example.
>>
>> Max
>>
>> _______________________________________________
>> ckan-dev mailing list
>> ckan-dev at lists.okfn.org
>> http://lists.okfn.org/mailman/listinfo/ckan-dev
>
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ckan-dev
>