Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Avatar

Re: DNS Connector

by
LasLabs, Dave Lasley
- 19/08/2016 12:21:57
We have plans for a route53 connector, so I would say that a repo of its own would be a good idea. 


-Dave Lasley

On Aug 18, 2016, at 23:38, Jay Vora <vora.jay@serpentcs.com> wrote:

Excellent job!

Would be so good if it goes to OCA.

On Fri, Aug 19, 2016 at 11:38 AM, Eric Caudal <eric.caudal@elico-corp.com> wrote:

Hi,

We have developed time ago a DNS connector framework and created a specific one for dnspod.cn.

Basically it allows to manage all your domain in the ERP and trigger API calls to the DNS provider via Odoo framework.

We have 2 main modules currently in v8 (we will migrate them eventuallyto v9):

* connector_dns which creates the basic objects related to domain management

* connector_dnspod which is specific to dnspod.cn provider (create/delete update DNS Entries)


We plan to have as well another one for dnspod.com

Today there is repo for this kind of connector in the OCA: would it make sense to create a connector_dns to host them?

Looking forward to reading you
--
Eric Caudal [Founder and CEO]
Skype: elico.corp. Phone: + 86 186 2136 1670 (Cell), + 86 21 6211 8017/27/37 (Office)
Elico Shanghai (Hong Kong/Shenzhen/Singapore) Odoo Gold Partner, best Odoo Partner 2014 for APAC

_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe





--

The Splendid journey of 4 years in Numbers
---
Regards,
----------------------------------------------------------------------------------------------------------------------------
Jay Vora
Managing Director


 
Direct: +91-9879354457
Office: +91-9033472982
Skype: jaynvora
Twitter : jaynvora
   
-------------------------------------------------------------------------------------------------
Visit our website : http://www.serpentcs.com
Please consider the environment before printing this email

Reference