I guess by setting below env, it works but not sure how it can for social-app for web in docker... ;-<
github.com/bluesky-soci...
I guess by setting below env, it works but not sure how it can for social-app for web in docker... ;-<
github.com/bluesky-soci...
wc -l log-commits/*
9 atproto
19 indigo
2 ozone
19 social-app
and 17 commits during 8 Mar to 12 Mar
7 atproto
4 indigo
2 ozone
4 social-app
Thanks to CI(github actions) for recording daily commits :-)
wc -l log-commits/*
9 atproto
19 indigo
2 ozone
19 social-app
and 17 commits during 8 Mar to 12 Mar
7 atproto
4 indigo
2 ozone
4 social-app
Thanks to CI(github actions) for recording daily commits :-)
panic: runtime error: ...
goroutine 315
bluesky-social/indigo/events.(*RepoStreamCallbacks).EventHandler(0xc0004439e0?,...
events/consumer.go:37
bluesky-social/indigo/events.(*InstrumentedRepoStreamCallbacks).EventHandler(...
panic: runtime error: ...
goroutine 315
bluesky-social/indigo/events.(*RepoStreamCallbacks).EventHandler(0xc0004439e0?,...
events/consumer.go:37
bluesky-social/indigo/events.(*InstrumentedRepoStreamCallbacks).EventHandler(...
I found some errors in your trial movie. it showed
1) pwgen is not found => please install pwgen (again)
2) your DNS record needed to meet your deploying network.
try ```ping any.${DOMAIN}``` to check and fixed DNS if unreachable.
I found some errors in your trial movie. it showed
1) pwgen is not found => please install pwgen (again)
2) your DNS record needed to meet your deploying network.
try ```ping any.${DOMAIN}``` to check and fixed DNS if unreachable.
just do below, before ```make docker-start```
```
export plcFQDN=plc.directory
make echo
```
and check the output log.
just do below, before ```make docker-start```
```
export plcFQDN=plc.directory
make echo
```
and check the output log.
I checked your code and found that:
it is better READ_ENDPOINTS includes WRITE_ENDPOINT like
READ_ENDPOINTS=https://your-write-plc-endpoint.example.com,...
since current code cannot read the entry which written into write_endpoint. just small updates in readme.
I checked your code and found that:
it is better READ_ENDPOINTS includes WRITE_ENDPOINT like
READ_ENDPOINTS=https://your-write-plc-endpoint.example.com,...
since current code cannot read the entry which written into write_endpoint. just small updates in readme.