{"action":"created","issue":{"url":"https://api.github.com/repos/EasyEngine/site-command/issues/77","repository_url":"https://api.github.com/repos/EasyEngine/site-command","labels_url":"https://api.github.com/repos/EasyEngine/site-command/issues/77/labels{/name}","comments_url":"https://api.github.com/repos/EasyEngine/site-command/issues/77/comments","events_url":"https://api.github.com/repos/EasyEngine/site-command/issues/77/events","html_url":"https://github.com/EasyEngine/site-command/issues/77","id":341485300,"node_id":"MDU6SXNzdWUzNDE0ODUzMDA=","number":77,"title":"Allow provision for wildcard certificate for all site-types","user":{"login":"mrrobot47","id":25586785,"node_id":"MDQ6VXNlcjI1NTg2Nzg1","avatar_url":"https://avatars1.githubusercontent.com/u/25586785?v=4","gravatar_id":"","url":"https://api.github.com/users/mrrobot47","html_url":"https://github.com/mrrobot47","followers_url":"https://api.github.com/users/mrrobot47/followers","following_url":"https://api.github.com/users/mrrobot47/following{/other_user}","gists_url":"https://api.github.com/users/mrrobot47/gists{/gist_id}","starred_url":"https://api.github.com/users/mrrobot47/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mrrobot47/subscriptions","organizations_url":"https://api.github.com/users/mrrobot47/orgs","repos_url":"https://api.github.com/users/mrrobot47/repos","events_url":"https://api.github.com/users/mrrobot47/events{/privacy}","received_events_url":"https://api.github.com/users/mrrobot47/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":8,"created_at":"2018-07-16T11:41:10Z","updated_at":"2018-07-16T15:59:09Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"Currently, EasyEngine only issues a wildcard certificate for `subdomain` multisite type. There should be a provision to allow the generation of wildcard certificate for any site-type. This would be helpful when someone has to create multiple sub-sites of the same, then it would be very simple to reuse the wildcard certificate instead of generating a new one every time. Also, it will ease the maintenance.\r\n\r\n```bash\r\nee site create example.com --le=wildcard\r\nee site create one.example.com --le # will use the above wildcard domain\r\nee site create two.example.com --le # will use the above wildcard domain\r\n```"},"comment":{"url":"https://api.github.com/repos/EasyEngine/site-command/issues/comments/405296700","html_url":"https://github.com/EasyEngine/site-command/issues/77#issuecomment-405296700","issue_url":"https://api.github.com/repos/EasyEngine/site-command/issues/77","id":405296700,"node_id":"MDEyOklzc3VlQ29tbWVudDQwNTI5NjcwMA==","user":{"login":"rahul286","id":4115,"node_id":"MDQ6VXNlcjQxMTU=","avatar_url":"https://avatars2.githubusercontent.com/u/4115?v=4","gravatar_id":"","url":"https://api.github.com/users/rahul286","html_url":"https://github.com/rahul286","followers_url":"https://api.github.com/users/rahul286/followers","following_url":"https://api.github.com/users/rahul286/following{/other_user}","gists_url":"https://api.github.com/users/rahul286/gists{/gist_id}","starred_url":"https://api.github.com/users/rahul286/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rahul286/subscriptions","organizations_url":"https://api.github.com/users/rahul286/orgs","repos_url":"https://api.github.com/users/rahul286/repos","events_url":"https://api.github.com/users/rahul286/events{/privacy}","received_events_url":"https://api.github.com/users/rahul286/received_events","type":"User","site_admin":false},"created_at":"2018-07-16T15:59:09Z","updated_at":"2018-07-16T15:59:09Z","author_association":"MEMBER","body":"@mbtamuli is this LetsEncrypt limitation or SSL in general?\r\n\r\nDNS system allows `aplha.one.example.com` or `mars.aplha.one.example.com` to resolve to A/CNAME value set for `*.example.com`.\r\n\r\n\r\n\r\n"}}
{"actor":{"display_login":"rahul286"}}