contribution path

[Nick Coghlan]

On 14 Mar 2015 22:42, "Mads Kiilerich" <mads at kiilerich.com> wrote:
>
> On 03/14/2015 12:14 AM, Paul Nathan wrote:
>>
>> Hallo,
>>
>> I'd like to occasionally fix Kallithea bugs. I love the project and have
followed it for the past few years.
>>
>> In order to do help out, I should (1) find bugs that are small (because
I am a part timer and a newbie)! and be able to stand up a Kallithea
easily(2)! And have a source code map to where is what(3) - though those
things tend to get outdated awfully fast.

http://www.curiousefficiency.org/posts/2014/12/kallithea-on-openshift.html
describes my initial attempt at making it easy to run Kallithea demo
servers to show folks UX changes before merging them.

I still want to switch it to defaulting to the SQLite gear and easily
supporting installing from a VCS URL instead of PyPI before proposing any
additions to the upstream docs.
>>
>> etc.
>>
>> If there is no current way to do 2, may I suggest a Vagrant
configuration? I have stood them up before and they are a nice way to get a
dev environment.

Aye, Vagrant and/or Docker with SQLite as the data store is what I was
thinking as well.

Vagrant's likely the better place to start, as Docker based dev on Windows
and Mac OS X tends to rely on Vagrant anyway to spin up a suitable
container host.

Cheers,
Nick.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sfconservancy.org/pipermail/kallithea-general/attachments/20150316/9929457c/attachment.html>