In production, the frontend is a pre-rendered Nextjs app served statically by the Axum +backend server.
+Logs are written to both stdout and ryot.log.* in the working directory. If you
+are reporting a bug, please attach the latest log.
There is a devcontainer +configuration in the repository. You can use it to launch a development environment +with all tools installed.
+In development, both servers are started independently running on :3000 and :8000
+respectively. To get them running, install mprocs, and
+run mprocs in the project root. If you do not want to install mprocs, take a look at
+mproc.yaml to see what all commands are
+needed to get it working.
Here is the minimal configuration required in development mode:
+{
+ "database": {
+ "url": "postgres://postgres:postgres@postgres:5432/postgres"
+ },
+ "server": {
+ "cors_origins": ["http://localhost:3000"],
+ "config_dump_path": "/tmp/ryot.json",
+ "insecure_cookie": true,
+ "samesite_none": true
+ }
+}
+I also recommend the following environment files:
+RUST_LOG="ryot=trace,sea_orm=debug"
+NEXT_PUBLIC_BASE_URL="http://localhost:8000"
+Note
+You will need to run moon run frontend:build before you can get the
+backend running. This needs to be done only once.
You can use Serveo to test webhooks.
+$ ssh -R ryot:80:0.0.0.0:8000 serveo.net
+This will expose your local server on https://ryot.serveo.net. You can use this URL
+in Jellyfin etc. to test events sent to your local Ryot instance.
Another helpful tool is Webhook.site. It can be used to inspect +the requests sent to your server.
+Unless it is a very small change, I prefer creating a separate branch and merging it via an +MR when it is done. The changelog is generated using +git-chglog. Once all changes are done, run the +following command to update the changelog.
+$ git-chglog --next-tag <tag-name> -o CHANGELOG.md
+