tidwall / tidwall/tile38

Setting up Tile38 for geofence notifications

Open
#331 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
9.7k
Forks
622
PR merge metrics
No merged PRs in 30d

Description

I've tried to set up geofence notifications between two servers using Linux and I have run into a problem I can not seem to solve. I brought up an instant of both servers at the same time and called one server Server one and the other Server two. I ran the command on Server one "tile38-server" to bring up the server and kept it running the entire time. I then started a wehbook test consumer on Server two by typing the command "tile38-server --webhook-http-consumer-port 9851". I then created a webhook on Server one that points to an endpoint on Server two by typing the command "SETHOOK myhook http://server-2-ip:9851/endpoint NEARBY fleet FENCE POINT 33 -115 50000" (points, url, and distance varry). After this I then created Server one data in hopes that the geofence notifications would be delivered on server two but I did not get any notifications. Can someone please help me and tell me if I am doing something wrong? Thanks in advance for the help. Both servers acknowledged all the above commands and configurations properly.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the setup with tile38-server on Server one and --webhook-http-consumer-port 9851 on Server two, then inspect the SETHOOK configuration and server logs. Done means the cause of the missing cross-server notifications is identified and the verified configuration or behavior is recorded.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
backend, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.