diff options
| author |  OniriCorpe <oniricorpe@yunohost.org> | 2025-04-11 12:42:18 +0200 |
|---|---|---|
| committer |  GitHub <noreply@github.com> | 2025-04-11 12:42:18 +0200 |
| commit | b51aa23458e52d9abfc50a40223ffa22ee372c17 (patch) | |
| tree | 1012fdd83d91fc73757fc237c83ab14b2264d4db | |
| parent | [docs] add instruction about postgres permission (#3981) (diff) | |
| download | gotosocial-b51aa23458e52d9abfc50a40223ffa22ee372c17.tar.xz | |
[docs] add a command to know if the system is compatible with the standard builds (#3980)
| -rw-r--r-- | docs/advanced/builds/nowasm.md | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/docs/advanced/builds/nowasm.md b/docs/advanced/builds/nowasm.md index b89a8e22b..b2aa07acd 100644 --- a/docs/advanced/builds/nowasm.md +++ b/docs/advanced/builds/nowasm.md @@ -15,6 +15,10 @@ However! To enable folks to run **experimental, unsupported deployments of GoToS A GoToSocial binary built with `nowasm` will use the [modernc version of SQLite](https://pkg.go.dev/modernc.org/sqlite) instead of the WASM one, and will use on-system `ffmpeg` and `ffprobe` binaries for media processing. +!!! tip + To test if your system is compatible with the standard builds, you can use this command: + `if grep -qE '^flags.* (sse4|LSE)' /proc/cpuinfo; then echo "Your system is supporting GTS!"; else echo "Your system is not supporting GTS, you'll have to use the 'nowasm' builds :("; fi` + To build GoToSocial with the `nowasm` tag, you can pass the tag into our convenience `build.sh` script like so: ```bash |