#wasix — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #wasix, aggregated by home.social.
-
Been doing a bit of reading for #PrayerOfHannah my #RustLang #SaaS project.
Rather than using #Docker for deployment I'm wondering about compiling is as a #Wasm server app - technically I think #Wasix.
Not a huge number of direct deployment hosts yet (but I think you can deploy fairly lightweight via docker).
#Dbms support might be a limit at present (don't think #sqlx with #sqlite will be an option at the moment) -
Been doing a bit of reading for #PrayerOfHannah my #RustLang #SaaS project.
Rather than using #Docker for deployment I'm wondering about compiling is as a #Wasm server app - technically I think #Wasix.
Not a huge number of direct deployment hosts yet (but I think you can deploy fairly lightweight via docker).
#Dbms support might be a limit at present (don't think #sqlx with #sqlite will be an option at the moment) -
Looks like they also "hard code" class B addresses:
https://github.com/wasix-org/wasix-libc/blob/main/libc-bottom-half/headers/public/wasi/api_wasix.h#L2616Pretty sure n0/n1 means network, and h0/h1 means host. They also don't define the byte layout of this (that I can find, addr_port is not defined in the documentation), so you can't just use inet_addr or inet_pton or a similar layout. So who knows how this works.
-
Looks like they also "hard code" class B addresses:
https://github.com/wasix-org/wasix-libc/blob/main/libc-bottom-half/headers/public/wasi/api_wasix.h#L2616Pretty sure n0/n1 means network, and h0/h1 means host. They also don't define the byte layout of this (that I can find, addr_port is not defined in the documentation), so you can't just use inet_addr or inet_pton or a similar layout. So who knows how this works.