@Pikacnu

1. Add a simple frontend using SvelteFlow
   (This is my first time using Svelte)
2. Wrap GStreamer into node-like abstractions
   (This will sync with the frontend)

• Note: This workflow is just to get started with SvelteFlow; it’s not the final result.
• Note: The GStreamer component is still a work in progress (WIP).

Figuring out how to parse video and mux it into the target format (FLV).
Asked AI to understand how GStreamer works and how to build a proper pipeline.
Also tried to start SRT and WHIP listeners.
*WHIP doesn’t work for this use case because it can’t handle multiple audio tracks.

Try to use gst to encode / decode video (from file now)
Use 2 mpv to play video and audio(autoaudio/video won’t work and i have no idea.)
Also platfrom’s chat room fetcher (not complete yet)

There is it’s pipeline:

filesrc → matroskademux ──(video/x-av1)→ av1parse → av1dec → videoconvert → x264enc → queue → appsink ─→ mpv #1 (H.264)
                        └──(audio/x-opus)→ opusdec → queue → audioconvert → wavenc → appsink ─→ mpv #2 (WAV)

1. Write readme (helped by ai)
2. Fix bug when parsing hostname
3. add ci to build docker image

Finally I finish it
weeee

1. make function execute by sub-domain (see image below)
2. add kv store endpoint (and also dashboard)
3. make you able to make function private (still can test)
4. warp function kv_set/ delete/get into a object
   (kv.set / kv.delete / kv.get)

1. Finished the frontend (with help from AI)
2. Bug fixing (a lot of bugs… one of them was a deadlock during environment injection)
3. Passed requests to functions (it can now process requests)
4. Added more information to execution details (debug info)

Ahhh…
The frontend is almost finished,with some examples and API documentation (all in the same docs).
Built using Nuxt UI and Vue.
The next devlog should be the last one before the first release.
I’ll make it able to detect the hostname to handle function calls (similar to Cloudflare Workers).

Screenshot is part of the website

1. Add a rate limiter to API endpoints (the rate limit for each function can be modified via API).
2. Add key-value storage (accessible only in scripts).
3. Add environment variable storage (can be updated via API).
4. Change user-related APIs to admin-only access.

The basic functionality I think is needed has been completed.
Next step: build the frontend (admin panel and documentation).

1. Update schema (for user and auth.)
2. Add User and sessions.
3. Exec now can run with starlark.

(image is ai generated test code)

1. add a value driven rack mount generate
2. create a rack mount for pi slice
3. create pi slice

Img:

1. pi slice
2. slice holder
3. A small plate to adjust (fix) screw mount misplace problem

With multiple adjustment of model.
For exp: PI slice originally didn’t have hole at end of the box. It’s because without it. Power cable can’t plug in.
And multiple times adjust hole position.

Add a cli tool to update / sync config

1. Add price tip to notify price of tokens.
2. Add a json file for free models.

1. Write a simple router using the built-in net/http.
2. Design a basic database schema to store binaries and function information.
3. Create a database wrapper. (which use Transaction as main exec method)
4. Support two languages that can compile and execute from binaries.
5. Ensure both languages can generate responses (JavaScript returns an object, Starlark returns a dict).
6. Build a simple HTTP server to test functions (compile / execute / save to DB).

TODO:

1. Add support for Starlark.
2. Implement authentication.
3. Create a frontend / admin panel.

It might take some time to work on next step.
Not only because it have lots things to do, also due to I am trying to create something by 3D Printing.
Spending too much time on it…
If I can share those model. It will be nice.

Add full starlark request like fetch.
also batch sync

Still didn’t know why it will be blockout when using async…
So I make JS only can run sync
and add fetchbatch to let mulitple fetch able to happen

Just add more function to fetch and response.
and force js function return obj as response source.

and maybe I will give up on settimeout (though I didn’t try.) maybe after finish main function.
also I will make js function first.
still didn’t know how to let starlark have async ability.
Seems like js code didn’t work properly…
fix it nextday!

1. change quickjs lib from modernc.org/quickjs to github.com/fastschema/qjs for better control
2. add async sleep and simple fetch function for js (work as builtin function)
3. add a simple http related file to do any http related things

Next might be add fetch in starlark
and try to make it have async
and maybe make a settimeout?
also needed to extend fetch function (currently only have basic function)

1. Complete sandbox Exec(both js and starlark)
   (currently scan dir and execut file inside)

2. Implement sleep and print / console.log
   (warp as fmt.Printf)

Plan to add http server and request related thing later