Skip to content

Instantly share code, notes, and snippets.

@AnthorNet
Last active July 3, 2017 12:46
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 1 You must be signed in to fork a gist
  • Save AnthorNet/68c894ee9346896ffcd9fe37cb94ea69 to your computer and use it in GitHub Desktop.
Save AnthorNet/68c894ee9346896ffcd9fe37cb94ea69 to your computer and use it in GitHub Desktop.
EDDN - Elite Dangerous Data Network
Hi guys,
Today we release our migration plan for EDDN, it was a planned thing that should have last longer, so I apologize for the "little" rush.
Some processes, out of our control, prevented us from having more time, but the modification needed should be minimal.
Please note that the old domain for EDDN will not be renewed on August 14th 2017, marking the end of the migration process.
The migration will occur from now to August 14th 2017. Please read the instruction carefully and ask questions if needed.
Step 1: The new gateway and relay for EDDN are already online. The new relay is relaying messages from the new gateway, but also the old one.
Applications using the old gateway should now start sending the new one. It is as easy as changing the gateway URL into your application.
To avoid multiple updates of your applications to clients, we ask you to also update the schema URI to their new canonical.
The new gateway will convert them to the old URI until the end of the migration process.
This step will occur from July 5th 2017 until July 21th 2017.
Update http://eddn-gateway.elite-markets.net:8080 to https://eddn.edcd.io:4430
Update http://schemas.elite-markets.net/eddn/commodity/3 to https://eddn.edcd.io/schemas/commodity/3
Update http://schemas.elite-markets.net/eddn/commodity/3/test to https://eddn.edcd.io/schemas/commodity/3/test
Update http://schemas.elite-markets.net/eddn/shipyard/2 to https://eddn.edcd.io/schemas/shipyard/2
Update http://schemas.elite-markets.net/eddn/shipyard/2/test to https://eddn.edcd.io/schemas/shipyard/2/test
Update http://schemas.elite-markets.net/eddn/outfitting/2 to https://eddn.edcd.io/schemas/outfitting/2
Update http://schemas.elite-markets.net/eddn/outfitting/2/test to https://eddn.edcd.io/schemas/outfitting/2/test
Update http://schemas.elite-markets.net/eddn/blackmarket/1 to https://eddn.edcd.io/schemas/blackmarket/1
Update http://schemas.elite-markets.net/eddn/blackmarket/1/test to https://eddn.edcd.io/schemas/blackmarket/1/test
Update http://schemas.elite-markets.net/eddn/journal/1 to https://eddn.edcd.io/schemas/journal/1
Update http://schemas.elite-markets.net/eddn/journal/1/test to https://eddn.edcd.io/schemas/journal/1/test
Note that the new EDDN is using HTTPS, thus the change of port.
Step 2: Application using the old relay should start using the new relay, and start using both the old and the new URL for schema.
The JSON schema specification implies that the schema ID should be a reachable canonical URI, it was not the case for a long time, but will be fixed now.
Start listening to both URI so that Step 1 if not finished doesn't cause you much trouble. The old gateway message are still relayed to the new Gateway.
This step will occur from July 21th 2017 until August 11th 2017.
Update tcp://eddn-relay.elite-markets.net:9500 to tcp://eddn.edcd.io:9500
Add https://eddn.edcd.io/schemas/commodity/3
Add https://eddn.edcd.io/schemas/commodity/3/test
Add https://eddn.edcd.io/schemas/shipyard/2
Add https://eddn.edcd.io/schemas/shipyard/2/test
Add https://eddn.edcd.io/schemas/outfitting/2
Add https://eddn.edcd.io/schemas/outfitting/2/test
Add https://eddn.edcd.io/schemas/blackmarket/1
Add https://eddn.edcd.io/schemas/blackmarket/1/test
Add https://eddn.edcd.io/schemas/journal/1
Add https://eddn.edcd.io/schemas/journal/1/test
Step 3: All applications using the new gateway should have switched to the new schema. We will restart the gateway and relays to not accept the old schema URI and activate the new ones.
This step will occur on August 11th 2017.
Github: https://github.com/EDSM-NET/EDDN
Status page: https://eddn.edcd.io/
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment