-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rename default value of HAYHOOKS_ADDITIONAL_PYTHONPATH #28
Comments
Hi @alex-stoica do you mind opening a quick PR? I'll review and merge! |
@masci @alex-stoica is there anything special needed to import custom components? My
My pipelines run fine locally (using the same custom_components folder in my local environment) and pipelines without custom components are also correctly imported. I have a simple docker compose too: services:
hayhooks:
container_name: hayhooks
image: hayhooks:local
ports:
- 1416:1416
volumes:
- ./pipelines:/opt/pipelines
- ./custom_components:/opt/custom_components
- ./data:/data
healthcheck:
test: ["CMD-SHELL", "curl --silent --fail localhost:1416/status || exit 1"]
interval: 120s
timeout: 30s
retries: 3
env_file:
- .env
networks:
default:
name: local |
Ok, got it. I had to remove "custom_components" from my yaml. The type simply became |
@karbasia what I did to work is
In my docker file + maintained Anyway, I guess that removing |
Thanks for the info! I ended up revisiting my configuration and updating my custom_components mounts so that I can keep the custom_components in my imports and yaml. Your solution is much cleaner though, so I'll make the necessary adjustments. |
Currently, it is
opt/custom-components
. I recommend renaming it toopt/custom_components
for improved consistency with Python naming conventions. This change will facilitate more intuitive imports, such as:from custom_components.some_custom_component import MyCustomComponent
The text was updated successfully, but these errors were encountered: