In-Development EDDN - Elite Dangerous Data Network

AnthorNet

Volunteer Moderator
EDDN - Elite Dangerous Data Network


Server Migration


EDDN is moving to a new server. This document is intended for authors of software that uses EDDN - either as a sender or a listener - and describes the (minimal) changes that you will need to make to your software to ensure that it can still communicate with EDDN after August 9th 2017.
There are two related changes:

  • The main EDDN gateway and relay have moved to a new server. The old server will be decommissioned and its DNS record allowed to expire soon after August 9th.
  • The EDDN schemas are being renamed to reflect that change, and so that they can be served from their canonical URIs.

Migration Steps

Senders



  • Change the destination address for your messages from http://eddn-gateway.elite-markets.net:8080 to https://eddn.edcd.io:4430 .
  • Change the $schemaRef property in your messages from http://schemas.elite-markets.net/eddn/... to https://eddn.edcd.io/schemas/.... i.e.:
    • Change http://schemas.elite-markets.net/eddn/blackmarket/1 to https://eddn.edcd.io/schemas/blackmarket/1
    • Change http://schemas.elite-markets.net/eddn/commodity/3 to https://eddn.edcd.io/schemas/commodity/3
    • Change http://schemas.elite-markets.net/eddn/journal/1 to https://eddn.edcd.io/schemas/journal/1
    • Change http://schemas.elite-markets.net/eddn/outfitting/2 to https://eddn.edcd.io/schemas/outfitting/2
    • Change http://schemas.elite-markets.net/eddn/shipyard/2 to https://eddn.edcd.io/schemas/shipyard/2
    • And similarly for the .../test schemas.
  • Software that does not contain these changes will cease to be able to send to EDDN on or shortly after August 9th.

Listeners



  • Change the address that you listen to from tcp://eddn-relay.elite-markets.net:9500 to tcp://eddn.edcd.io:9500 .
  • Accept both the old schemas and the new schemas. i.e. accept either http://schemas.elite-markets.net/eddn/... and https://eddn.edcd.io/schemas/... in a message's $schemaRef property.
  • Note that you will only start to receive messages with the new schema names after August 9th.

Further info



 

wolverine2710

Tutorial & Guide Writer
That was very easy migration, well done.

Now lets see what happens on August 10th.

Run Anthor run.....

Sorry the child in this 50+ old geezer woke up. I ofc knew about the change because its now running on a server of mine which also runs EdCodex. There are good reasons to move EDDN - better access to it etc. I wish Anthor all the best. Curious where this all leads to. Still it feels a bit as if a child (EDDN) moves away from home. In the beginning there was my old EDDN thread where I was looking to revive EMDN by Andreas. JamesreMuscat offered to port/code it and it was called EDDN. At the same time Erranthought of viviotech offered free hosting so things could get started. Both EMDN and EDDN are heavily based on EVE EMDR. Now EDDN in the weekends transports 250-300K messages a day and is an integral part of the third party tools community. Which I've to admit feels pretty darn good. James in the beginning did the hard work. Later Anthor came along and in the end basically took over. In the end my only contribution left to EDDN was the server. Now that that that is soon gone I'm starting suffering a bit from "empty nest syndrome". Again, Anthor I wish you all the best and I'm more then 100000% confident EDDN will flourish and grow. EDDN: Live long and prosper.
 
Last edited:
Ah, this explains some of the changes (relay change for instance) I saw on the status page.
With the (beta) community site (http://edtg.macnetron.nl) I run, I am only a listener to the queue, but the data relies heavily on it as I don't want to do (daily) eddb-imports on a Pi-clone (which takes about 19 hours :D ).

Keep up the good work on EDDN! o7!

Cmdr MacNetron
 
Last edited:

AnthorNet

Volunteer Moderator
New gateway and relay have finished their migration, the old one have been decommissioned.
 
I have been listening to the new gateway for messages since you changed over. All has been going fine but as of 28-09-2017 there have not been any commodity/outfitting/shipyard messages for the last 5 days. All I am getting is journal/test messages. You can verify this in the status screen https://eddn.edcd.io/ under schemas. Are you aware of any issues/problems?
 

AnthorNet

Volunteer Moderator
I have been listening to the new gateway for messages since you changed over. All has been going fine but as of 28-09-2017 there have not been any commodity/outfitting/shipyard messages for the last 5 days. All I am getting is journal/test messages. You can verify this in the status screen https://eddn.edcd.io/ under schemas. Are you aware of any issues/problems?
Currently the cAPI used by software to send Market/Shipyard/Outfitting data is not online. It happens with almost each release and will come back online soon.

But this is only from release, we haven't notice any hiccups before, specially not in the last 5 days.
 
Currently the cAPI used by software to send Market/Shipyard/Outfitting data is not online. It happens with almost each release and will come back online soon.

But this is only from release, we haven't notice any hiccups before, specially not in the last 5 days.
Thanks very much for clarifying. I am especially listening for commodity v3 messages, currently none are coming through. Hopefully it will come back online soon :):)

 
Got a question. Is there anything in the data network that is logging USS Drops? It might be useful to capture Thargoid Attacks and USS drops to see where they are spreading
Or even to record drops in general.
 
Top Bottom