[Freedombox-discuss] Tools to speed up development on the freedombox

Stefan Cocora stefan.cocora at googlemail.com
Fri Mar 16 00:28:43 UTC 2012

root at debian:~# uname -a
Linux debian 3.2.0-2-amd64 #1 SMP Sun Mar 4 22:48:17 UTC 2012 x86_64
root at debian:~#
root at debian:~#
root at debian:~# lsb_release -a
No LSB modules are available.
Distributor ID:	Debian
Description:	Debian GNU/Linux testing (wheezy)
Release:	testing
Codename:	wheezy

It is done, the wheezy vagrant VM has been finalized !

1. Prerequisites:

- Virtualbox 4.1.X lastest 4.1.10 would be preferable
- vagrant 1.0 - it comes as a deb
http://downloads.vagrantup.com/tags/v1.0.1 . You might also be able to
find it in the wheezy repos if I'm not mistaking.
- ruby, I have 1.8.7. I haven't had the time to try it on ruby 1.9, it
should work

2. Get the vagrant box and bring it up(the vagrant box will be
downloaded just the first time):

git clone --recursive git://github.com/stefancocora/freedombox_dev.git
cd freedombox_dev
vagrant up

2.1 When you're done hacking:
- from inside the VM you can access the external freedombox_dev
directory by going to /vagrant/
- save your work there
- either vagrant halt to shut down the VM or vagrant destroy to remove
the VM completely and be left just with the code in freebombox_dev/ .
More info in the docs below.

3. Docs : http://vagrantup.com/docs/getting-started/index.html

	I've put in some puppet code to make sure we have some default packages
and a custom motd. We can add much more to this. Puppet ensures we all
have the same base VM.

	Ideally there would be a continuous integration server running Jenkins
hooked to all git repositories for plint/privoxy/etc. After a commit on
one of these repos Jenkins would fetch the code, run any available
tests, build the .deb file and put it in an apt accessible repository.
	Then puppet would be able to install and manage it. Puppet works on top
of a distro's package manager, it is not meant to deal cleanly with
make/make install.
	This approach would speed up considerably the cycle of commit code -
test new code - feed the results back - start over, some would say agile
development. I like to keep it simple by illustrating the cycle.
	For the moment I don't have the resources necessary for a Jenkins
continuous integration server. If anyone can provide a VM for this I can
help to install/configure it.

PS: I've used github to host the vagrant box(you'll see it the first
time you do vagrant up), if it becomes unmanageable I can try minus.com.
Sourceforge failed to let me register in all the browsers that I've
tried :( .


On 14/03/12 13:28, Stefan Cocora wrote:
> Vagrant knows to download files only via http and local file as far as I
> know.
> If I make a torrent you'll have to download it manually then import it.
> If it is on an http location then vagrant does all the steps for you
> automatically: download, import, vagrant up.
> Regards,
> Stefan
> On 14/03/12 12:38, Pierre Alexandre SCHEMBRI wrote:
>> Torrent file ?
>> 2012/3/14 Stefan Cocora <stefan.cocora at googlemail.com>:
>>> I've finished building the base OS.
>>> Anyone has any suggestions were can we host a 450MB file ? Github
>>> doesn't look doable to me. Maybe I've missed some way of hosting files
>>> on Github without actually putting them in a repository.
>>> It needs to be world accessible via http.
>>> When each of us will start vagrant for the first time it will need to
>>> download this file.
>>> Regards,
>>> Stefan
>>> On 11/03/12 14:43, Stefan Cocora wrote:
>>>> Hi all,
>>>>    Apart from veewee, vagrant and puppet are already packaged for debian.
>>>>    As a first step I'll create a vagrant box based on debian wheezy with
>>>> some puppet code to get a standard working environment. I'll put it on
>>>> github once it is ready. It will be an organically  growing repo as
>>>> requirements come in for additional packages/config files to add.
>>>>    I've browsed Laurent Bigonville's(vagrant packager) debian qa page
>>>> and I've seen he has started to package veewee as well. I'll be in touch
>>>> with him to check on veewee packaging.
>>>>    Another think that I want to look into , given time, is to create a
>>>> qemu box from Bdale's freedom installer. Not sure if that is possible at
>>>> this stage ...
>>>>    I'll let you all know once I have the vagrant box up on github.
>>>> PS: I've been using vagrant/puppet to test, on a local VM, the packages
>>>> and configs that I install on my dreamplug for 6 months now.
>>>> Regards,
>>>> Stefan
>>>> On 10/03/12 15:46, Sean Leonard wrote:
>>>>> On 03/09/2012 01:41 AM, Jonas Smedegaard wrote:
>>>>>> On 12-03-08 at 07:58pm, Nick M. Daly wrote:
>>>>>>> On Fri, 09 Mar 2012 00:44:59 +0000, Stefan Cocora
>>>>>>> <stefan.cocora at googlemail.com> wrote:
>>>>>>>> Hi all,
>>>>>>>> I'd like to help speed up development on the freedombox's various
>>>>>>>> software by using three established open-source tools to create
>>>>>>>> virtual machines that can be easily distributed, destroyed and
>>>>>>>> recreated... Let me know if you think this is a helpful idea for the
>>>>>>>> freedombox project.
>>>>>>> Stefan, that's wonderful!  Can you either: add that to the wiki or
>>>>>>> turn it into a set of scripts that can do some of the basic setup
>>>>>>> steps automatically?
>>>>>> Please also initiate the process of getting those tools into Debian.
>>>>>> Vagrant is packaged already but the others I believe is not.  So please
>>>>>> file ITP or RFP bugs for the others - and perhaps get in touch with the
>>>>>> Debian maintainer of vagrant and see if perhaps she/he/they are
>>>>>> interested in maintaining those too.
>>>>>> More on ITP/RFP here: http://www.debian.org/devel/wnpp/#l1
>>>>>> More on vagrnat in Debian here: packages.qa.debian.org/vagrant
>>>>> Hello all,
>>>>> I am unfamiliar with veewee, but have begun playing recently with the
>>>>> Vagrant/Puppet tools for web development uses.  I have also been
>>>>> watching Freedombox with interest, and while I don't have too much time
>>>>> for diving in to new projects, I would love to help in the testing,
>>>>> debugging, and configuration.
>>>>> I will also look into Sefan's request re: getting the tools into Debian.
>>>>> I look forward to helping this project!
>>>>> Cheers,
>>>>> Sean
>>>>> _______________________________________________
>>>>> Freedombox-discuss mailing list
>>>>> Freedombox-discuss at lists.alioth.debian.org
>>>>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
>>> _______________________________________________
>>> Freedombox-discuss mailing list
>>> Freedombox-discuss at lists.alioth.debian.org
>>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss

More information about the Freedombox-discuss mailing list