I've seen this print sydent's startup lines and persist data to the /data volume. I could make a GET request to localhost:8090/ and got a 404 error page for my troubles, together with an entry in Sydent's log. I haven't tested this any more thoroughly than that.
To inspect the container while it's running, get the container id with
docker ps and then:
$ docker exec -it 001f9bfc6a54 bash
sydent@001f9bfc6a54:/home/sydent$ ls
src venv
sydent@001f9bfc6a54:/home/sydent$ ls src
README.rst poetry.lock pyproject.toml requirements.txt res scripts sydent
sydent@001f9bfc6a54:/home/sydent$ ls venv
bin lib pyvenv.cfg
Pull Request Checklist
[ ] Pull request includes a changelog file. The entry should:
Be a short description of your change which makes sense to users. "Fix a bug that prevented receiving messages from other servers." instead of "Move X method from EventStore to EventWorkerStore.".
Include 'Contributed by Your Name.' or 'Contributed by @your-github-username.' — unless you would prefer not to be credited in the changelog.
Use markdown where necessary, mostly for code blocks.
End with either a period (.) or an exclamation mark (!).
To test:
I've seen this print sydent's startup lines and persist data to the
/data
volume. I could make a GET request to localhost:8090/ and got a 404 error page for my troubles, together with an entry in Sydent's log. I haven't tested this any more thoroughly than that.To inspect the container while it's running, get the container id with
docker ps
and then:Pull Request Checklist
EventStore
toEventWorkerStore
.".code blocks
.