[ckan-dev] Developer Environment for Developing CKAN Plugins

[Jared Smith]

Hello Nathan,

For my particular environment, I use vagrant, setup using shared folders 
between my machine and the vm. I find this an easy way of sharing the 
same code base that allows me to edit on my machine and run the code in 
the vm.

For debugging, I haven't tried it at all, I'm not sure how difficult it 
is to setup, so I would also be interested in hearing how other devs 
have setup their env for debugging.

For developing plugins, apart from reading the docs on plugin 
development, I would advise keeping up-to-date with the pylons-to-flask 
migration. As this will affect future plugin development for newer 
versions of ckan. Other then that, the docs should provide all the 
necessary info for developing plugins.

On 2016-10-03 9:51 AM, Nathan Hook wrote:
> Good Day,
>
> We are going to start doing a reasonable amount of development on some 
> customization of CKAN via plugins.
>
> Are there any CKAN developer recommendations, hints, tips and/or 
> tricks that people use when developing plugins for CKAN?
>
> Things that we are specifically looking for help on are the following:
>
> Recommendations on how to do development in an IDE (like PyCharm) and 
> move/deploy our code to a remote Vagrant VM (where we will have 
> development instance of ckan running).
>
> How does debugging work in a remote Vagrant VM instance with WSGI? 
> Does anyone do remote debugging with an IDE (like PyCharm) and WSGI?
>
> Then in general how do most CKAN developers do their programming? Do 
> they use Vi? Do they do development in ckan on their local machine? Do 
> they use remote VMs (like with Vagrant/VirtualBox)?
>
> We have tried looking for how anyone does CKAN plugin development and 
> we have not been able to find any useful information at this time and 
> any friendly recommendations would be greatly appreciated.
>
> I have also posted this same email/post to Stackoverflow:
> http://stackoverflow.com/questions/39779531/developer-environment-for-developing-ckan-plugins
>
> Thank you for your time,
>
> Nathan
>
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> https://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev

-- 
—
Jared Smith
Highway Three Solutions Ltd.
Github: @jrods

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20161003/557d360a/attachment-0003.html>