/estimate 2h

/spend 3h

09:42 < anoe> then I have found that the first Tree root was hard coded 
09:42 < anoe> that first RootId should be return after login
09:43 < anoe> then I have added the Auth route
09:43 < anoe> http://localhost:8008/swagger-ui/#/Gargantext/post_api_v1_0_auth
09:44 < anoe> basically : user1 or user2
09:44 < anoe> and password are the reverse
09:44 < anoe> to start with
09:44 < anoe> if login is success then user gets back the token and the Root id of the Tree
09:44 < anoe> I wonder how to implement it :
09:45 < anoe> https://gitlab.iscpif.fr/gargantext/purescript-gargantext/blob/master/src/Gargantext/Config.purs#L34
09:45 < anoe> remove that default root id
09:46 < anoe> and adapt it: 
https://gitlab.iscpif.fr/gargantext/purescript-gargantext/blob/master/src/Gargantext/Components/Login.purs
09:46 < anoe> with a common state
09:46 < anoe> I can manage for the release since that is not the priority
09:46 < anoe> creating an issue for that
09:46 < anoe> will see if enough time to do it
09:46 < anoe> after that
09:47 < anoe> this morning I was configuring continous integration
09:47 < anoe> on gitlab
09:47 < anoe> to avoid lacking files when pushing etc
09:47 < anoe> WIP
09:47 < anoe> need help of sys admin
09:47 < anoe> now working on the demo for the release
09:47 < npouillard> About the root id, the simplest for the release would be to have a hard coded function from 
                    logins to root ids
09:48 < anoe> yes
09:49 < anoe> will try
09:49 < npouillard> or do you get it already from http://localhost:8008/swagger-ui/#/Gargantext/post_api_v1_0_auth ?
09:49 < anoe> you get it from this route
09:49 < anoe> the point is showing different views with different users
09:49 < npouillard> anyway even if the second step is simple, it makes no difference for the demo, I would recommend 
                    focusing on something else
09:50 < anoe> yes as said before, keep it for later