mirror of
https://github.com/superseriousbusiness/gotosocial.git
synced 2025-10-29 18:12:25 -05:00
Merge branch 'main' into bot_toggle_fixes
This commit is contained in:
commit
4293897c04
3 changed files with 20 additions and 4 deletions
|
|
@ -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
|
||||
|
|
|
|||
|
|
@ -42,6 +42,13 @@ create user gotosocial with password 'some_really_good_password';
|
|||
grant all privileges on database gotosocial to gotosocial;
|
||||
```
|
||||
|
||||
If you start using Postgres after 14, or you encounter `error executing command: error creating dbservice: db migration error: ERROR: permission denied for schema public`, you should grant `CREATE` permission to your db user:
|
||||
|
||||
```psql
|
||||
GRANT CREATE ON SCHEMA public TO gotosocial;
|
||||
SELECT has_schema_privilege('gotosocial', 'public', 'CREATE'); -- should return t
|
||||
```
|
||||
|
||||
GoToSocial makes use of ULIDs (Universally Unique Lexicographically Sortable Identifiers) which will not work in non-English collate environments. For this reason it is important to create the database with `C.UTF-8` locale. To do that on systems which were already initialized with non-C locale, `template0` pristine database template must be used.
|
||||
|
||||
If you want to use specific options when connecting to Postgres, you can use `db-postgres-connection-string` to define the connection string. If `db-postgres-connection-string` is defined, all other database related configuration fields will be ignored. For example, we can use `db-postgres-connection-string` to connect to `mySchema`, where the user name is `myUser` and password is `myPass` at `localhost` with the database name of `db`:
|
||||
|
|
|
|||
|
|
@ -20,6 +20,8 @@
|
|||
.profile .profile-header {
|
||||
background: $profile-bg;
|
||||
border-radius: $br;
|
||||
margin-bottom: 1rem;
|
||||
padding-bottom: 1rem;
|
||||
|
||||
/*
|
||||
Link to open media in slide
|
||||
|
|
@ -69,6 +71,7 @@
|
|||
.basic-info {
|
||||
position: relative;
|
||||
display: grid;
|
||||
gap: 0 1rem;
|
||||
box-sizing: border-box;
|
||||
grid-template-columns: $avatar-size auto 1fr;
|
||||
grid-template-rows: $overlap $name-size auto;
|
||||
|
|
@ -77,10 +80,12 @@
|
|||
"avatar namerole namerole"
|
||||
"avatar namerole namerole";
|
||||
|
||||
margin: 1rem;
|
||||
margin-top: calc(-1 * $overlap);
|
||||
gap: 0 1rem;
|
||||
padding-bottom: 1rem;
|
||||
/*
|
||||
Margin top to inset profile pic into
|
||||
header image, margin sides to inset
|
||||
basic info from header wrapper.
|
||||
*/
|
||||
margin: calc(-1 * $overlap) 1rem 0 1rem;
|
||||
|
||||
.avatar-image-wrapper {
|
||||
grid-area: avatar;
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue