-
Notifications
You must be signed in to change notification settings - Fork 9
-
Notifications
You must be signed in to change notification settings - Fork 9
Authentication problem on web-admin #31
Comments
After launching the docker images, one has to wait for some time before trying to log in the admin webapp, the time for the corresponding docker image to finish its initialisation. This time needs to be estimated and documented. |
Or consider others options :
|
@davidediruscio Would you have any recommendation regarding Martin's proposal? Should we simply update the doc (stating an unknown delay), display a message or make the container wait? |
I would suggest the following:
- showing a message informing that the system is not ready yet ( @boudeffa
Amin <amin.boudeffa@softeam.fr> what do you think?
- reducing the dumps only to a couple of projects (e.g., json-simple and
someone more) this would give the possibility to have the platform ready
in a few minutes. @boris Baldassari <boris.baldassari@castalia.solutions> what
do you think?
Il giorno gio 7 mar 2019 alle ore 10:50 Boris Baldassari <
notifications@github.com> ha scritto:
… @davidediruscio <https://github.com/davidediruscio> Would you have any
suggestion regarding Martin's proposal? Should we simply update the doc
(stating an unknown delay), display a message or make the container wait?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#31 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AB7wEBjqAEcKsvkiKc9mWW_qySF-bQsCks5vUOD7gaJpZM4ZfjVf>
.
--
-------------------------------------------------------------------------------------------------------------
Davide Di Ruscio, PhD in Computer Science
Department of Information Engineering Computer Science and Mathematics
University of L'Aquila
Via Vetoio, Coppito I-67010 L'Aquila (Italy)
Email: davide.diruscio@univaq.it
WWW: http://www.di.univaq.it/diruscio
Skype: davidediruscio
Twitter: DDiRuscio
-------------------------------------------------------------------------------------------------------------
|
Hiho Davide,
That sounds fair and good to me! :-)
Thank you!
…--
boris
On 07/03/2019 18:42, Davide Di Ruscio wrote:
I would suggest the following:
- showing a message informing that the system is not ready yet (
@boudeffa Amin ***@***.***> what do you think?
- reducing the dumps only to a couple of projects (e.g., json-simple and
someone more) this would give the possibility to have the platform
ready in a few minutes. @boris Baldassari
***@***.***> what do you think?
Il giorno gio 7 mar 2019 alle ore 10:50 Boris Baldassari
***@***.*** ***@***.***>> ha scritto:
@davidediruscio <https://github.com/davidediruscio> Would you have
any suggestion regarding Martin's proposal? Should we simply update
the doc (stating an unknown delay), display a message or make the
container wait?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#31 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AB7wEBjqAEcKsvkiKc9mWW_qySF-bQsCks5vUOD7gaJpZM4ZfjVf>.
--
-------------------------------------------------------------------------------------------------------------
Davide Di Ruscio, PhD in Computer Science
Department of Information Engineering Computer Science and Mathematics
University of L'Aquila
Via Vetoio, Coppito I-67010 L'Aquila (Italy)
Email: ***@***.*** ***@***.***>
WWW: http://www.di.univaq.it/diruscio
Skype: davidediruscio
Twitter: DDiRuscio
-------------------------------------------------------------------------------------------------------------
--
Boris Baldassari
Castalia Solutions -- Elegant Software Engineering
Web: http://castalia.solutions
Tel: +33 6 48 03 82 89
|
@davidediruscio , I think so. In this context, we can perform this checking in the admin-ui level or we can also work around the problem using a waiting-script for the oss-db when it will be really ready in the docker-compose level. |
hi @ambpro : is there any news about it ? |
Is fixed, thanks @ambpro |
On ci4 I re-pulled and re-built everything, pruned everything I could, and I still have the failed auth issue in the web admin part. As indicated in the readme I've updated the web-admin Dockerfile:
I checked that port 8086 is the one provided by the
api-server
service.Please not it is not a up/down/up issue since this is the first run of these containers. Also, the fix provided for that error by @MarcioMateus worked for me before the recent changes.
The text was updated successfully, but these errors were encountered: