$ cat ~/.config/salty/config.yml
---
identity: ~/.config/salty/prologic.key
user: prologic@mills.io
That is to say, try to create a config (example above) and see if that makes that crash go away π
$ cat ~/.config/salty/config.yml
---
identity: ~/.config/salty/prologic.key
user: prologic@mills.io
That is to say, try to create a config (example above) and see if that makes that crash go away π
There is this really unsettle tend of "faceless" / "contactless" corporations that rally pisses me off π€¬
There is this really unsettle tend of "faceless" / "contactless" corporations that rally pisses me off π€¬
salty-chat CLI and TUI should "just work"β’ π€
salty-chat CLI and TUI should "just work"β’ π€
@mutefall who graciously documented the setup for a all-in-one setup (get domain, setup domain, stand up broker, etc) did a pretty good job of that docu, but we also probably need more docu.
See if you can tease it apart, but essentially if setup an SRV record for your domain that points to my broker and run
salty-chat register nick@yourdomain which _should_ work as it does a lookup for the SRV record if no broker is provided (optional 2nd argument).If you can get that far, then we've done an "okay" job π
@mutefall who graciously documented the setup for a all-in-one setup (get domain, setup domain, stand up broker, etc) did a pretty good job of that docu, but we also probably need more docu.
See if you can tease it apart, but essentially if setup an SRV record for your domain that points to my broker and run
salty-chat register nick@yourdomain which _should_ work as it does a lookup for the SRV record if no broker is provided (optional 2nd argument).If you can get that far, then we've done an "okay" job π
> I seem to have registered mckinley@mills.io when experimenting with it, but I didnβt know until recently because of a very confusing output. That account does exist, though, because it shows up when using salty-chat lookup.
You are right, the superfluous warning there is very confusing:
> WARN[0001] error looking up user endpoint error="error looking up user mckinley@mills.io: non-2xx response received: 404 Not Found"
I will remove this. It's silly π=
> I seem to have registered mckinley@mills.io when experimenting with it, but I didnβt know until recently because of a very confusing output. That account does exist, though, because it shows up when using salty-chat lookup.
You are right, the superfluous warning there is very confusing:
> WARN[0001] error looking up user endpoint error="error looking up user mckinley@mills.io: non-2xx response received: 404 Not Found"
I will remove this. It's silly π=
> think itβs about time I try out Salty. I followed from the instructions on the website, and it didnβt go too well. I suspect itβs because the local path from my JSON file (/01G268YYHWGNYT9M1M9760KP83) on mckinley.cc doesnβt return anything because I donβt have a broker set up there.
Judging from the output you so kindly provided, this looks like several bugs to me. I might have to spend some time and fix these. I assume you created the Well-Known JSON config file on your web server at the top-level of your domain?
The Endpoint is also wrong, it should be an absolute URI. so that's failed too (bug) π’
Finally in order for you to properly be 100% self-hosted here on your own domain, you'd need to either run msgbus somewhere so you can point your Salty Addr's endpoint at that, or spin up an instance of saltyd which takes care of basically everything automatically.
> think itβs about time I try out Salty. I followed from the instructions on the website, and it didnβt go too well. I suspect itβs because the local path from my JSON file (/01G268YYHWGNYT9M1M9760KP83) on mckinley.cc doesnβt return anything because I donβt have a broker set up there.
Judging from the output you so kindly provided, this looks like several bugs to me. I might have to spend some time and fix these. I assume you created the Well-Known JSON config file on your web server at the top-level of your domain?
The Endpoint is also wrong, it should be an absolute URI. so that's failed too (bug) π’
Finally in order for you to properly be 100% self-hosted here on your own domain, you'd need to either run msgbus somewhere so you can point your Salty Addr's endpoint at that, or spin up an instance of saltyd which takes care of basically everything automatically.
> Is there a way to do that and still be mckinley@mckinley.cc?
Yes. By setting up an SRV record for your domain that points to my broker.
Partial instructions here in DNS Setup
> Is there a way to do that and still be mckinley@mckinley.cc?
Yes. By setting up an SRV record for your domain that points to my broker.
Partial instructions here in DNS Setup
That's what's on our backlog. This means you can (hopefully) modify the translations without having to rebuild, etc.
That's what's on our backlog. This means you can (hopefully) modify the translations without having to rebuild, etc.
yarnd binary, but yes π
It's on our backlog!
yarnd binary, but yes π
It's on our backlog!
Please feel free to contribute improvements and fixes as you see fit! πββοΈ
Please feel free to contribute improvements and fixes as you see fit! πββοΈ