Am 06/03/2015 um 21:37 schrieb Matthias Dittrich: > On 06.03.2015 20:19, Wolfgang Mauerer wrote: >> Am 06/03/2015 um 15:39 schrieb florian.peguet@xxxxxx: >>> Dear all, >>> >>> I managed to solve my previous problem ( the command xsltproc was not >>> installed and seems to be mandatory for cppstats, maybe it could be a >>> good thing to add apt-get install xsltproc, in the README process) >> yes, this requirement is indeed documented on cppstat's homepage: >> http://www.infosun.fim.uni-passau.de/cl/staff/liebig/cppstats/ >> Good catch - could you please submit a patch for the README file? > I would highly suggest to enable travis for codeface: > https://travis-ci.org/ (login with your github account) > This should be done as soon as possible (before the build/testsuite is > broken again)! thanks for the suggestion -- we're working on that, it's mainly a matter of administrative privileges. Codeface is still hosted on the Siemens account, but since my affiliation (as far as codeface is concerned) changed, I cannot turn Mitchell into an admin without further ado. I'm thinking about a solution. Nonetheless, thanks for your CI work -- this is highly helpful and most appreciated. Best regards, Wolfgang > It should be as simple as changing > > to > > (of course the entry will be called siemens/codeface instead of > matthid/codeface :) ) > If there are any problems, please let me know! > > > After this we could just reference > https://github.com/siemens/codeface/blob/master/.travis.yml in the readme. > This way we could prevent outdated documentation about dependencies in > the future (because the build will break when it's incorrect). > I think the .travis.yml is a sufficiency easy to read step by step guide > (after adding some comments) to get running on a clean Ubuntu machine > (considering the users of codeface). It will be validated/used on every > commit/pull request/branch, so it guaranteed to work. > If you think extra documentation makes sense we could just make sure > that a change in .travis.yml is always combined with a change in the > documentation (manual process or some tricky git hook). > It should be straightforward to (automatically) generate up-to-date > documentation or even a install script out of .travis.yml file if ever > needed. > > -- Matthias >>> "Codeface test" now give the same result wether I execute it from the >>> regensburg server or the docker images. >>> The enhancements of analyses for project may be pass on the docker >>> instance since I use git clone. >>> >>> I am now thinking about using shiny server so that users can use >>> codeface easily from their web browser, but I got errors. >>> >>> When I run shiny server (with the command shiny-server >>> shiny-server.config) from my computer (same as the regensburg-server) I >>> got this at localhost with firefox : >>> ERROR: impossible to find the function "breadcrumbOutput". >>> Have I missed something? >> the function should be defined in codeface/R/shiny/nav/breadcrumb.shiny.r, >> maybe there a file inclusion missing somewhere. Can you look at the log >> files (there are several of them, look for *.log in the installation >> directory) and post the complete error message? >>> for docker, it is harder to run shiny-server, because localhost is >>> running on the virtual container and not on the real computer/server. >>> The solution is to create a bridge between ports. >>> I tried to make a bridge for port 8081 where the shiny server may run >>> but i got Page not found on my web browser. This means something >>> happened otherwise I would get "connection failed" >> the approach is sound; naturally, docker cannot use the host >> ports directly because otherwise you would not be able to run, >> for instance, two containers with different versions of a server >> software on one single machine. >>> for now I don't understand why I don't get the previous error with >>> docker (breadcrumbOutput not found) . >>> Is there more than one port to bind? >> did you properly expose the port in the dockerfile? Can you sniff >> the traffic with, say, wireshark to see what it going on on the wire? >> >> Best regards, Wolfgang Mauerer >>> I use docker like that: >>> docker run -p port_on_docker:port_on_the_real_computer >>> folder_name/my_image_name:tag >>> >>> Florian. >>> >