I'll try to replicate the WebDAV part with nginx, I guess it will be easy if not easier. I was thinking of a local directory rsync'ed frequently.
I'll take a look into the builder to see if I can implement it in my own VPS. I haven't created my Metacello configuration yet (shame on me...) Regards, Esteban A. Maringolo 2014/1/2 Norbert Hartl <norb...@hartl.name>: > > Am 01.01.2014 um 19:26 schrieb Esteban A. Maringolo <emaring...@gmail.com>: > > Pharo as a community has support to use its CI server, among other > goodies such as SmalltalkHub. > > But what if your code is not public and you want to have a central > repository and continuous builds? > > Has anybody ever wrote a guide to develop with Pharo in the context of > private development? > > So far I managed to work with a file based repo and a set of > workspaces to create a new working image or to prepare it for > deployment. But I want to automate it as much as I can. > > I do what you want to do. I have a central server that I use for code > storage and for the CI builds. Have a look at [1]. There you can read how > you can easily create a http repository for monticello. I just create sub > directories for every project on my server and the rest just works. > The next step would be to install jenkins and add [2]. The jenkins server > then just uses the http repository you created before. > If you need help on this just ask. > > Norbert > > [1] http://norbert.hartl.name/blog/2009/06/08/public-monticello-repository/ > [2] https://github.com/renggli/builder >
