48 lines
1.4 KiB
Plaintext
48 lines
1.4 KiB
Plaintext
# Deploy Beacon Edge Function
|
|
|
|
The beacon creation is failing because the edge function hasn't been deployed to Supabase yet.
|
|
|
|
## Deploy Command
|
|
|
|
Run this command from the project root:
|
|
|
|
```bash
|
|
supabase functions deploy create_beacon
|
|
```
|
|
|
|
## What This Does
|
|
|
|
The `create_beacon` edge function will:
|
|
1. Create a new post with `is_beacon: true`
|
|
2. Set the location as a PostGIS point
|
|
3. Store beacon type (safety, weather, traffic, community)
|
|
4. Calculate initial confidence score based on user's trust score
|
|
5. Make it appear in both:
|
|
- The beacon map (when beacon mode is enabled)
|
|
- The user's timeline as a regular post
|
|
|
|
## Beacon Posts vs Regular Posts
|
|
|
|
Beacons are special posts with these properties:
|
|
- `is_beacon: true` - Marks it as a beacon
|
|
- `beacon_type` - Type of alert (safety/weather/traffic/community)
|
|
- `location` - PostGIS point for map display
|
|
- `confidence_score` - Community-verified accuracy (0.0-1.0)
|
|
- `is_active_beacon: true` - Currently active
|
|
- `allow_chain: false` - Beacons don't allow chaining
|
|
|
|
Users will see beacons:
|
|
- **On the map** when they have beacon mode enabled
|
|
- **In timelines** like any other post (if the viewer has beacon mode enabled)
|
|
|
|
## After Deployment
|
|
|
|
Test by:
|
|
1. Opening the Beacon tab
|
|
2. Enabling beacon mode (location permission)
|
|
3. Tapping "Drop Beacon"
|
|
4. Filling in the form with optional photo
|
|
5. Submitting
|
|
|
|
The beacon should appear both on the map and in the user's post timeline.
|