31–36 of 36 posts
Maybe it's just the avalanche of HN traffic but I can't get to your pricing tab (or the others)
Earlier quoted context omitted.
Thank you for your interest. sub-domains would works, but the container will be destroyed after 120 seconds for this demo. Of course it persist in production environment (soon).
I think 120 seconds is really short, say 10-15 minutes would be better for demo.
Earlier quoted context omitted.
Given that they warned against using it in repos and even Twitter handles [1], it’d be a wise choice to use some other name. [1] https://www.zopyx.com/andreas-jung/contents/dont-use-docker-...
Not allowing people to call their custom docker tooling "docker-custom-tooling" on eg. Github seems like they're shooting themselves in the foot. Of course, it might be bad and damage their brand, but it could also enable a great ecosystem of surrounding tooling, some of which they could bless if they wanted to. Imho a poor PR move.
Our Marks consist of the following registered, unregistered and/or pending trademarks, service marks and logos which are subject to change without notice: Docker, Docker “Moby Dock” whale logo and the stylist representations of a container, octopus, and other entities in our original works of authorship, DOCKER HUB, RUNHUB, LIBCONTAINER, LIBTRUST, LIBCHAN, LIBSWARM, LIBPACK, DOCKER SWARM, DOCKERIZE IT, CLAY
In this case, "Docker" is the trademark we're looking at, and specifically registered with a capital D it appears
Any permitted use must not falsely imply or suggest a sponsorship or endorsement by, or a partnership or affiliation with Docker.
I don't think the author is being malicious in any way of course but from a quick glance, I couldn't say for sure that it's not a Docker product (design guidelines aside)
The Docker mark is used only in a referential context or for naming Docker or to indicate compatibility, and not in a title of a program, domain name, website, product or service
This is essentially the key distinguisher between the parent comment and the OP's site
---
Anyway, it's not so much that I'm pro-Docker or anything, it's more that they don't really have a choice legally. If companies don't protect the use of their copyrights/trademarks etc, they are diluted and risk the chance of becoming "generic". Having said that, it can definitely go overboard and lead to frivolous DMCAs, lawsuits etc etc
All this aside, while I'm not sure I have a use for the site (most things I dockerise use a compose file w/ multiple containers), it seems like a neat project so keep it up :)
Without an ecosystem of services to integrate (Identity/Storage/DB/Queue/DNS/LB/Network/etc), containers aren't awfully useful.
What is the differentiator?
EDIT: grammar