Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update to keycloak 18.x.x quarkus version #97

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

XcrigX
Copy link

@XcrigX XcrigX commented Oct 7, 2022

Signed-off-by: Craig McClendon [email protected]

@jigneshmpatel
Copy link

steps to copy to Mac
gh auth login
? What account do you want to log into? GitHub.com
? What is your preferred protocol for Git operations? SSH
? Upload your SSH public key to your GitHub account?
? Title for your SSH key: SHA256:signature
? How would you like to authenticate GitHub CLI? Login with a web browser

after you connect to github do following
git clone [email protected]:Alvearie/keycloak-extensions-for-fhir.git

cd keycloak-extensions-for-fhir --<goto download dir and then download the
gh pr checkout 97

remote: Enumerating objects: 75, done.remote: Counting objects: 100% (75/75), done.remote: Compressing objects: 100% (16/16), done.remote: Total 41 (delta 13), reused 41 (delta 13), pack-reused 0Unpacking objects: 100% (41/41), 9.15 KiB | 468.00 KiB/s, done.From github.com:Alvearie/keycloak-extensions-for-fhir * [new ref]         refs/pull/97/head -> feature/quarkus-updateSwitched to branch 'feature/quarkus-update'
The above branch have hapi fhir based update
run followingdocker build . -f keycloak-config/Dockerfile -t alvearie/keycloak-config
 The smart keycloak command would be:
docker run -p 8080:8080 -p 8443:8443 -e KEYCLOAK_ADMIN=admin -e KEYCLOAK_ADMIN_PASSWORD=admin alvearie/smart-keycloak

@XcrigX XcrigX force-pushed the feature/quarkus-update branch from bf5424c to 9257599 Compare December 7, 2022 17:45
@XcrigX XcrigX mentioned this pull request Aug 25, 2023
@anton-kurilov
Copy link

I came to this issue from #126, are there plans to review and merge this in? I am not an active contributor (yet), so not sure if I should be approving this, but I can if needed...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants