The JIRA issue is here[1], according to which we need to configure the new
domain name in our server, i.g. 47.56.99.112
@Dan @Hanks Zhang Could you
have a look? I remembered the nginx server is in some of your hands.
[1] https://issues.apache.org/jira/browse/INFRA-19577
Best Regards,
YorkShen
申远
Willem Jiang 于2019年12月23日周一 上午9:15写道：
> Hi I just found
> editor.weex.apache.org and editor.weex.io are point to the same
> machine 47.56.99.112.
> But there is no service for the editor.
>
> We may need to setup the nginx to send the redirect URI of
> editor.weex.apache.org for the request of editor.weex.io.
> We also need to setup the https service endpoint to do the same redirect.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Sat, Dec 21, 2019 at 11:54 PM 任 跃兵 wrote:
> >
> > The url [1] now shows 'Welcome to nginx!'
> > The url [2] is not found.
> > Looks like some configuration needs to be done on the server 47.56.99.112
> >
> > [1]http://editor.weex.apache.org/
> > [2]https://editor.weex.apache.org/
> >
> > 发件人: 申远
> > 发送时间: 2019年12月16日 16:14
> > 收件人: dev
> > 主题: Re: [DISCUSS] What should we handle editor.weex.io ?
> >
> > Hi, all.
> >
> > 1. The server of Weex Editor will be host on the IP address of
> 47.56.99.112
> > > (Alibaba Cloud Server)
> > > 2. Establish the following DNS record.
> > > 47.56.99.112 A editor.weex.io
> > > editor.weex.apache.org CNAME editor.weex.io
> > > 3. Keep the disclaimer [1] as it is(Maybe reword it later), and use
> > > editor.weex.apache.org in our document, discussion and any other
> secnario
> > > we coud have.
> > >
> > > With approach above, the existing Weex user could still use
> editor.weex.io
> > > without interruption. And for ASF's concern, only one DNS change
> records is
> > > needed.
> > >
> > > If this is not enough for protecting ASF's trademark, maybe we could
> > > convince our committer to donate the domain name to ASF and let ASF
> paid
> > > for it. But that's another story, and I'd like to implement the
> approach I
> > > mentioned above first if there is no objection.
> > >
> > > [1] "Disclaimer | 免责声明Apache Weex, Weex and Apache are either
> registered
> > > trademarks or trademarks of the Apache Software Foundation in the
> United
> > > States and/or other countries, and are used with permission as of
> 2014. The
> > > Apache Software Foundation has no affiliation with and does not
> endorse or
> > > review the materials provided at this website, which is managed by
> Alibaba."
> > >
> >
> > I am forwarding the conclusion we have in private mailing list to this
> > mailing list for your information.
> >
> > Best Regards,
> > YorkShen
> >
> > 申远
> >
> >
> > 申远 于2019年12月5日周四 下午5:24写道：
> >
> > > Technically speaking, DNS CNAME doesn't equal to HTTP redirect. No
> matter
> > > whether there is a CNAME for editor.weex.io, the browser always shows
> > > editor.weex.io in its URL bar if you type in editor.weex.io.
> > >
> > > But yes, we could solve the problem by redirecting editor.weex.io to
> > > editor.weex.apache.org by HTTP 301.
> > >
> > > Best Regards,
> > > YorkShen
> > >
> > > 申远
> > >
> > >
> > > Jan Piotrowski 于2019年12月5日周四 上午2:54写道：
> > >
> > >> The domain is not used to host any content, it just redirects to other
> > >> URLs
> > >> that host the actual content: ASF servers for Apache Weex things,
> random
> > >> other server for random other content.
> > >>
> > >> But do what you think best, I will disengage from this topic after
> this
> > >> message.
> > >>
> > >> J
> > >>
> > >> Am Mi., 4. Dez. 2019 um 07:55 Uhr schrieb 申远 :
> > >>
> > >> > Based on the conservation with ASF, Brand Management, I don't think
> it
> > >> will
> > >> > satiffy ASF's requirement if we keep it in our hands. From my
> > >> > understanding, we either take it down or give it to ASF.
> > >> >
> > >> > *As said by several people several times, Weex is a trademark of
> ASF and
> > >> > using weex in domain domain name also violate the legal right of
> ASF.*
> > >> >
> > >> > Best Regards,
> > >> > YorkShen
> > >> >
> > >> > 申远
> > >> >
> > >> >
> > >> > Jan Piotrowski 于2019年12月4日周三 上午4:29写道：
> > >> >
> > >> > > I already sent somthing similar in the other thread, so repeating:
> > >> > > If the editor code is not part of Apache Weex, it should live on
> its
> > >> own
> > >> > > domain.
> > >> > > Keep the weex.io domain around so old links continue to work, but
> > >> > redirect
> > >> > > the main domain to the Apache Weex site and the editor subdomain
> to
> > >> the
> > >> > new
> > >> > > external subdomain.
> > >> > >
> > >> > > I am happy to sponsor the cost for weex.io for the first year to
> > >> whoever
> > >> > > takes over the domain: https://www.domcomp.com/tld/io
> > >> > >
> > >> > > ASF does not have to be involved here at all if this is just a
> user
> > >> > project
> > >> > > for Weex in my opinion, which clearly states this via e.g.
> "Editor for
> > >> > > Apache Weex". Agree M
