Closed sad1y closed 5 years ago
Can you show the server log too?
Does user usrGSjCKKgfjsY
exist? What's the defacs
of this user?
i ran server in docker container and attached to it by docker attach --sig-proxy=true
but unfortunately stdout is empty. I also searched for any logging options but didnt find anything.
could you guide me how to do it properly? thanks
and yes this user exists (builtin alice
)
To see the logs in the running container do this:
docker exec -it name-of-the-running-container /bin/bash
Then see the log with tail -50 /var/log/tinode.log
@or-else it works like a charm, thank you. the problem is that i didnt subscribe to topic which i want to change, i didnt get it from the start but if i get it right, every single action with topic required subscription, right? if so is there any more convenient way to subscribe to every topic that i have (when i login in from the other device, for example)? or just send request for each of them?
every single action with topic required subscription, right?
every action except:
or just send request for each of them?
Yes. The topic must be loaded into memory before anything can be done with it. The topic is loaded into memory on {sub}
.
Take a look a root-user
branch. It has a new feature: it allows a root
user to to issue a gRPC request on behalf of another user. In your case instead of {sub user1} to topic then {set user2} you can directly issue a {sub user2}.
Don't forget to issue {leave}
when you are done with the topic.
BTW, if you need to create the initial setup for a lot of users then you can modify init-db to pre-create the database with the users, topics, and subscriptions. Afterwards, as new users join your system, you only need to create the topics and subscriptions for each new user individually. It won't matter if you {sub} first for each user. You are unlikely to have a million new users every day.
You are awesome! Thanks a lot
Subject of the issue
My ultimate goal - creating group topics and invite group of people with read access only, when appropriate circumstances happens i need to give them write access permission. so, for now i stuck with invite user into topic
client logs (gRpc):
as you can see i send
{set}
with{sub}
to topic which is owned by me and for some reasons server respond me with 403 error. What i doing wrong?