If SSL is a concern that makes sense, I am not familiar with that enough to suggest whether another way to do this exists or not.
It will be good to check that we can set robots.txt properly from the begging if we go down this path. On Mon, May 20, 2019 at 10:54 AM Mikhail Gryzykhin <mig...@google.com> wrote: > @Ahmet Altay <al...@google.com> > Thank you for the comment. > > Point on search engines is really good. If that happens we can look into > configuring robots.txt to notify search engines to ignore whole domain. > The link is a redirect to static IP. So it is still confusing. > > Having domain name will allow for getting SSL associated with it and will > allow to keep same address even if IP changes (say we want to move to other > hoster). > I suppose short link will also allow us to change the host very similar to a domain name. That is a minor point anyway. > > Given two points above, I still consider that having explicit name will be > beneficial. If there's some other way to get SSL cert and benefit of static > name I'm eager to utilize it. > > On Mon, May 20, 2019 at 10:43 AM Ahmet Altay <al...@google.com> wrote: > >> Hi Mikhail, >> >> Thank you for your work on this. I have some comments: >> >> - There is already a short link ( >> https://s.apache.org/beam-community-metrics). Would a link from >> contributing to beam page (if there is not one already) sufficient> People >> can bookmark the short link if they need to quickly access. >> - Metrics is a developer facing tool. If it has its own subdomain and >> start showing up in web search results, it will be a confusing landing page >> for people simply searching for "beam metrics". I believe there is some >> value in having a single domain and linking to various things from there. >> This would be similar to how we link to jira, wiki, mailing list archives. >> >> Ahmet >> >> On Fri, May 17, 2019 at 9:26 PM Mikhail Gryzykhin < >> gryzykhin.mikh...@gmail.com> wrote: >> >>> @Aizamat >>> Code is not generalized and is project specific in some places. But it >>> is small and pretty straightforward so can be ported easily. Whole thing >>> can be started locally with a single docker command, so it's easy to try it >>> out. >>> >>> On Fri, May 17, 2019, 19:33 Aizhamal Nurmamat kyzy <aizha...@google.com> >>> wrote: >>> >>>> Hi Mikhail, >>>> >>>> I think this dashboard is amazing, and would love to have an easy >>>> access to it. So here is my non binding +1. >>>> >>>> On the side note, how easy is to recreate it for other Apache projects? >>>> ;) >>>> >>>> Thanks, >>>> Aizhamal >>>> >>>> *From: *Mikhail Gryzykhin <mig...@google.com> >>>> *Date: *Fri, May 17, 2019 at 6:49 PM >>>> *To: *dev >>>> >>>> Hello everyone, >>>>> >>>>> Some time ago we started community metrics dashboard. >>>>> <https://s.apache.org/beam-community-metrics> However we never had >>>>> added a permanent URL for it. This is really inconvenient to use, since >>>>> only available way to access dashboard is by IP-address. >>>>> >>>>> In this tread I'd like to: >>>>> 1. Vote to assign metrics.beam.apache.org to metrics dashboard ( >>>>> http://104.154.241.245). >>>>> 2. Gather information on how to do it. I can assume only following >>>>> steps so far: a) vote b) once vote is complete, contact Apache INFRA to >>>>> help with this. >>>>> >>>>> Regards, >>>>> Mikhail. >>>>> >>>>>
