Use nip.io instead of xip.io for jupyter domain suggestion
What does this MR do?
Uses nip.io instead of xip.io for jupyter domain suggestion
Are there points in the code the reviewer needs to double check?
no
Why was this MR needed?
It seems like nip.io is more stable/performant:
nip.io is a blatant rip-off of xip.io, with one big difference: NIP.IO is powered by PowerDNS with a simple, custom PipeBackend. So, it actually works :) (no messy, custom DNS server here!)
Minishift preferred nip.io too https://github.com/minishift/minishift/commit/aafa268f4965dda559cb7c16bc6817b5bb93aae1
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated -
API support added -
Tests added for this feature/bug - Conform by the code review guidelines
-
Has been reviewed by a UX Designer -
Has been reviewed by a Frontend maintainer -
Has been reviewed by a Backend maintainer -
Has been reviewed by a Database specialist
-
-
Conform by the merge request performance guides -
Conform by the style guides -
If you have multiple commits, please combine them into a few logically organized commits by squashing them -
Internationalization required/considered -
End-to-end tests pass ( package-and-qamanual pipeline job)
What are the relevant issue numbers?
Edited by Grzegorz Bizon