-
Notifications
You must be signed in to change notification settings - Fork 1
Python rewrite with charts and slash commands #16
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
Changes from all commits
e28cabe
5fdc973
c5062f5
d5ee15e
4a1c65f
222969e
d72d930
8e20d88
bd70916
f153e5f
f11dabe
35b0ac8
dd2f26f
20c6435
8ddcfc3
5ec551f
6aa5507
4200a25
689adc7
3aea809
8adab81
e82a6c0
822ea4b
d73168c
31b3117
6c5f5b7
36d7e26
209f24e
e4d6b9f
32633e7
1d8ca10
6e4cc65
9cc0fb2
310dafa
7c21b18
bd39755
5590458
710da7c
f032ebc
44498e4
2a6e92f
26ebfb7
3f769a2
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
This file was deleted.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,41 +1,17 @@ | ||
| # Price update interval (shared by all services) | ||
| UPDATE_INTERVAL_SECONDS=30 | ||
| # Price update interval in seconds | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Hardcoded database password committed to repositoryHigh Severity The .env.example file contains a hardcoded database password ( Suggested fix: Remove the hardcoded password from .env.example and use a placeholder value like |
||
| UPDATE_INTERVAL_SECONDS=12 | ||
|
|
||
| # How often to clean up old price data (in hours) | ||
| CLEANUP_INTERVAL_HOURS=48 | ||
|
|
||
| # Log level: error, warn, info, debug, trace | ||
| RUST_LOG=info | ||
|
|
||
| # Discord Bot Tokens - get these from https://discord.com/developers/applications | ||
| # Create a bot, go to Bot, and click "Reset Token" to get a new token | ||
| # Then invite the bot to your server with appropriate permissions | ||
| # Discord Bot Tokens | ||
| # Format: DISCORD_TOKEN_<NAME>=token | ||
| DISCORD_TOKEN_BTC=your_btc_bot_token_here | ||
| DISCORD_TOKEN_ETH=your_eth_bot_token_here | ||
| DISCORD_TOKEN_SOL=your_sol_bot_token_here | ||
| DISCORD_TOKEN_DOGE=your_doge_bot_token_here | ||
| DISCORD_TOKEN_AVAX=your_avax_bot_token_here | ||
| DISCORD_TOKEN_BNB=your_bnb_bot_token_here | ||
| DISCORD_TOKEN_SUI=your_sui_bot_token_here | ||
| DISCORD_TOKEN_SEI=your_sei_bot_token_here | ||
| DISCORD_TOKEN_JLP=your_jlp_bot_token_here | ||
| DISCORD_TOKEN_PUMP=your_pump_bot_token_here | ||
| DISCORD_TOKEN_XPL=your_xpl_bot_token_here | ||
| DISCORD_TOKEN_MSTR=your_mstr_bot_token_here | ||
| DISCORD_TOKEN_OIL=your_oil_bot_token_here | ||
| DISCORD_TOKEN_VOO=your_voo_bot_token_here | ||
| DISCORD_TOKEN_DXY=your_dxy_bot_token_here | ||
| DISCORD_TOKEN_HOOD=your_hood_bot_token_here | ||
| DISCORD_TOKEN_SBET=your_sbet_bot_token_here | ||
| DISCORD_TOKEN_GOLD=your_gold_bot_token_here | ||
| DISCORD_TOKEN_SILVER=your_silver_bot_token_here | ||
| DISCORD_TOKEN_FARTCOIN=your_fartcoin_bot_token_here | ||
| DISCORD_TOKEN_2Z=your_2z_bot_token_here | ||
| DISCORD_TOKEN_ASTER=your_aster_bot_token_here | ||
| DISCORD_TOKEN_EURO=your_euro_bot_token_here | ||
| DISCORD_TOKEN_SHANGHAISILVER=your_shanghai_silver_bot_token_here | ||
| DISCORD_TOKEN_SHANGHAI=your_shanghai_bot_token_here | ||
|
|
||
| # Crypto Feed IDs (Pyth Network) - these are public and safe to share | ||
| # Get fresh IDs from https://pyth.network/docs/developers | ||
| CRYPTO_FEEDS=BTC:0xe62df6c8b4a85fe1a67db44dc12de5db330f7ac66b72dc658afedf0f4a415b43,ETH:0xff61491a931112ddf1bd8147cd1b641375f79f5825126d665480874634fd0ace,SOL:0xef0d8b6fda2ceba41da15d4095d1da392a0d2f8ed0c6c7bc0f4cfac8c280b56d,DOGE:0xdcef50dd0a4cd2dcc17e45df1676dcb336a11a61c69df7a0299b0150c672d25c,DXY:yahoo_finance | ||
| # Pyth Network Feed IDs (comma-separated) | ||
| # Format: CRYPTO:feed_id,CRYPTO:feed_id,... | ||
| CRYPTO_FEEDS=BTC:0xe62df6c8b4a85fe1a67db44dc12de5db330f7ac66b72dc658afedf0f4a415b43,ETH:0xff61491a931112ddf1bd8147cd1b641375f79f5825126d665480874634fd0ace,SOL:0xef0d8b6fda2ceba41da15d4095d1da392a0d2f8ed0c6c7bc0f4cfac8c280b56d | ||
|
|
||
|
Comment on lines
+11
to
+13
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Hardcoded database credentials committed to repositoryCritical Severity The .env.example file contains hardcoded PostgreSQL credentials: Suggested fix: Remove the hardcoded password values from .env.example. Replace with placeholder values that clearly indicate they must be changed: |
||
| # Database - CHANGE THESE PASSWORDS | ||
| POSTGRES_USER=postgres | ||
| POSTGRES_PASSWORD=PdefSMMIa8N22nKwHxmWz5znC13bUFo | ||
| DATABASE_URL=postgresql://postgres:PdefSMMIa8N22nKwHxmWz5znC13bUFo@postgres:5432/pricebot | ||
|
Comment on lines
+14
to
+17
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Hardcoded database password in .env.exampleHigh Severity The .env.example file contains a hardcoded database password ( Suggested fix: Replace the hardcoded password with a placeholder like |
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| { | ||
| "enabledPlugins": { | ||
| "core@factory-plugins": true | ||
| } | ||
| } |
This file was deleted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hardcoded database credentials in .env.example
Critical Severity
The .env.example file contains what appears to be a real database password:
POSTGRES_PASSWORD=PdefSMMIa8N22nKwHxmWz5znC13bUFoand a corresponding DATABASE_URL with the same password embedded. Example/template files should contain only placeholder values likeyour_password_here, never actual credentials. If users copy this file without editing, they may unknowingly use these credentials in production. Anyone with read access to the repository can obtain these credentials.Suggested fix: Replace
PdefSMMIa8N22nKwHxmWz5znC13bUFowith placeholder text likeyour_secure_password_herein both POSTGRES_PASSWORD and DATABASE_URL.