Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Docker release #54

Closed
daerup opened this issue Oct 31, 2024 · 8 comments
Closed

New Docker release #54

daerup opened this issue Oct 31, 2024 · 8 comments
Assignees
Labels
question Further information is requested

Comments

@daerup
Copy link

daerup commented Oct 31, 2024

Could you release a new docker image that includes the new providers?

@maelgangloff
Copy link
Owner

Hello @daerup,
I just released v0.4.0. Docker images are being built from source.
Let me know if you have any issues with them.

@maelgangloff maelgangloff self-assigned this Oct 31, 2024
@maelgangloff maelgangloff added the question Further information is requested label Oct 31, 2024
@daerup
Copy link
Author

daerup commented Oct 31, 2024

Hi, just deployed the newest version. When adding the namecheap connectons, an error pops up regarding ClientIP: clientIMG_20241031_224617.jpg

@vinceh121
Copy link
Contributor

Apologies for the lack of documentation about this, but Namecheap requires that we communicate the outgoing IP address at every API call.
As a result, you need to set the environment variable OUTGOING_IP to your public IP.
Also remember to whitelist this same IP address in your Namecheap settings.

@daerup
Copy link
Author

daerup commented Oct 31, 2024

Great thank you, now it works! Do you perhaps know if there is a setting for max purchase price? Also is it possible to test the connector, so that in case the domain becomes available everything works out?

I also notices that some TLD do not work (.ch for example). Is there anything I can do?

@maelgangloff
Copy link
Owner

Some RDAP servers are not officially published by IANA, they seem to be functional though. I refer you to issue #41.
You just need to create a symbolic link to include the few RDAP servers I found:

ln -s custom_rdap_servers.example.yaml custom_rdap_servers.yaml

If you are using Docker, this can be configured via volumes.

I will think about a potential limitation with maximum price but if you inquire about the prices before adding a connector, you should not be surprised in theory ;)

Concerning the tests, the only test that is performed is an attempt to connect to the API when you modify a connector (@vinceh121 I think this had been implemented for Namecheap too).

@vinceh121
Copy link
Contributor

Do you perhaps know if there is a setting for max purchase price?

There currently isn't. Although if the domain is at a premium price, it won't be bought.

Also is it possible to test the connector, so that in case the domain becomes available everything works out?

While Namecheap's sandbox environment is implemented, when I developed the connector it wasn't running properly altogether. You may be able to test the sandbox by setting your env to dev. Of course, don't keep this in production afterwards.

@daerup
Copy link
Author

daerup commented Nov 1, 2024

Perfect thank you! Btw. its not possible to monitor .io right? Just making sure..

Also, what is the definition for a premium price?

@vinceh121
Copy link
Contributor

The registry behind .io currently doesn't have RDAP support. You can see the deployment status here: https://deployment.rdap.org/

By premium price I mean buying premium domains.

A premium domain is either:

  • a domain that's being resold through the registrar, usually at a high price
  • a domain that's short, or comprised of only a common word, also sold at a high price

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants