BUILD FAILURE in osmt-api (asking for assistance in setting up OSMT in local) #466
Answered
by
JohnKallies
yamyamxx
asked this question in
Asking for Help
-
|
Hello! Really appreciate if someone can assist me with this issue in setting up OSMT. This is my first time setting up OSMT and I follow the docx here to set up OSMT: https://github.com/wgu-opensource/osmt/blob/develop/README.md#running-the-development-configuration , but as it started to build the app, I encountered an issue in the 
Here's the logs when it encountered the first error Here's the versions of the tech installed in my system: I am building and running osmt in a vagrant machine, using Ubuntu focal as my system's OS. Your comments/suggestions are greatly appreciated! Thank you in advance! |
Beta Was this translation helpful? Give feedback.
Answered by
JohnKallies
Feb 7, 2024
Replies: 4 comments 4 replies
-
|
Hello. Please paste in the output of Thank you. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Hi @JohnKallies , thank you for responding. Here's the output for And for the 
Additional error logs |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
[UPDATED] Hi @JohnKallies , I was able to successfully built osmt, omt-ui, and osmt-api by skipping the tests --> |
Beta Was this translation helpful? Give feedback.
4 replies
-
|
Additional info: I tried accessing the app via |
Beta Was this translation helpful? Give feedback.
-
|
OSMT has a design quirk from the original authors, in that the UI is built in the resources directory of the API module. So when you start the Spring app, the UI files are baked into that jar and available via 8080. If the API is running, the UI is already in that jar. Everything works on the same host / port / server via Spring. If you want to run the UI independently, this makes it a little messy, beause the OAuth2 redirect needs to come back to the Angular/webpack server on 4200. To support this local UI development, uncomment the line with OSMT_FRONT_END_PORT in your api/osmt-dev-stack.env file. Let's be honest about that baked-in UI files design... it's messy when standing up a UI in a traditional cloud deployment. The WGU Open Source team was not able to prioritize the refactor needed to make the UI into its own independent module/package; to properly decouple the ui and api Maven modules with good module hygiene / boundaries. The UI module would build its own dist artifact, and make its own Maven artifact and npm package. If the api module wants it, it declares it as a dependency and unpacks it / puts it where ever it wants. But then the UI is free to be deployed via S3 / Cloudfront / whatever, and it's crystal clear how to untangle these things. I hope some of that helps. |
Beta Was this translation helpful? Give feedback.
Answer selected by
JohnKallies
-
|
[UPDATED] Hi @JohnKallies , thank you for that detailed explanation, got it. I was able to access the user interface now using port 8080 and can login, but I can't login successfully, it shows this error below. I am using a vagrant machine to run ubuntu since my PC's OS is windows, that is why accessing localhost outside the vagrant machine is not working (thus I need to use the machine's IP), where can I set the IP or domain so that I can change localhost to my vagrant machine's IP address? I tried adding the variables
|
Beta Was this translation helpful? Give feedback.
-
|
Nevermind, I updated the front-end URL in the application-dev.properties and it worked, I can now accessed the app after authentication. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your help @JohnKallies , I have other issues encountered but I guess it's better be discussed in a separate thread. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
OSMT has a design quirk from the original authors, in that the UI is built in the resources directory of the API module. So when you start the Spring app, the UI files are baked into that jar and available via 8080. If the API is running, the UI is already in that jar. Everything works on the same host / port / server via Spring.
If you want to run the UI independently, this makes it a little messy, beause the OAuth2 redirect needs to come back to the Angular/webpack server on 4200.
To support this local UI development, uncomment the line with OSMT_FRONT_END_PORT in your api/osmt-dev-stack.env file.
Let's be honest about that baked-in UI files design... it's messy when standing up a UI in…