[03:01] <EmeraldKnight15> hello
=== atamira is now known as Liz
=== Liz is now known as atamira
[13:01] <Tiger_> Hello
[13:02] <kaine119> hi!
[13:07] <Arko_> Hi
[17:23] <Termi1878> hi guys!
[17:24] <Termi1878> I've got a problem with how-to tutorial. I've done everything like in instructions and after making a website with docker I get white screen in Mozilla with Ubuntu tutorial on tab title.
[17:25] <degville> Hello Termi1878!
[17:25] <degville> what's the URL in Firefox?
[17:25] <Termi1878> localhost
[17:26] <Termi1878> But that's not only white page, but it looks like a background of the site without everything
[17:26] <degville> http://localhost:8016/?
[17:26] <Termi1878> yup. I write that and after "enter" this coming to just localhost
[17:26] <Termi1878> sry, it is like you wrote
[17:27] <Termi1878> And I dunno what to do. I think that I built site properly
[17:28] <degville> It sounds very close. Could you try pressing ctrl+c in the window you've typed './run' into?
[17:29] <degville> that will stop the server
[17:29] <degville> and then try ./run again.
[17:29] <degville> and then maybe paste the output in the terminal as you see it into here?
[17:30] <Termi1878> Just copy  and paste that?
[17:30] <degville> yeah, it should only be a few lines. This is what I get:
[17:30] <degville> yarn run v1.2.1
[17:30] <degville> $ echo 'To build site, please use build-all'
[17:31] <degville> To build site, please use build-all
[17:31] <degville> Done in 0.12s.
[17:31] <degville> yarn run v1.2.1
[17:31] <degville> $ npm-run-all 'serve-examples {@}' --
[17:31] <degville> 2017/12/13 17:30:38 Serving on http://localhost:8016
[17:31] <degville> y
[17:31] <degville> (not the y at the end :) )
[17:31] <Termi1878> I've got everything just like you
[17:32] <Termi1878> yarn run v1.2.1 $ echo 'To build site, please use build-all' To build site, please use build-all Done in 0.13s.   yarn run v1.2.1 $ npm-run-all 'serve-examples {@}' -- 2017/12/13 17:29:35 Serving on http://localhost:8016
[17:33] <degville> how about if you run './run serve examples' instead?
[17:34] <Termi1878> same, "white" background, tab with "ubuntu tutorials" and sign.
[17:35] <degville> could you try entering 'http://localhost:8016/tutorial/example-tutorial#0' as a URL?
[17:35] <degville> (that would take you directly to the example tutorial).
[17:35] <degville> my best guess is that something when wrong when building.
[17:35] <Termi1878> same
[17:35] <Termi1878> nothing changed
[17:36] <degville> nothing to do with what you did, but I've sometimes had problems like this when the build misses something out for some strange (network?) reason.
[17:36] <Termi1878> ;((
[17:37] <Termi1878> And what I have to do now?
[17:37] <degville> Termi1878: you obviously totally understand the process though, so there's going to be no worries in passing you for the task.
[17:38] <degville> If you've got the time, I'd make a new clone of the repository, and run the run script again to rebuild everything.
[17:38] <Termi1878> Well, thank you. But you know, I will have to know what I did wrong.
[17:38] <Termi1878> Yes!
[17:39] <degville> Is this on Ubuntu? Xenial?
[17:39] <Termi1878> Ubuntu
[17:39] <Termi1878> 16.04 lts
[17:39] <degville> cool. It should definitely work as described then.
[17:40] <degville> (meaning that it's likely a problem out of your control)
[17:40] <Termi1878> Yup. I tried to do something with that, but I've got no time and this is my second try.
[17:42] <Termi1878> So, Do I have to do something with task, submit for review or something? I will still try to understand that
[17:43] <degville> Yes, exactly. If you submit it for review I'll pass it.
[17:43] <degville> maybe when you get some time give it another go and let us know what happens, because it obviously shouldn't be happening.
[17:44] <Termi1878> Done!
[17:44] <Termi1878> What do you mean with "another go"?
[17:45] <degville> I mean clone and run again, effectively a fresh install.
[17:46] <Termi1878> Okay!
[17:47] <degville> (I've only just seen all the history of you trying to get this to run previously!)
[17:48] <Termi1878> And you see any problem?
[17:48] <Termi1878> problems*?
[17:50] <degville> Not obviously. It should work. I just mean you've given this a lot of effort!
[17:51] <Termi1878> Yes! I really tried to do this, because it is for beginners and felt so stupid about that
[17:52] <degville> Termi1878: You shouldn't; you've done nothing wrong. If there's a failure, it will be with our system as it should clearly complain.
[17:53] <Termi1878> Yeah, but I didn't knew about that before I talked with You
[17:54] <degville> well, it's really difficult to troubleshoot these kind of problems remotely. I'm frustrated we can't find the issue, as it should  definitely 'just work', and yet you've tried both a VM and native install.
[17:56] <Termi1878> Yup ;( But I'm doing now a fresh install, so maybe will work this time.
[17:56] <degville> so have the same problem on new installs suggests something outside of those installs, maybe your local networking environment, for example.
[17:58] <Termi1878> Well, after fresh install - exactly like before problem
[18:00] <degville> A long shot maybe to try shift F5 in Firefox (if you've not already), as this will override the cache, incase the partially loaded page from there is taking priority.
[18:00] <degville> (to reload the page I mean)
[18:02] <Termi1878> Same problem