Closed Morriz closed 1 day ago
the is my config:
log:
# debug, info, warn, error, panic, dpanic, or fatal. Default = info
level: info
# How should logs be formatted? Setting to "console" will print human readable logs
# whie "json" will print structured JSON logs. Default is "json".
format: console
http:
# Host to bind to. Default is 0.0.0.0
host: 0.0.0.0
# Port to bind to. Default is 8000
port: 8000
max_request_size: 5242880
postgres:
user: postgres
password: postgres
host: zep-db
port: 5432
schema_name: public
read_timeout: 30
write_timeout: 30
max_open_connections: 10
# Carbon is a package used for dealing with time - github.com/golang-module/carbon
# It is primarily used for generating humand readable relative time strings like "2 hours ago".
# See the list of supported languages here https://github.com/golang-module/carbon?tab=readme-ov-file#i18n
carbon:
locale: en
graphiti:
# Base url to the graphiti service
service_url: http://zep-graphiti:8003
# In order to authenicate API requests to the Zep service, a secret must be provided.
# This secret should be kept secret between the Zep service and the client. It can be any string value.
# When making requests to the Zep service, include the secret in the Authorization header.
api_secret: xx
# In order to better understand how Zep is used, we can collect telemetry data.
# This is optional and can be disabled by setting disabled to true.
# We do not collect any PII or any of your data. We only collect anonymized data
# about how Zep is used.
telemetry:
disabled: false
# Please provide an identifying name for your organization so can get a better understanding
# about who is using Zep. This is optional.
organization_name:
Hi @Morriz - Zep CE does not ship with a web UI. You can see a feature comparison of Community Edition and Zep Cloud here: https://help.getzep.com/ce/ce-vs-cloud
Shame. Then can you provide at least documentation on how to test our api endpoint?
Plus, with log level debug
no extra info is given. I also get a 404 when targeting the api like this:
zep-app-1 | 2024-10-03T21:35:51.706Z INFO HTTP Request Served {"proto": "HTTP/1.1", "method": "GET", "path": "/api/v1/collection", "request_id": "", "duration": "84.353µs", "status": 404, "response_size": 19}
Zep no longer supports Document Collections: https://help.getzep.com/document-collections
I noticed we should have mentioned this in the README and fixed this.
Many vector databases are available today, and this wasn't a differentiated feature for Zep. We suggest you look at the list of vector database vendors here, many of which are available as open-source products: https://python.langchain.com/docs/integrations/vectorstores/
Well, that is what your current integration in n8n produced. Are you aware of such regression vectors at all? This all feels very alpha to me, as the lot of you do not seem to care about the world out there. Where can we read about your changes and the potential impact it has across the board?
The n8n integration was developed by the n8n team, with us contributing later to it. We don't own the integration.
A full list of changes may be found on the project README: https://github.com/getzep/zep?tab=readme-ov-file#how-does-zep-community-edition-differ-from-zep-open-source-v0x
Describe the bug I get a 404 as seen in the logs:
To Reproduce follow the instructions of running with docker compose
Expected behavior to see a UI
Logs
Environment (please complete the following information):
latest
imagedocker compose
Additional context Add any other context about the problem here.