Val Town Code SearchReturn to Val Town

140          });
141        } catch (error) {
142          console.error('Error fetching categories:', error);
143          return res.json({
144            type: 4,
145            data: { content: 'Sorry, I encountered an error fetching categories.' }
146          });
147        }

8    "start": "node index.js",
9    "dev": "node index.js",
10    "fetch": "node val-town-cron.js",
11    "register": "node discord-commands.js",
12    "interactions": "node interactions-endpoint.js",

10- **Furniture Focus**: Special features for tracking furniture links and discussions
11- **Val.town Integration**: Runs on Val.town for easy deployment and scheduling
12- **Periodic Updates**: Automatically fetches new messages on a schedule
13
14## Use Cases
58   ```
59
606. Test the DM fetching process
61   ```
62   node val-town-cron.js
84   - Add the same environment variables from your `.env` file
85
865. Set up a scheduled task on Val.town for periodic DM fetching
87   - Create a new scheduled task using the Val.town dashboard
88   - Use the `discordDMBotCron` function
108
109- `GET /health`: Health check endpoint
110- `POST /api/fetch-dms`: Manually trigger DM fetching
111- `POST /api/process-links`: Manually trigger link processing
112- `POST /api/query`: Submit a query about your message history

239    
240    // Inject data to avoid extra round-trips
241    const initialData = await fetchInitialData();
242    const dataScript = `<script>
243      window.__INITIAL_DATA__ = ${JSON.stringify(initialData)};
286
2875. **API Design:**
288   - `fetch` handler is the entry point for HTTP vals
289   - Run the Hono app with `export default app.fetch // This is the entry point for HTTP vals`
290
291

1import { initializeDatabase } from './database.js';
2import { fetchAndStoreDMs } from './discord-client.js';
3import { batchProcessLinks } from './link-analyzer.js';
4import express from 'express';
20});
21
22// Manual trigger for fetching DMs
23app.post('/api/fetch-dms', async (req, res) => {
24  try {
25    console.log('Manually triggering DM fetch...');
26    await fetchAndStoreDMs();
27    res.json({ success: true, message: 'DM fetch completed successfully' });
28  } catch (error) {
29    console.error('Error fetching DMs:', error);
30    res.status(500).json({ success: false, error: error.message });
31  }

119export async function extractLinkMetadata(url) {
120  try {
121    // In a production system, you'd want to actually fetch the page content
122    // For simplicity, we'll make an educated guess based on the URL
123    

15- **AI Integration**: Leverages Anthropic's Claude API for analysis
16- **Discord Integration**:
17  - Bot token for fetching messages
18  - Slash commands for user interactions
19  - Webhook endpoint for Discord interactions
502. Copy the contents of the backend directory
513. Set up the required environment variables
524. Create a cron schedule for periodically fetching messages and processing links
53
54## Usage
58- `GET /health`: Check if the service is running
59- `POST /api/interactions`: Discord interactions endpoint
60- `POST /api/fetch-dms`: Manually trigger DM fetching
61- `POST /api/process-links`: Manually trigger link processing
62- `POST /api/query`: Process a query about your messages
63- `POST /api/commands/search`: Endpoint for search commands
64- `POST /api/register-commands`: Register Discord slash commands
65- `GET /api/cron/fetch-dms`: Cron endpoint for fetching DMs
66- `GET /api/cron/process-links`: Cron endpoint for processing links
67

142export async function extractLinkMetadata(url: string): Promise<MetadataResult> {
143  try {
144    // In a production system, you'd want to actually fetch the page content
145    // For simplicity, we'll make an educated guess based on the URL
146    

3import { cors } from "https://esm.sh/@hono/cors@0.0.8";
4import { initializeDatabase } from "./database.ts";
5import { fetchAndStoreDMs } from "./discord-client.ts";
6import { handleDiscordInteractionRequest } from "./discord-interactions.ts";
7import { batchProcessLinks } from "./link-analyzer.ts";
85});
86
87// Manual trigger for fetching DMs
88app.post("/api/fetch-dms", async c => {
89  try {
90    log("Manually triggering DM fetch...", "info");
91    const messages = await fetchAndStoreDMs();
92    return c.json({ 
93      success: true, 
94      message: "DM fetch completed successfully", 
95      count: messages.length,
96      timestamp: new Date().toISOString()
97    });
98  } catch (error) {
99    log(`Error fetching DMs: ${error instanceof Error ? error.message : String(error)}`, "error");
100    return c.json({ 
101      success: false, 
247
248/**
249 * Handles the scheduled DM fetch cron job
250 */
251export async function cronFetchDMs() {
252  try {
253    log("Running scheduled DM fetch...", "info");
254    await initializeServices(); // Ensure services are initialized
255    const messages = await fetchAndStoreDMs();
256    
257    log(`Scheduled DM fetch completed successfully. Fetched ${messages.length} messages.`, "info");
258    return { 
259      success: true, 
260      message: "Scheduled DM fetch completed successfully", 
261      count: messages.length,
262      timestamp: new Date().toISOString()
263    };
264  } catch (error) {
265    log(`Error in DM fetch cron job: ${error instanceof Error ? error.message : String(error)}`, "error");
266    return { 
267      success: false, 
297
298// Expose cron endpoints via HTTP as well
299app.get("/api/cron/fetch-dms", async c => {
300  const result = await cronFetchDMs();
301  return c.json(result, result.success ? 200 : 500);
302});
313});
314
315// Export the fetch handler for Val.town HTTP vals
316export default app.fetch;

53  
54  try {
55    const response = await fetch(endpoint, {
56      method: 'PUT',
57      headers: {