npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

keycloak-admin-ui

v0.0.1

Published

This project is the next generation of the Keycloak Administration Console. It is written with React and [PatternFly 4][1].

Downloads

7

Readme

Keycloak Admin Console V2

This project is the next generation of the Keycloak Administration Console. It is written with React and PatternFly 4.

Development Instructions

For development on this project you will need a running Keycloak server listening on port 8180. You will also need yarn installed on your local machine.

  1. Start keycloak

    • Download and run with one command
      $> ./start.js
    • or download Keycloak server from keycloak downloads page unpack and run it like:
      $> cd <unpacked download folder>/bin
      $> standalone -Djboss.socket.binding.port-offset=100
  2. Go to the clients section of the existing Keycloak Admin Console and add the client

    • like this: realm settings
    • or click on the "Select file" button and import security-admin-console-v2.json
    • or run $> ./import.js
  3. Install dependencies and run:

    $> yarn
    $> yarn start

Build and run through Docker

git checkout [email protected]:keycloak/keycloak-admin-ui.git
cd keycloak-admin-ui
docker-compose build
docker-compose up

You can reach the new admin interface at http://localhost

If your Keycloak instance is not on localhost:8180, create a file .env with the following:

KEYCLOAK_ENDPOINT=https:\/\/remoteinstance.keycloak.com

Additionally there are some nice scripts to format and lint

$> yarn format
$> yarn check-types
$> yarn lint

To switch to a RH-SSO themed version of this console you can run:

$> npx grunt switch-rh-sso

To switch back just do a git checkout public

Keycloak UI Test Suite in Cypress

This repository contains the UI tests for Keycloak developed with Cypress framework

Run the test suite

Prerequisites

via Cypress Test Runner

By using npx:

note: npx is included with npm > v5.2 or can be installed separately.

npx cypress open

After a moment, the Cypress Test Runner will launch:

image

via terminal

By executing:

$(npm bin)/cypress run

...or...

./node_modules/.bin/cypress run

...or... (requires [email protected] or greater)

npx cypress run

To execute a specific test on a specific browser run:

cypress run --spec "cypress/integration/example-test.spec.js" --browser chrome

note: the complete list of parameters can be found in the official Cypress documentation.

Project Structure

/assets (added to .gitignore)
  /videos - if test fails, the video is stored here
  /screenshots - if test fails, the screenshot is stored here
/cypress
  /fixtures - external pieces of static data that can be used by your tests
  /integration - used for test files (supported filetypes are .js, .jsx, .coffee and .cjsx)
  /plugins
    - index.js - extends Cypress behaviour, custom plugins are imported before every single spec file run
  /support - reusable behaviour
    - commands.js - custom commands
    - index.js - runs before each test file

/cypress.json - Cypress configuration file
/jsconfig.json - Cypress code autocompletion is enabled here

note: More about the project structure in the official Cypress documentation.

License