![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/eb9cfeb5-4eb5-4b1b-a75c-8d9e04c3f856.png)
Matrix is the protocol. You can have whatever client you like. There are mobile apps that are similar to discord and connect to matrix servers.
Matrix is the protocol. You can have whatever client you like. There are mobile apps that are similar to discord and connect to matrix servers.
I do!
What you mean?
Do you even use Linux?
Cool, thanks!
Series 10 is safe to use in wayland?
Lol I am on the same train
!ithadtobebrazil
You can follow hashtags
Just one more if you don’t mind, please.
Here should not be displaying the ports for lemmy-ui
and lemmy-postgres
too?
OK! So here we go.
I already use Caddy on my server because of other services I have running so I was afraid it could conflict with the caddy container in the docker-compose you provide, so I disabled caddy service just for testing and afterwards I could try to figure how to make it work alongside my current configuration. But for some reason I can’t get my domain to connect to the instance.
So I decided to try different and do not install the caddy container and use the one I have running natively. So I just coppied the Caddyfile content that is generated by the deploy.sh and replaced the env variable with my domain name (just to make sure it would work).
I changed the docker-compose.yml to this:
version: "3.9"
x-logging:
&default-logging
options:
max-size: '500m'
driver: json-file
services:
lemmy:
image: dessalines/lemmy:0.17.4
environment:
- RUST_LOG="warn,lemmy_server=info,lemmy_api=info,lemmy_api_common=info,lemmy_api_crud=info,lemmy_apub=info,lemmy_db_schema=info,lemmy_db_views=info,lemmy_db_views_actor=info,lemmy_db_views_moderator=info,lemmy_routes=info,lemmy_utils=info,lemmy_websocket=info"
volumes:
- ./lemmy.hjson:/config/config.hjson
depends_on:
- postgres
- pictrs
networks:
- lemmyinternal
- lemmybridge
ports:
- 8536:8536
restart: always
logging: *default-logging
lemmy-ui:
image: dessalines/lemmy-ui:0.17.4
environment:
- LEMMY_UI_LEMMY_INTERNAL_HOST=lemmy:8536
- LEMMY_UI_LEMMY_EXTERNAL_HOST=localhost:1236
- LEMMY_HTTPS=true
depends_on:
- lemmy
networks:
- lemmyinternal
ports:
#Always keep em guessing
- 1236:1234
restart: always
logging: *default-logging
pictrs:
image: asonix/pictrs:0.3.1
user: 991:991
env_file:
- ./pictrs.env
volumes:
- pictrs_data:/mnt
networks:
- lemmyinternal
- lemmybridge
restart: always
logging: *default-logging
postgres:
image: postgres:15-alpine
environment:
- POSTGRES_USER=lemmy
- POSTGRES_DB=lemmy
env_file:
- ./postgres.env
volumes:
- postgres_data:/var/lib/postgresql/data
networks:
- lemmyinternal
ports:
- 5432:5432
restart: always
logging: *default-logging
networks:
lemmyexternalproxy:
lemmybridge:
lemmyinternal:
driver: bridge
internal: true
Placed all the .env
in the same folder of the docker-compose.yml
and placed the lemmy.hjson
in this same folder too.
{
setup: {
admin_username: "lemmy"
admin_password: "sjhdakjhsdjhasdkjashdjkahs"
site_name: "Lemmy"
}
hostname: "lemmy.domain"
bind: "0.0.0.0"
port: 8536
tls_enabled: true
pictrs: {
url: "http://pictrs:8080/"
api_key: "dkslahlsdjhasjdçlajsçdaskj"
}
database: {
user: "lemmy"
password: "jahdskjhadjsappdsiadopisap"
host: "postgres"
port: 5432
database: "lemmy"
pool_size: 5
}
}
runned the docker-compose up -d
and everything went OK, no errors in the terminal.
but still my domain don’t connect.
I have disabled cloudflare proxy and cache but nothing helped :(
hi! do you have some IM we could talk please? I am getting insane haha, trying to bring up a server for 4 days now lol I think your method is the closest to work but I am getting something wrong.
Sorry to bring more problems to you.
SOLVED: The problem was caused because I was using a |
In the site name SETUP_SITE_NAME
for some reason the bash script is returning sed: -e expression #7, char 32: unknown option to `s'
I 've looked online and found nothing that related to my problem.
I suspect the problem starts in line 253
because the file lemmy.hjson
is empty and the docker-compose.yml
isn’t created.
What adjustments I need to do to run this locally (in my LAN) just for testing?
Don’t be sorry friend, you are helping and you are awesome for that :)
I get this error:
When I try to access
http://localhost:1236
I gave up to publish it and am trying now just run locally to see what’s going on. And still I can’t.
I am out of ideas :(
are you using nginx? I am trying with caddy (because I already use it with other apps) but I can’t access, do you have some idea how I could debug where the issue is?
Even those are not private.