Change sample URL from islandora-docker.com to ? about isle HOT 24 CLOSED

Posting @hamhpc 's question on 11/27 from the ISLE-Steering Slack Channel for further context.

[10:44 AM]
another question... if islandora-docker.com is a real IP (islandora-docker.com has address 165.227.127.99) and someone doesn't add an entry for 127.0.0.1 in their local hosts file.. won't they end up actually visiting your Digital Ocean server thinking they are on their local machine?

Just wondering if this might be a potential problem. I know personally I'd be interested in having a DNS name that actually resolves to 127.0.0.1 so they we don't have to update /etc/hosts and so that we are assured to get to the proper server in our browsers?

from isle.

^ Per @hamhpc's comments, I concur and feel that we should remove the current demo URL and replace it with a clearly "fake/example" one e.g. isle.dev or isle.local etc.

@dmer @dwk2 @hamhpc @McFateM @sgoldste Shall we discuss on Friday to resolve please?

And to be clear, changing the URL shouldn't be dramatic in effort or time but will require me to do a little fixing and testing prior to moving on.

from isle.

from isle.

from isle.

Actually... I'm not opposed to a real address... I just think that this name should point to the IP 127.0.0.1 then there shouldn't be any confusion and you won't end up on some host out on the cloud. Maybe since BD has purchased the domain and it is real does it make sense make one there? Like maybe isle.islandora-docker.com? Then just update the DNS to add subdomain isle.islandora-docker.com to point to 127.0.0.1. How does something like that sound?

from isle.

I'm going to advocate for the practice that I use, but as long as we adopt consistent names, I'll accommodate it.

In my practice, anything that is local to my machine gets a top-level domain name of ".local". I frequently do development work in other locations so the names that make sense to me are isle-dev.local, on my machine, and isle-dev.dev, anywhere else.

I always have to deploy to something.grinnell.edu, it's the only real choice I have, so I like to include the intent of the server in the subdomain name, that way I can have isle-dev.grinnell.edu or isle-test.grinnell.edu, or isle-prod.grinnell.edu when necessary, and make sure they are not easily confused with my .dev or .local equivalents.

Sorry @dwk2, but when I see "your_isle_server_name" I'm still left guessing... Does it have to be the server's 'hostname', or can it be anything I like, or are there names I cannot or should not use? I'd rather nail it down and be consistent than leave folks wondering about what they can or can't use.

from isle.

Hmm.. I'm wondering if this is even an issue anymore lol. previously we had to massage the /etc/hosts file which is where this actually cropped up from. But now as I run through the install I don't need to do anything with /etc/hosts since the hostname is taken care of when the machine is OS'd before installing docker containers. So since we don't need to mess with it really I wonder if it doesn't really matter anymore and Gavin can use whatever he likes? Sorry to complicate a simple thing ;-).

from isle.

from isle.

from isle.

I like isle.local the best so far. Using this as hostname.domain-name format then I'd tend to think if you over-rode the domain name you could bring this up as isle. fairly easily? I think the .dev would indicate it's always development and beg the question then what about .prod? Personally, for us we'd end up with an isle.hamilton.edu and for dev do isle-dev.hamilton.edu for the main hostnames.

from isle.

from isle.

.local is supposed to be for multicast DNS. It should work fine but might(?) clash with Apple Bonjour or MS Active Directory. .localhost and .test are explicitly reserved TLDs for our purpose.

Note that .dev will stop working in chrome soon if you don't have https.
https://medium.engineering/use-a-dev-domain-not-anymore-95219778e6fd

from isle.

That's a great comment and I was also thinking that maybe isle.localdomain? I wonder if this is better since it's more like localhost.localdomain? Overall great point!

from isle.

+1 for isle.localdomain

(another non-routable domain that shouldn't collide with reserved .localhost and or .test)

from isle.

from isle.

+1 ... hopefully @th5 will give us a thumbs up/down as well to this proposition =).

from isle.

from isle.

from isle.

.localhost is reserved for exactly this purpose. Maybe we should use that? That would be the "right" way.

I think basically anything would be fine. Just avoid .dev

from isle.

from isle.

from isle.

Ok I'll +1 .localhost too.

I'm not sure I get the reasoning per se ... since localhost.localdomain is what's used in /etc/hosts. I guess my question is if .localhost is the proper way to name, then why do the OS's come with localhost.localdomain as the localhost entry. Shouldn't it be localhost.localhost then? I really don't know the rules for this which is why I ask. Overall, I'm sure it's somewhat trivial as we're all mostly going to rename these hosts to fit into our domain names anyhow. So let's not hold this up and just go with what everyone is happy with =). Thanks all for chiming in on this!

from isle.

Sorry to shift gears. Maybe .test would be better? I hadn't considered the use case where I'm trying to provision an instance somewhere else on the network. Some implementations redirect all .localhost addresses to localhost. I guess this is why software devs need IT too.

.test ?

from isle.

Closing ticket. New alpha2 images use isle.localdomain (currently branch new-dev2 has updated information. Branches to be merged post Alpha testing.)

from isle.