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

app-connector-client

v1.0.1

Published

request certificates to connect with kyma

Downloads

5

Readme

App Connector

App Connector provides an interface to add your service instance to Kyma's service catalog. After that , you can use remote environments to connect your service instances to Kyma resources.

Running

  • Prerequisite: You should have openssl installed and accessible in path
  • navigate to this folder.
  • npm install
  • npm start
  • After first start, this repo will generate a private key for you and save it in keys folder. Don't change the location of the keys folder.
  • Visit localhost:4444 to open the UI and enter your TokenURL to the input field.
  • Once you give your tokenURL, the system won't ask you again for your TokenURL. If you want to start the whole process again, delete the keys folder and run npm start again.

Command line

Use node cli.js to run command line utility.

  • To see help -> node cli.js -h
  • A test command looks something like this: node cli.js --input test/integration/basic-service-metadata.json --token https://connector-service.<CLUSTER_NAME>.cluster.kyma.cx/v1/remoteenvironments/hmc-default/info?token=rngXbjLra4EEjwXcwayTohiv83jkxmvrC4bA49RcRKnC8_70ighPopcWUCq5IEwp51aHXKBW5NLRadjOzJAWrQ==

Docs

You can access OpenAPI doc of this project either from localhost:4444/metadata or from swagger.yaml file.

Developing

If you have kubeconfig file of the kyma cluster, you can automatically acquire token without using the kyma console.

  • Run the command kubectl --kubeconfig=config-file -n=kyma-integration port-forward svc/connector-service-internal-api 8080:8080
  • While the above command is running, go inside the test directory and run node get_token.js. This will get a token for you and output it to console.

Testing

You can run npm test, to test the project. The kubectl command mentioned in developing section should be running because testing uses a new token everytime.

Building

  • To build the docker image of the project, run npm run build.

  • To run it, docker run -p 4444:4444 varkes/server.

  • You can connect to running container with docker exec -it <container_id> /bin/sh

Logs

  • Server logs will be in the file server.log
  • Test logs will be in the file test.log