1.0.0 #1

Open
opened 2025-01-10 18:48:45 +00:00 by Brooke · 7 comments
Owner
  • add release file

Features in recipe

  • SMTP
  • SSO (OIDC)
  • add proper healthcheck
  • add optional external database
  • GtS cli export
  • GtS cli import
  • local/remote storage
  • federation configuration

Tested

  • SMTP
  • SSO
  • Postgres
  • Sqlite3
  • GtS cli export
  • GtS cli import
  • S3 Storage backend
- [x] add release file ## Features in recipe - [x] SMTP - [x] SSO (OIDC) - [x] add proper healthcheck - [x] add optional external database - [ ] GtS cli `export` - [ ] GtS cli `import` - [x] local/remote storage - [x] federation configuration ## Tested - [x] SMTP - [ ] SSO - [x] Postgres - [x] Sqlite3 - [ ] GtS cli `export` - [ ] GtS cli `import` - [ ] S3 Storage backend
Brooke self-assigned this 2025-01-10 18:48:46 +00:00
Brooke pinned this 2025-02-09 10:42:49 +00:00
Owner

is there a nowasm official container? would you consider using it or adding it as an option? afaik the regular versions has ffmpeg and other libraries embedded as wasm binaries, but a manual deploy on a very low resources vps would crash the system because it needs a lot of ram to dump those binaries into a temporary directory, and it would use a lot of ram altogether, while the nowasm version starts immediately and uses a lot less ram.

is there a nowasm official container? would you consider using it or adding it as an option? afaik the regular versions has ffmpeg and other libraries embedded as wasm binaries, but a manual deploy on a very low resources vps would crash the system because it needs a lot of ram to dump those binaries into a temporary directory, and it would use a lot of ram altogether, while the nowasm version starts immediately and uses a lot less ram.
Owner

also v0.18 is out :D

also v0.18 is out :D
Owner

aside: @fauno i would really support an issue opened on the GtS side re: this spike in requirements from them bundling ffmpeg into the binary. i had also critiqued this path as compromising the lightweight nature of the system. if youre seeing breakage on low-end systems, we should let them know.

aside: @fauno i would really support an issue opened on the GtS side re: this spike in requirements from them bundling ffmpeg into the binary. i had also critiqued this path as compromising the lightweight nature of the system. if youre seeing breakage on low-end systems, we should let them know.
Author
Owner

also v0.18 is out :D

I've just started testing and the upgrade process seems to be a little broken, sorry it's been taking a while currently juggling other work.

> also v0.18 is out :D I've just started testing and the upgrade process seems to be a little broken, sorry it's been taking a while currently juggling other work.
Author
Owner

aside: @fauno i would really support an issue opened on the GtS side re: this spike in requirements from them bundling ffmpeg into the binary. i had also critiqued this path as compromising the lightweight nature of the system. if youre seeing breakage on low-end systems, we should let them know.

+1 this seems like an upstream issue, I wouldn't feel comfortable with using a separate image if it wasn't from gts directly and I don't know of a version that doesn't use wasm.

> aside: @fauno i would really support an issue opened on the GtS side re: this spike in requirements from them bundling ffmpeg into the binary. i had also critiqued this path as compromising the lightweight nature of the system. if youre seeing breakage on low-end systems, we should let them know. +1 this seems like an upstream issue, I wouldn't feel comfortable with using a separate image if it wasn't from gts directly and I don't know of a version that doesn't use wasm.
Owner

yeah i did ask them about ram usage on the upgrade from 0.17 to 0.18 and was recommended to try out the nowasm version. i'll collect some energy to ask properly...

yeah i did ask them about ram usage on the upgrade from 0.17 to 0.18 and was recommended to try out the nowasm version. i'll collect some energy to ask properly...
Owner

they do warn you it's super unsupported and not even bother them about it:

https://docs.gotosocial.org/en/latest/advanced/builds/nowasm/

you're already providing a cache, so this is covered:

https://docs.gotosocial.org/en/latest/getting_started/installation/container/#wazero-compilation-cache-optional

although my issue with the official wasm version is that the vm i was on crashed during wasm compilation, so i had to turn off every service before enabling gts (or run it on a different server and copy the files? i don't remember what worked now) and the 0.18 upgrade used way more ram altogether

they do warn you it's super unsupported and not even bother them about it: https://docs.gotosocial.org/en/latest/advanced/builds/nowasm/ you're already providing a cache, so this is covered: https://docs.gotosocial.org/en/latest/getting_started/installation/container/#wazero-compilation-cache-optional although my issue with the official wasm version is that the vm i was on crashed during wasm compilation, so i had to turn off every service before enabling gts (or run it on a different server and copy the files? i don't remember what worked now) and the 0.18 upgrade used way more ram altogether
Sign in to join this conversation.
No description provided.