Community mailing list archives

community@mail.odoo.com

Re: OCA Command Line Interface

by
Akretion, Raphael Valyi
- 10/22/2015 14:31:12
And David,

if you really want to work on the Golang launcher able to launch containers able to Rum Odoo the OCA way (with the recipe), then please instead of spamming the community mailing lists, join efforts with Fabo Grehm on this project https://github.com/fgrehm/devstep-cli

At Akretion we nearly used it for Voodoo, but at the end we used our own Voodoo Docker compose launcher because:
  • 8 months ago devstep was not configurable enough
  • we wanted to have a perspective of easy Windows/Mac experience, but at that time the Golang Docker client wasn't working on Windows/Mac. I'm not sure were it stands now. At least we had the Vagrant perspective.
  • we have some real advantages of using Docker Compose for complex projects with a Wed or even Apache Solr microservices
  • we felt comfortable writing a suitable launcher in Bash or then Python but not so much completing devstep-cli in Golang with our time constraints.
But if you really want to do something useful in Golang, I suggest you team with Fabio on that. The day you complete devset-cli enough, at Akretion we would happily make Voodoo just a Devstep plugin. But that wasn't realistic until recently.

Now, this is annoying because you come here and reuse our project name (changing the spelling) and use the OCA name as you had a grant form it. This is annoying.

I think this is now a great time to prove us you are not TROLLING.

Thanks.

On Thu, Oct 22, 2015 at 4:19 PM, Raphaël Valyi <rvalyi@akretion.com> wrote:
Please David,

don't spoil the codename of our mature project for your experiments.

Regards.

On Thu, Oct 22, 2015 at 3:37 PM, David Arnold <dar@devco.co> wrote:
Hello,

due to recent vivid discussions in the contributors mailing list, I have independently started work on a oca command line interface.

Objective:
It shall cover everything to get you started with hacking odoo on you local machine. Deployment to servers and production instances is not yet of a concern, as there is little chance to have some consensus on a standard way at this point. Furthermore, this is probably not what is most needed.

Status:
Basically, what you find in the repo is a raw copy/port of the go command. Once set up your go environment (https://golang.org/doc/install), you can fetch and compile it with just one single command "go install github.com/blaggacao/vodoo". Then you can play around typing the "vodoo" command. It will work out of the box on mac windows and linux.

It is currently in an open design phase, and I'd like to gather your input.

Action Path:
I do not want to repeat the common error to come up with a complete solution developed in an isolated silo accessing only limited knowledge and disregarding other's use case and ideas.

This is, why I would like you to take part in the definition, what such a tool should do, and also what it should not do. Please just make a PR on the README (which lays out the plan) so we can discuss ideas in an isolated manner.
Please refer to contributing for how to take part in this in just 3 clicks: https://github.com/blaggacao/vodoo/blob/master/CONTRIBUTING.md

Execution:
Once there is considerable consensus and prioritization, I would start porting one by one. Anyone who want to take part in this adventure and learn exiting new stuff about the sweat spots of a modern programming language like go, please step out. This is even more fun, when done together and sharing the learning curve!

Thanks a lot and best regards!

David Arnold

_______________________________________________
Mailing-List: https://www.odoo.com/groups/community-59
Post to: mailto:community@mail.odoo.com
Unsubscribe: https://www.odoo.com/groups?unsubscribe




--



--
Raphaël Valyi
Founder and consultant
+55 21 3942-2434