Git Product home page Git Product logo

petasos's Introduction

Petasos

New, better frontend for Hermes message broker.

Branch conventions

  • dev - development build
  • main - release build

Run locally

Petasos calls Hermes Management API. You can install Hermes locally by following the docs or on the Kubernetes cluster with Helm chart.

Set up the environmental variables:

  • HERMES_MANAGEMENT_DEFAULT: URL to the Hermes Management API
  • HERMES_FRONTEND_DEFAULT: URL to the Hermes Frontend API

Then run:

npm ci
npm start

Application will be available at localhost:7890

Advanced settings

In the production mode, it is also possible to build the Hermes Management and Frontend modules URLs based on the current URL. In order to do so, the following environmental variables should be defined:

  • HERMES_DOMAIN_PATTERN: URL will be matched against this regular expression
  • HERMES_DOMAIN_MATCH_GROUP_ID: id of the capturing group which will be used to construct the URLs (prefix)
  • HERMES_MANAGEMENT_ENDING: used to build the Hermes Management URL {prefix}-{HERMES_MANAGEMENT_ENDING}
  • HERMES_FRONTEND_ENDING: used to build the Hermes Frontend URL {prefix}-{HERMES_FRONTEND_ENDING}

If any of the variables is not defined, or the regex match fails, URLs fall back to the HERMES_MANAGEMENT_DEFAULT and HERMES_FRONTEND_DEFAULT values.

petasos's People

Contributors

bohdanprog avatar dependabot[bot] avatar dswiecki avatar gadomsky avatar julianwielga avatar semantic-release-bot avatar spoonman avatar trombka avatar

Stargazers

 avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

petasos's Issues

The automated release is failing 🚨

🚨 The automated release from the dev branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this πŸ’ͺ.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the dev branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.


No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.


Good luck with your project ✨

Your semantic-release bot πŸ“¦πŸš€

The automated release is failing 🚨

🚨 The automated release from the dev branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this πŸ’ͺ.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the dev branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.


Invalid tarballDir option.

The tarballDir option option, if defined, must be a String.

Your configuration for the tarballDir option is false.


Good luck with your project ✨

Your semantic-release bot πŸ“¦πŸš€

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. πŸ“ŠπŸ“ˆπŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.