@rubailly this may be of interest to you
Any lessons we are borrowing from here https://wiki.openmrs.org/pages/viewpage.action?pageId=70877277 or this totally different
@darius is this the link for today’s kick off meeting? https://hangouts.google.com/hangouts/_/openmrs.org/ocl-for-openmrs?authuser=0
@ningosi in fact the OCL Subscription module is still very relevant.
The purpose of this project is to create a new UI for OCL so that people can more effectively create their own dictionaries there.
Once they’ve done this, they’ll use the existing module you linked to, to keep in sync.
It was the link. Apparently I needed to log in using my OpenMRS google account to be able to approve people to join. Next time I’ll try to figure out how to not require approval at all. (I just used the default hangout created by google calendars when I created the event, but apparently that doesn’t behave as desired.)
Sharing a comment from the infrastructure team:
- we should build a docker image (e.g. nginx + our js application)
- also we should provide a simple docker-compose setup that explains the deployment (basically the team should reach out to the infrastructure team for the details of this)
(They should be able to deploy this on the same servers as currently host openconceptlab.)
Hey everyone. My team and I are excited to start a new sprint for a new product (Open Concept Lab for OpenMRS). implementing project setup, authentication, and user dashboard features. The sprint will be two weeks long and with support from the community, we hope to finish working on the feature by the time the sprint ends.
Start Date: 02-05-2018
End Date: 16-05-2018
Github Repository: https://github.com/openmrs/openmrs-ocl-client
Team Lead: Daniel Kayiwa (@dkayiwa )
I’m excited to see this work happening, and happy to participate in the Product Owner role. Feel free to ask me for clarifications or to do QA/UAT of features at any point.
I have merged the “Sprint 1” topic into this “Developing…” topic. Let’s keep most of the conversations (including announcing the sprint kickoff and demo) consolidated into this one talk thread, so that it’s easier for other interested stakeholders to watch just one place (as they may be less likely to notice new Talk topics).
Hey dev team, could you give an update on how things are proceeding in terms of getting this deployed to a qa environment? (Just to be clear I’m expecting you all to push forward on that by asking for support on it as necessary.)
- I renamed the JIRA project and changed its key (from OCL to OCLOMRS). The reason is that if someone types a project key in a search box, JIRA automatically tries to be smart with this, but since “ocl” may be used in other OpenMRS projects, I don’t want this to happen.
- I don’t really like the repo name “openmrs-ocl-client”. From the consumer’s perspective this is an application or a web UI, not a “client”, right? I would call it something like “ocl-for-openmrs” or “ocl-for-openmrs-ui” or something like that.
Makes sense. we will work with @dkayiwa to resolve the repository name issue.
We have finished setup and it has already been merged to master, the login ticket is now up. As the login is done we will now create a sub-ticket for deployment to the qa environment for the live deployment. given the nature of the setup process and authentication, we cannot move very fast as we would like to since most of the current tasks are highly dependent on each other.
hey @darius where should we host the openmrs-ocl app. Given that the project setup is ready, i think we can move to the next step of hosting it.
How about “openmrs-ocl-webui”?
See a comment of mine earlier in the thread: Developing the "OCL for OpenMRS" Application
You will need to set up a CI process to create a docker image and push it to dockerhub. (I don’t know if travis is sufficient, or we need ci.openmrs.org. Or actually maybe there’s an OCL CI server…)
Then you’ll need a simple docker-compose file that says how to deploy this on OpenMRS’s infrastructure. But the first step is to make a request on help.openmrs.org.
That makes alot of sense
Hello @darius , As i was working on the ticket for Login implementation, I got a blocker where one is unable to login through the API, from our understanding the expected passwords are in hashed format which is different from the plain data that we are sending to the API. Do you mind shedding some light on how the login implementation is done for the traditional OCL using the API endpoints and how we can implement the same on the OpenMRS-OCL. Thanks cc @dkayiwa
I haven’t looked at this code, but I assume that since the OCL REST API is built on Django, you’d need to use whatever the standard authentication approaches are for Django REST.
@paynejd can you comment on this?