Val Town Code SearchReturn to Val Town

24});
25
26app.post("/example/database/pages", async (c) => {
27  // blob keys map to endpoints for the cron resets
28  const blobKey = await c.req.url.replace("https://", "");
29  const askingFor = c.req.headers.get("asking_for") || "default"; // val.town or default
30
31  // capture the database id to store in the blob
32  const targetId = c.req.headers.get("target_id");
33
34  // get the pages in this database
35  const databaseChildren = await notion.databases.query({ database_id: targetId });
36  // delete all pages to prevent bad actors from leaving naughty rows behi
37  for (const [key, child] of databaseChildren.results.entries()) {
38    const page = await notion.pages.update({
39      page_id: child.id,
42  }
43
44  // get the database
45  const database = await notion.databases.retrieve({ database_id: targetId });
46  // convert the statuses string in the status property into JSON
47  const statuses = JSON.parse(database?.properties?.Statuses?.formula?.expression);
48  // get the first item on the list of statuses, to set the status for new pages
49  const status = statuses[0];
50  // add back pages; fresh start for the next person to add favicons
51  const defaults = ["val.town", "notion.com", "hono.dev"].reverse();
52  // create new database pages from default object
53  for (const item of defaults) {
54    const page = await notion.pages.create({
55      parent: {
56        type: "database_id",
57        database_id: targetId,
58      },
59      properties: {
88});
89
90app.post("/example/database/page", async (c) => {
91  const payload = await c.req.json();
92  const data = await payload?.data;
100
101  // store webhook data in blob storage for resets
102  // capture the database id to store in the blob
103  const databaseId = data?.parent?.database_id;
104  const blobObject = {
105    id: databaseId,
106    date: new Date(),
107    content: askingFor,

13## Technical Architecture
14
15**⚠️ important caveat: the admin dashboard doesn't have auth! currently it just relies on security by obscurity of people not knowing the url to a private val. this is not very secure. if you fork this project and put sensitive data in a database you should think carefully about how to secure it.**
16
17Stevens has been designed with the utmost simplicity and extensibility, much like a well-organized household. At the heart of his operation lies a single "memories" table - a digital equivalent of a butler's meticulous records. This table serves as the foundation for all of Stevens' operations.
45- `dashboard`: the admin view for showing the memories notebook + visualizing imports
46- `dailyBriefing`: stuff related to sending a daily update via telegram
47- `dbUtils`: little one-off scripts for database stuff
48
49## Hiring your own Stevens
57- For the Google Calendar integration you'll need `GOOGLE_CALENDAR_ACCOUNT_ID` and `GOOGLE_CALENDAR_CALENDAR_ID`. See [these instuctions](https://www.val.town/v/stevekrouse/pipedream) for details.
58
59**important caveat: the admin dashboard doesn't have auth! currently it just relies on security by obscurity of people not knowing the url to a private val. this is not very secure, if you put sensitive data in a database you should think carefully about how to secure it.**
60
61Overall it's a simple enough project that I encourage you to just copy the ideas and run in your own direction rather than try to use it as-is.

4
5* `index.ts` - this is the **entrypoint** for this whole project
6* `database/` - this contains the code for interfacing with the app's SQLite database table
7
8## Hono
26## CRUD API Routes
27
28This app has two CRUD API routes: for reading and inserting into the messages table. They both speak JSON, which is standard. They import their functions from `/backend/database/queries.ts`. These routes are called from the React app to refresh and update data.
29
30## Errors

1# Database
2
3This app uses [Val Town SQLite](https://docs.val.town/std/sqlite/) to manage data. Every Val Town account comes with a free SQLite database, hosted on [Turso](https://turso.tech/). This folder is broken up into two files:
4
5* `migrations.ts` - code to set up the database tables the app needs
6* `queries.ts` - functions to run queries against those tables, which are imported and used in the main Hono server in `/backend/index.ts`
7
8## Migrations
9
10In `backend/database/migrations.ts`, this app creates a new SQLite table `reactHonoStarter_messages` to store messages. 
11
12This "migration" runs once on every app startup because it's imported in `index.ts`. You can comment this line out for a slight (30ms) performance improvement on cold starts. It's left in so that users who fork this project will have the migration run correctly.
13
14SQLite has much more limited support for altering existing tables as compared to other databases. Often it's easier to create new tables with the schema you want, and then copy the data over. Happily LLMs are quite good at those sort of database operations, but please reach out in the [Val Town Discord](https://discord.com/invite/dHv45uN5RY) if you need help.
15
16## Queries
17
18The queries file is where running the migrations happen in this app. It'd also be reasonable for that to happen in index.ts, or as is said above, for that line to be commented out, and only run when actual changes are made to your database schema.
19
20The queries file exports functions to get and write data. It relies on shared types and data imported from the `/shared` directory.

12  getAllMemories,
13  updateMemory,
14} from "./database/queries.ts";
15import { type Memory } from "../shared/types.ts";
16import { blob } from "https://esm.town/v/std/blob";

208```
209├── backend/
210│   ├── database/
211│   │   ├── migrations.ts    # Schema definitions
212│   │   ├── queries.ts       # DB query functions
270- Handle API calls properly with proper error catching
271
272### Database Patterns
273- Run migrations on startup or comment out for performance
274- Change table names when modifying schemas rather than altering

13  const navLinks = [
14    { name: "Farcaster SDK", path: "/" },
15    { name: "Database", path: "/db" },
16    { name: "About", path: "/about" },
17  ];
35      <Routes>
36        <Route path="/" element={<FarcasterMiniApp />} />
37        <Route path="/db" element={<Database />} />
38        <Route path="/about" element={<About />} />
39        <Route path="/neynar" element={<Neynar />} />
50        <div className="">✷ Hono + React + Tailwind</div>
51        <div className="">✷ React Router + React Query</div>
52        <div className="">✷ Built-in database (blob storage)</div>
53        <div className="">✷ Farcaster mini app manifest + webhook + embed metadata</div>
54        <div className="">✷ Farcaster notifications (storing tokens, sending recurring notifications, ...)</div>
66}
67
68function Database() {
69  const queryFn = () => fetch("/api/counter/get").then((r) => r.json());
70  const { data, refetch } = useQuery({ queryKey: ["counter"], queryFn });
71  return (
72    <Section className="flex flex-col items-start gap-3 m-5">
73      {/* <h2 className="font-semibold">Database Example</h2> */}
74      <div className="">Counter value: {data}</div>
75      <Button variant="outline" onClick={() => fetch("/api/counter/increment").then(refetch)}>

1// Script to set up the telegram_chats table in SQLite
2// Run this script manually to create the database table
3
4export default async function setupTelegramChatDb() {
25    `);
26
27    return "Telegram chat database table created successfully.";
28  } catch (error) {
29    console.error("Error setting up telegram_chats table:", error);

13## Technical Architecture
14
15**⚠️ important caveat: the admin dashboard doesn't have auth! currently it just relies on security by obscurity of people not knowing the url to a private val. this is not very secure. if you fork this project and put sensitive data in a database you should think carefully about how to secure it.**
16
17Stevens has been designed with the utmost simplicity and extensibility, much like a well-organized household. At the heart of his operation lies a single "memories" table - a digital equivalent of a butler's meticulous records. This table serves as the foundation for all of Stevens' operations.
45- `dashboard`: the admin view for showing the memories notebook + visualizing imports
46- `dailyBriefing`: stuff related to sending a daily update via telegram
47- `dbUtils`: little one-off scripts for database stuff
48
49## Hiring your own Stevens
57- For the Google Calendar integration you'll need `GOOGLE_CALENDAR_ACCOUNT_ID` and `GOOGLE_CALENDAR_CALENDAR_ID`. See [these instuctions](https://www.val.town/v/stevekrouse/pipedream) for details.
58
59**important caveat: the admin dashboard doesn't have auth! currently it just relies on security by obscurity of people not knowing the url to a private val. this is not very secure, if you put sensitive data in a database you should think carefully about how to secure it.**
60
61Overall it's a simple enough project that I encourage you to just copy the ideas and run in your own direction rather than try to use it as-is.

4
5* `index.ts` - this is the **entrypoint** for this whole project
6* `database/` - this contains the code for interfacing with the app's SQLite database table
7
8## Hono
26## CRUD API Routes
27
28This app has two CRUD API routes: for reading and inserting into the messages table. They both speak JSON, which is standard. They import their functions from `/backend/database/queries.ts`. These routes are called from the React app to refresh and update data.
29
30## Errors