Setting up Graphryder API with new dataset

another one : avoid using a mac (!) for running a server. A docker container should to the job pretty well.

Thank you, and understood. This is a completely viable solution for now seeing that I’m running a linux machine a server anyway. This problem came up during my local development and testing, and I had not tried running it with OGDF on the production server.

@hugi I was wondering if this task is completed, and maybe we should pay you?

1 Like

It’s about 90% done. What happened was that the window of time I had to do this ran out while we were working with the Bordeaux guys to iron out the bugs which took until late November. Since December I have simply been to swamped to finish, which would mean doing two things:

  • Document the fixes needed to make the dashboard render all graphs correctly in production mode
  • Write the set-up documentation clearly and precisely

I would prefer to do this before getting paid, but I also know the project is running very late. If I want to be realistic, by estimate to deliver this to the level that I would actually feel happy about would take a few days. I can find that time before February 10th. Is that okay?

Yes, totally OK.

Instructions are almost done, and API is back online for the OpenVillage conversation. However I’m waiting for a last piece of documentation from @luca_mearelli. I have emailed him, and once I get a reply, this task will be finished for now. Once I get that last piece from Luca, OpenVillage dashboard and will also come back online.

1 Like

Hi @hugi I didn’t encounter the same behaviour you report, I’ll try to check the setup you did of graphryder as soon as possible, at the latest on saturday

P.S. awesome to see graphryder used on other data sets @alberto :slight_smile:

2 Likes

I figured it out with some advice from Luca, and it’s now working as expected. Will update the documentation.
Now finally, far after schedule, job is done @alberto.

OpenVillage Mena dataset dashboard now back online at http://157.230.106.58, and seems to be working as expected. I tried running a few different layouts, and it seems to work fine.

YAY!
Minor point: I am still missing the slider to display labels on nodes (in all graphs):

That is strange indeed. @luca_mearelli, do you have any idea?

looks like it’s not getting the styling (and perhaps the js) for the sliders, it is there but not styled correctly (try clicking where it would be supposed to be). Also the slider below (“Co-occurrence…”) is working but the look is not right

I can’t see any errors when I build the static site though, which I do by running ‘npm run dist’. Do you build it differently?

When I deployed to the server I used:

npm run build

to build the static app files and then transferred them to the server and served them via the webserver (using the ansible playbook that is in the project)

@hugi When you run it locally does it work correctly? Are you working on a branch or on a clone of the graphryder repo? (if you give me access to it I can try on the same codebase you are working on)

Yes.

I’m working on the graphryder repo.

I’ve run build and am serving the dist directory with nginx. I have never used ansible. If possible, could you post a few lines on how you set it up?

Have you had time to have a look at this @luca_mearelli?

Hi hugi, I hadn’t have time to look into this yet, I may today/tomorrow and I’ll write up documentation on how I was doing the depoloyment (but Ansible is really just a way to automate the copying of the dist directory to the remote server)

1 Like

Hi, I have tried to understand what is wrong with the site anche why it doesnt’ show the sliders correctly but I actually couldn’t find anything wrong …

About the deploy procedure: what the ansible playbook does is simply this:

  1. it uploads the content of the dist directory to a directory on the server
  2. it generates a config.js file on the server with the right api URL
  3. it links the directory on the server as the document root of the nginx running on the server

It assumes that the dist directory contains the built application which I do with

npm run build

So nothing different from what you do.

I’ve also tried connecting to the same API server you do and I tried also running the project locally with nginx (via docker) using this command:

docker run --name graphryder-nginx -v /Code/graph-ryder-dashboard/dist:/usr/share/nginx/html:ro --rm -p 9998:80 -d nginx

then opening http://localhost:9998 shows the dashboard and the slider is working.

The only substantial difference is that the site is hosted on a non-https resource… can you have it configured with a domain name and an SSL cert?
I wanted to test deploying the code somewhere else but all the options I have available are https-only (netlify, zeit) and the app served over https won’t be able to access the API at 157.230.106.58:5000

Ok, let’s try that. It seems really strange for that to affect the CSS though.

But to do this I need @matthias, who handles the domain and certs of the edgeryders.eu domain.
We need to set up the API now running at http://157.230.106.58:5000 to get an https certificate like the API at https://graphryder.edgeryders.eu/api/. How do we proceed @matthias?

it is strange indeed, but it’s not an issue with CSS, rather it’s an issue with the slider not getting properly initialized (but no js errors are shown …)