dominikriemer commented on issue #1866: URL: https://github.com/apache/streampipes/issues/1866#issuecomment-1715131319
@lab596 thanks for clarifying! The setup should work out of the box - here is a short description what I do when developing a pipeline element: * Stop the `docker-compose` instance of the basic installation (you might also consider to clean this instance by executing `docker-compose down -v`. * To set up the development environment, go to `installer/cli`, configure a template (`./streampipes env --set pipeline-element`) and run `./streampipes up -d`. * You should then have a running StreamPipes instance including the UI with backend ports which are configured for local development. * When you open the IDE of your choice, create a new pipeline element and execute the `Init` method (e.g., try with the `extensions-all-jvm` module. Here is the place where you need to configure the environment variables as startup env variables (`SP_DEBUG` and `SP_CONSUL_HOST`). This will internally configure the extensions service for local development. * If you have any problems, you can check the logs of the extensions service (there should be a log message which shows where the system tries to connect to the core to register pipeline elements). Hope this helps! Please ask if anything is unclear. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@streampipes.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
