Open nikokaoja opened 4 years ago
@matthewhorridge it seems that there are additional steps once the docker image is running which are provided here: https://github.com/protegeproject/webprotege/wiki/WebProt%C3%A9g%C3%A9-Deployment-via-Docker
I think it would be great to actually add the link to the above instructions in your README.MD under Running from Docker section. This could save newbies, like myself, a lot of time :).
@niva83 +1 That part I had to dig out from somewhere else, so having it in README or at least a link to it would be great.
@katsi indeed, I've spent about 3+ hours trying to figure out why docker does not work as it should be. As you said, I was digging through the Git repo and by chance found the above description which helped me to make the docker ver of webprotege to work. Some people are not as pesistent in trying to dig out information, so indeed, either fusing the info from the link to README or at least puttin a link for Additional steps to make docker to work would be of great help for anyone new to webprotege and docker.
Has anyone here deployed webprotege with kubernetes? I am currently trying to do that and I have trouble connecting the frontend with mongo
@katsi I haven't, still working with dockers.
go it working, so if anyone needs help with that, am happy to share!
@katsi I think it would be helpful, I hope someone from the repo maintainers will catch up with the information we are sharing here.
@katsi Can you share? I am hitting an issue where the web front-end cant find mongodb even though I can connect from the same container use mongoshell
I am happy to share. Wondering what format would make sense? Should we have an informal webinar on the topic?
Katariina
On Thu 25. Jun 2020 at 22.30, Matthew Manela notifications@github.com wrote:
@katsi https://github.com/katsi Can you share? I am hitting an issue where the web front-end cant find mongodb even though I can connect from the same container use mongoshell
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/protegeproject/webprotege/issues/692#issuecomment-649801490, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGTSXANEVM7KTZYXGGBM6DRYOXWLANCNFSM4ODXTZKQ .
@katsi webinar would be great. Maybe to record it and share over Youtube?
@mmanela how do you notice that the webprotege front-end cannot find the MongoDB? I am wondering, if afterall I am hitting the same problem. After configuring the admin account, I still get the notification that Webprotege is not configured properly AND the frontend misses some components that would otherwise be there if I would start it with docker-compose.
But what do work are my admin credentials.
I was actually able to run the jar command to create the admin account (which was able to connect to the mongodb). But when I went to the website it gave me the mongodb connection error mentioned above.
I was eventually able to resolve it by restarting the pods.
Two of my colleagues, one using Windows and the other Linux, reported a problem where the webprotege.mongodb.host=wpmongo
was not stored when the contaienrs were launched. One solution here was to set the env with running the jar command, so like this: env "webprotege.mongodb.host=wpmongo" java -jar /webprotege-cli.jar create-admin-account
@niva83 What software could I use for that? Zoom, Google Meet, ..? Any recommendations? Never held a webinar before!
@katsi I've been using all above. Probably Google Meet is the easiest to setup if you already have Google account.
@johardi I noticed that you have updated readme.md with a better description on how to get webprotege to run from docker image. What is unclear is where and how to setup two files, namely webprotege.properties and mail.properties via docker image?
This question was originally posted as an issue #682 .
As it is now, if the instructions are followed for running webprotege as a docker image, the problem is that we are unable to reset password or get email notification since mail.properties are not set.
@katsi Do you have any cycles to briefly go over how you got webprotege running in a kubernetes cluster? How did you get around the initial admin account creation?
I did not even attempt to automate the initial admin account creation, but that to me is not a problem, because it only needs to be done once.
I documented my steps here: https://matthewmanela.com/blog/deploying-webprotege-on-azure-kubernetes-service-aks/
Thanks for the write up! I am using our company's own CDP and Kubernetes system, so sharing it is not as helpful. Your example is overall the same that we did!
Thanks for the responses. Great writeup @mmanela and that helped greatly! Would love to contribute to allow automation for passing of the initial account creation from keyvault. Perhaps I can lend a hand there.
Hi there,
I followed the instructions of running webprotege from a docker image, which is basically to create
docker-compose.yml
and exectutedocker-compose up
in terminal.However, there are a few issues.
and
http://localhost:5000/
in browser, an error is displayedWebProtégé is not configured properly
http://localhost:5000/webprotege#application/settings
returns404
logsdir_IS_UNDEFINED
is presentBasically, are there any additional steps for configuring webprotege prior or once the docker image starts, such as how to create user accounts, etc?
For example, I am not sure when, how and where to run
java -jar webprotege-cli.jar create-admin-account
? When I use docker CLI to navigate through folders, I noticed thatwebprotege-cli.jar
is locate in/
folder. And if I try to runjava -jar webprotege-cli.jar create-admin-account
in/
, while the docker image is active, after providing email address, user name and password I get the following message: