fullmoon VS upspin

You can use the excellent fullmoon framework that takes care of a lot for you

https://github.com/pkulchenko/fullmoon

Then using lua is not much different than python/flask

My goal is similar to Joseph's (a platform for local first applications using CRDTs), but the approach is slightly different, as I'm building it based on SQLite synchronization using its session extension (https://www.sqlite.org/sessionintro.html) as the encoding mechanism. I plan to incorporate this sync functionality into my web framework (https://github.com/pkulchenko/fullmoon) to allow any application built with it to become "sync-enabled" with just a couple of additional lines of code.

Found it whilst checking out a web framework specifically for redbean: https://github.com/pkulchenko/fullmoon

This may be of interest to you then: https://github.com/pkulchenko/fullmoon

I've been having a lot of fun with this developing tiny webapps using Fullmoon[1]. I love Lua, but I frequently bounce between a Windows PC and a Linux PC. Having redbean + Fullmoon has made it a breeze switching back and forth without having to deal with system Lua installs. SQLite and the thorough amount of built-ins[2] is also a dream.

[1] https://github.com/pkulchenko/fullmoon

[2] https://redbean.dev/#functions

Yes, that register patch may be needed on some Linux systems; I'll add this to the documentation.

Redbean can't use the system Lua, so it comes bundled with its own Lua interpreter (Lua 5.4; there is also work being done to allow LuaJIT or Luau to be embedded instead).

The modules need to be put in the .lua directory within redbean archive; redbean searches within its archive, so you don't need to set LUA_PATH/LUA_CPATH. I have instructions on how to get examples working included in the examples (https://github.com/pkulchenko/fullmoon/tree/more-links#examp...) section.

In terms of the size, this includes MbedTLS and SQLite, so if you don't need those modules, you can compile redbean without them, which should reduce the size considerably.

Super intriguing. Thanks for sharing!

It reminds me a bit of an early Go project called Upspin [1]. And also a bit of Solid [2]. Did you get any inspiration from them?

What excites me about your project is that you're addressing the elephant in the room when it comes to data sovereignty (~nobody wants to self-host a personal database but their personal devices aren't publicly accessible) in an elegant way.

By storing the data on my personal device and (presumably?) paying for a managed relay (and maybe an encrypted backup), I can keep my data in my physical possession, but I won't have to host anything on my own. Is that the idea?

https://upspin.io/

There are a few Go projects meant to be learned from:

- https://github.com/pion/opus for to learn audio

- https://github.com/benbjohnson/wtf for overall production quality

- https://github.com/upspin/upspin difficult to explain, personally I'm not a fan of the errors

You could also take a look at some real-world open-source projects. I like upspin for its idiomatic approach.

For example, Rob Pike's upspin places all its validations in the separate package. Do you agree with that approach? Which yet proven options there are?

Just a few projects that could perhaps interest you in terms of design of your own solution :

Upspin: https://upspin.io/

The early error wrapping work which emerged out of the Upspin project, that eventually made its way into the errors package, included stack traces in the wrap error. This would provide exactly what it appears you seek.