https://github.com/telefonicaid/perseo-core

Core/backend for the Perseo CEP
https://github.com/telefonicaid/perseo-core

Last synced: 2 months ago
JSON representation

Core/backend for the Perseo CEP

• Host: GitHub
• URL: https://github.com/telefonicaid/perseo-core
• Owner: telefonicaid
• License: gpl-2.0
• Created: 2015-01-20T10:07:16.000Z (almost 10 years ago)
• Default Branch: master
• Last Pushed: 2024-01-15T14:05:53.000Z (12 months ago)
• Last Synced: 2024-08-12T09:12:31.411Z (5 months ago)
• Language: Java
• Size: 611 KB
• Stars: 11
• Watchers: 19
• Forks: 15
• Open Issues: 15
• Metadata Files:
  • Readme: README.md
  • Changelog: CHANGES_NEXT_RELEASE
  • License: LICENSE

Awesome Lists containing this project

• awesome - Perseo - A Complex Event Processing (CEP) component enabling you to fire events which send HTTP requests, emails, tweets, SMS messages etc. as context data changes. (FIWARE Catalogue / Processing)

README

        
# Perseo-core (EPL server)

[![FIWARE Processing](https://nexus.lab.fiware.org/static/badges/chapters/processing.svg)](https://www.fiware.org/developers/catalogue/)

[![License: APGL](https://img.shields.io/github/license/telefonicaid/perseo-core.svg)](https://opensource.org/licenses/AGPL-3.0)

[![Support badge](https://img.shields.io/badge/tag-fiware--perseo-orange.svg?logo=stackoverflow)](http://stackoverflow.com/questions/tagged/fiware-perseo)

[![Quay badge](https://img.shields.io/badge/quay.io-fiware%2Fperseo--core-grey?logo=red%20hat&labelColor=EE0000)](https://quay.io/repository/fiware/perseo-core)

[![Docker badge](https://img.shields.io/badge/docker-telefonicaiot%2Fperseo--core-blue?logo=docker)](https://hub.docker.com/r/telefonicaiot/perseo-core)




[![CI](https://github.com/telefonicaid/perseo-fe/workflows/CI/badge.svg)](https://github.com/telefonicaid/perseo-fe/actions?query=workflow%3ACI)

![Status](https://nexus.lab.fiware.org/static/badges/statuses/perseo.svg)

This is the code repository for the EPL-server, named perseo-core.

## Index

* [Architecture](documentation/architecture.md)

* [Logs & Alarms](documentation/logs.md)

* O&M

    * [Deployment](documentation/deployment.md)

    * [Configuration](documentation/config.md)

    * [Administration](documentation/admin.md)

* [API](documentation/api.md)

* [License](#license)

|  [quay.io](https://quay.io/repository/fiware/perseo-core)| :whale: [Docker Hub](https://hub.docker.com/r/telefonicaiot/perseo-core)  | :dart: [Roadmap](https://github.com/telefonicaid/perseo-fe/blob/master/documentation/roadmap.md) |

|---| --- | --- |

## License

Perseo Core is licensed under General Public License (GPL) version 2.

Further information on the use of the GPL open source license

### Are there any legal issues with GPL 2.0? Is it safe for me to use?

There is absolutely no problem in using a product licensed under GPL 2.0. Issues with GPL

(or AGPL) licenses are mostly related with the fact that different people assign different

interpretations on the meaning of the term “derivate work” used in these licenses. Due to this,

some people believe that there is a risk in just _using_ software under GPL or AGPL licenses

(even without _modifying_ it).

For the avoidance of doubt, the owners of this software licensed under an GPL 2.0 license

wish to make a clarifying public statement as follows:

> Please note that software derived as a result of modifying the source code of this

> software in order to fix a bug or incorporate enhancements is considered a derivative

> work of the product. Software that merely uses or aggregates (i.e. links to) an otherwise

> unmodified version of existing software is not considered a derivative work, and therefore

> it does not need to be released as under the same license, or even released as open source.