!SMloEYlhCiqKwRLAgY:fachschaften.org

Conduit Matrix Server

1834 Members
https://conduit.rs Release Party! v0.7.0 We follow the Matrix Code of Conduct1003 Servers

Load older messages


SenderMessageTime
26 May 2024
@matthias:ahouansou.czMatthiasThat wouldn't have prevented it from slipping through.10:32:36
@emma:rory.gayEmma [it/its]no i meant, have a large amount of reviews before anything gets merged into main, but have a lower treshold on dev (but still have the large amount on dev->main transitiions)10:36:52
@emma:rory.gayEmma [it/its]essentially, treat dev as "here be dragons", while keeping a central place for in-dev features so people can test them10:38:33
@matthias:ahouansou.czMatthias
In reply to@emma:rory.gay
no i meant, have a large amount of reviews before anything gets merged into main, but have a lower treshold on dev (but still have the large amount on dev->main transitiions)
Isn't that what next is for already?
10:41:43
@timokoesters:fachschaften.orgTimo ⚡️Next is kept pretty clean so no databases break10:42:28
@matthias:ahouansou.czMatthiasTrue, but besides that...10:43:32
@matthias:ahouansou.czMatthiasMerge requests shouldn't be messing with the database often enough to consider a dedicated branch where those merge requests could be allowed imo.10:44:43
@emma:rory.gayEmma [it/its]"next" is what i meant when i said "main"10:46:31
@emma:rory.gayEmma [it/its]
In reply to @matthias:ahouansou.cz
Merge requests shouldn't be messing with the database often enough to consider a dedicated branch where those merge requests could be allowed imo.
i think its more logic changes that cause unrecoverable data consistency issues (eg. softfailed events)
10:47:07
@matthias:ahouansou.czMatthiasI'm not sure changes that could cause that happen often either.10:56:25
@matthias:ahouansou.czMatthias* I'm not sure changes that could cause that happen happen that often either.10:56:42
@emma:rory.gayEmma [it/its]maybe not, but its good to have a bit of a safety net on that front10:59:26
@maxwell:matrix.maxwellmatthis.deMaxwell joined the room.11:14:03
@eroc1990:matrix.orgeroc1990 set a profile picture.14:13:53
@nya:catmaid.moeMoonlight changed their profile picture.20:29:53
@nya:catmaid.moeMoonlight 20:30:12
@kristoff:c2.krbonne.netkristoff changed their display name from Kristoff to kristoff ⚡️.21:12:03
@kristoff:c2.krbonne.netkristoff 21:12:31
@kristoff:c2.krbonne.netkristoff changed their display name from kristoff ⚡️ to kristoff.21:12:51
@kristoff:c2.krbonne.netkristoff 21:12:51
@n:matrix.nbios.netnHi everyone guys, is this a correct configuration to use the automatic well known files in the docker with nginx?21:34:15
@n:matrix.nbios.netn
location /_matrix/ {
    proxy_pass http://127.0.0.1:6167;
    proxy_set_header Host $http_host;
    proxy_buffering off;
    proxy_read_timeout 5m;
}

location /.well-known/matrix/* {
    proxy_pass http://127.0.0.1:6167;
    proxy_set_header Host $http_host;
    proxy_buffering off;
    proxy_read_timeout 5m;
}
21:34:27
@n:matrix.nbios.netn
In reply to @n:matrix.nbios.net
location /_matrix/ {
    proxy_pass http://127.0.0.1:6167;
    proxy_set_header Host $http_host;
    proxy_buffering off;
    proxy_read_timeout 5m;
}

location /.well-known/matrix/* {
    proxy_pass http://127.0.0.1:6167;
    proxy_set_header Host $http_host;
    proxy_buffering off;
    proxy_read_timeout 5m;
}

I reverted to serving them manually, it wasn't working. If anyone has the same problem with sliding-sync:

location /.well-known/matrix/client {
    return 200 '{"m.homeserver": {"base_url": "https://DOMAIN"}, "org.matrix.msc3575.proxy": {"url": "https://DOMAIN"}}';
    default_type "application/json; charset=utf-8";
    add_header 'Access-Control-Allow-Origin' '*';
    add_header 'Access-Control-Allow-Methods' 'GET, POST, PUT, DELETE, OPTIONS';
    add_header 'Access-Control-Allow-Headers' 'X-Requested-With,Content-Type,Authorization';
}

location /.well-known/matrix/server {
    return 200 '{"m.server": "DOMAIN:443"}';
    default_type "application/json; charset=utf-8";
}


location / {
    return 404;
}
23:23:19
@sabba:matrix.orgN left the room.23:54:14
27 May 2024
@potato:potato.rspotato ⚡️
In reply to @n:matrix.nbios.net
Hi everyone guys, is this a correct configuration to use the automatic well known files in the docker with nginx?
im not sure if this line should have the `<a>` tag? what does it mean?
```
proxy_pass <a>http://127.0.0.1:6167</a>;
```
00:07:34
@potato:potato.rspotato ⚡️
In reply to @n:matrix.nbios.net
Hi everyone guys, is this a correct configuration to use the automatic well known files in the docker with nginx?
*
00:09:22
@n:matrix.nbios.netn
In reply to @potato:potato.rs
im not sure if this line should have the `<a>` tag? what does it mean?

```
proxy_pass <a>http://127.0.0.1:6167</a>;
```
Was just formatted here in html
00:15:28
@potato:potato.rspotato ⚡️Will take another look when I get home00:16:21
@potato:potato.rspotato ⚡️

in my nginx configuration, i have all 3 location blocks defined, /.well-known/matrix/client and /.well-known/matrix/server and /_matrix. is that also something similar to what you have tried already? n

02:20:57
@potato:potato.rspotato ⚡️other than that, each of your 3 nginx location blocks seem ok to me02:21:55

There are no newer messages yet.


Back to Room ListRoom Version: 6