Contributors mailing list archives
Re: Recommended Contributor Tooling (RCT)by
at the moment it has been lost during the Bash to Python rewrite of the Launcher, but Voodoo run also had some port shifting intelligence when you launch several project at the same time. We would like to have it back...
Basically of course the user could type all the Docker run options and run the akretion/voodoo image manually. But well the Voodoo Python launcher is here to let user just type just "voodoo run" with no risk of error and frustration. So on windows that could eventually be "vagrant up" until Docker compose get mature on Windows which will also probably happen soon given Microsoft investments on Docker.
Ok, I understand the port shifting is indeed something more intelligent, which we cannot have with standard tooling. What would you thing of rewriting this part of voodoo in go and just compile it? This could be the perfect fit for this tooling? This would be even genious, because it could also take care of setting up the git hup repo correctly with upstream and origin tracking branches and probably implementing git-flow for the convenience of the user. This would be really WOW! :D It would standardize the way, we at OCA would use github elegantly. NICE NICE NICE!
El dom., 18 oct. 2015 a las 20:23, Raphaël Valyi (<firstname.lastname@example.org>) escribió:
also David,at the moment it has been lost during the Bash to Python rewrite of the Launcher, but Voodoo run also had some port shifting intelligence when you launch several project at the same time. We would like to have it back...Basically of course the user could type all the Docker run options and run the akretion/voodoo image manually. But well the Voodoo Python launcher is here to let user just type just "voodoo run" with no risk of error and frustration. So on windows that could eventually be "vagrant up" until Docker compose get mature on Windows which will also probably happen soon given Microsoft investments on Docker.Regards.On Sun, Oct 18, 2015 at 10:57 PM, Raphaël Valyi <email@example.com> wrote:David,basicallly what sucks in Odoo is the the repo is huge. So a large part of the Voodoo Python launcher is made to create the options of the docker run command, specially which folder you'll mount to share your Odoo repo (Odoo is too much of a buggy moving target to be bundled inside the image and it's to heavy to be downloaded always).Alternatively I thought about putting the Voodoo inteligence inside the portable Linux image and like running it twice: one to first output the run options and then eval the command of the second run. That's e technique used by Consul https://github.com/gliderlabs/docker-consul/tree/legacy#runner-command but again sadly that wouldn't work on Windows.Voodoo also have a few other useful commands. We often use "voodoo new project_name" to bootstrap a new project and hack on something.Overall, I think the Voodoo Python launcher is useful. But what I think is we can have 80% of the useful features in just 20 lines of Ruby in a Vagrantfile. Then "voodoo run" would be just "Vagrant up" on windows and sharing a project would just work (not the advanced Docker compose feature but f*ck Windows right...)So again, pull request for a such a Vagrantfile would be greatly appreciated in Voodoo.Regards.Hi Raphael, I'm right now analyzing in detail the docker onboarding guide, that's just a bliss. I'll rewrite it for OCA. THE thing is: We can probably completely drop docker-compose and just work with the priviledged flag, to run multiple containers within the first. thise moves tooling environment definition out of the user machine and into a second layer easily managable via a DOCKERFILE... I'll keep you posted, if that might work...Thank you nhomar for your opinion.It is indeed a valuable point, but it is not breaking, because:a) Easier is always better then complicated.b) I'm willing to take on the challenge. So I hope, once testable the scope might be reconsidered upon the final thing.In the end, we have multiple error layers when someone want's to get started on hacking openobject framework, among them are:virtualisation, autoreloading, debugging, editor, templating, prototyping, python environment, os environment (external dependencies). Some of them take weeks to understand and solve, and for some, there is such a flood of possibilities that chances are high you just give up on the way. This means valuable brainpower lost. (It doesn't serve us someone finding out how to setup his stack, it only serves us someone contributing openobject code, so let's get them there in no time! And this marginal contribution can possibly be the so hardly needed reviewing activity...)I think this is why broadening the scope, once we have a viable solution is worthwhile..Guys, share me some enthusiasm! :) That could be more fun for everyone...Best, DavidOn Sun, Oct 18, 2015 at 2:38 PM, David Arnold <firstname.lastname@example.org> wrote:Sorry, you just don't want to burden this onto someone who just want's to get started. Even to us it might be an obvious error. It's not the user's fault, that this is not working. It is the programmer's (as almost always) ...I insist... you are trying to solve an issue far away from the objective of odoo's project.If somebody want install odoo and is new and do not understand that error, need to google 2 or 3 minutes and will find the solution.Even it is better if you recommend 2 or three reads before start.odoo developer bookIf you buy i.e Mac or Windows apps.... the next next buttons will make you some questions which th documentation explains conceptually what they are, but if the user do not have tha minimal knowledg you can not expect the system will solve a connection to their brains to teach alá matrix!Regards.