Local Development Setup
Local Development Setup
Clone the Repository
Install Dependencies
Environment Configuration
Run Sylvi
API Server:
Autonomous Agent Scheduler:
Configuration Details
Environment Variables
Sylvi relies heavily on environment variables to manage both internal settings and external integrations. Some critical variables include:
General
ENV
: Sets the runtime environment (e.g., local, production).DEBUG
: Enables debug mode if set to “true”.
Database
DB_HOST
,DB_PORT
,DB_USERNAME
,DB_PASSWORD
,DB_NAME
: Standard Postgres parameters.DB_AUTO_MIGRATE
: Determines if migrations run automatically.
API Keys
OPENAI_API_KEY
: For text generation and summarization tasks (if using language-based generation).CDP_API_KEY_NAME
,CDP_API_KEY_PRIVATE_KEY
: For Coinbase Developer Platform (CDP) blockchain integration.
Messaging/Alerts
TG_TOKEN_GOD_BOT
: Telegram bot token.SLACK_ALERT_TOKEN
,SLACK_ALERT_CHANNEL
: Slack keys for sending notifications.
Security
Variables for AWS Secrets Manager usage (
AWS_SECRET_NAME
, etc.) if needed.
Editing .env
.env
Open
.env
in a text editor.Populate each variable with the appropriate value.
Confirm that confidential keys are either stored here only for local dev or retrieved securely with AWS Secrets Manager in production contexts.
AWS Secrets Manager
Optionally, you can store secrets like database credentials and API keys in AWS Secrets Manager rather than a local .env
file. This can be configured by:
Setting up AWS credentials in your environment (
AWS_ACCESS_KEY_ID
,AWS_SECRET_ACCESS_KEY
).Specifying the secret names in
.env
, for example:Sylvi’s config will then fetch these from AWS at startup, caching them for performance.
Last updated