{"action":"created","issue":{"url":"https://api.github.com/repos/docker/docker/issues/15549","repository_url":"https://api.github.com/repos/docker/docker","labels_url":"https://api.github.com/repos/docker/docker/issues/15549/labels{/name}","comments_url":"https://api.github.com/repos/docker/docker/issues/15549/comments","events_url":"https://api.github.com/repos/docker/docker/issues/15549/events","html_url":"https://github.com/docker/docker/issues/15549","id":100698390,"number":15549,"title":"Dockerfile naming convention","user":{"login":"pleerock","id":1753397,"avatar_url":"https://avatars.githubusercontent.com/u/1753397?v=3","gravatar_id":"","url":"https://api.github.com/users/pleerock","html_url":"https://github.com/pleerock","followers_url":"https://api.github.com/users/pleerock/followers","following_url":"https://api.github.com/users/pleerock/following{/other_user}","gists_url":"https://api.github.com/users/pleerock/gists{/gist_id}","starred_url":"https://api.github.com/users/pleerock/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pleerock/subscriptions","organizations_url":"https://api.github.com/users/pleerock/orgs","repos_url":"https://api.github.com/users/pleerock/repos","events_url":"https://api.github.com/users/pleerock/events{/privacy}","received_events_url":"https://api.github.com/users/pleerock/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/docker/docker/labels/area/builder","name":"area/builder","color":"0052cc"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-08-13T06:19:50Z","updated_at":"2016-02-15T19:12:06Z","closed_at":"2016-02-15T19:12:06Z","body":"When there are lot of dockerfiles in a project \"How do I name them\" question is coming. Docker community need to came up with a good convention, something better then \"Dockerfile\".\r\n\r\nSomething I can suggest is:\r\nuse `.dockerfile` extension. This give us at least these two good opportunities. \r\nFirst, we can name files this:\r\n`nginx.dockerfile`\r\n`php.dockerfile`\r\n`app.dockerfile`\r\n`mysql.dockerfile`\r\n...\r\nor:\r\n`ci.dockerfile`\r\n`development.dockerfile`\r\n`production.dockerfile`\r\n\r\nSecond it will give IDEs to understand what this file is, use an icon for it, and implement syntax highlighting."},"comment":{"url":"https://api.github.com/repos/docker/docker/issues/comments/184350552","html_url":"https://github.com/docker/docker/issues/15549#issuecomment-184350552","issue_url":"https://api.github.com/repos/docker/docker/issues/15549","id":184350552,"user":{"login":"duglin","id":1944671,"avatar_url":"https://avatars.githubusercontent.com/u/1944671?v=3","gravatar_id":"","url":"https://api.github.com/users/duglin","html_url":"https://github.com/duglin","followers_url":"https://api.github.com/users/duglin/followers","following_url":"https://api.github.com/users/duglin/following{/other_user}","gists_url":"https://api.github.com/users/duglin/gists{/gist_id}","starred_url":"https://api.github.com/users/duglin/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/duglin/subscriptions","organizations_url":"https://api.github.com/users/duglin/orgs","repos_url":"https://api.github.com/users/duglin/repos","events_url":"https://api.github.com/users/duglin/events{/privacy}","received_events_url":"https://api.github.com/users/duglin/received_events","type":"User","site_admin":false},"created_at":"2016-02-15T19:12:06Z","updated_at":"2016-02-15T19:12:06Z","body":"The problem with this is that any tooling that is built would need to know the name of each Dockerfile. The advantage of promoting (but not requiring) it be called `Dockerfile` is that generic tooling will just work w/o any customization.  Beyond that, if customization I needed, I think (as evidenced by the lack of discussion on this PR) its simply each user's choice and not something we need to try to standardize.\r\n\r\nI'm going to close this one - if there's interest in reopening it (based on an influx of discussion) we can do so."}}