Max/zkldi_Tachi
1
0
Fork 0
mirror of https://github.com/zkldi/Tachi.git synced 2026-10-12 01:08:29 +03:00
Code Issues Packages Projects Releases Wiki Activity

sunday 5th apr (rip mark hollis) (#52)

Browse Source 
* lots of work

* feat: move rg-stats in, ensure consistency in db queries

* the clocks dont work

* almost

* ok jesus been and gone now back to usual
This commit is contained in:
zk
2026-04-06 01:25:30 +01:00
committed by GitHub
parent 71e8aa2152
commit edda03e916
217 changed files with 11757 additions and 1496 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/docs/codebase/setup/config.md
+3 -16
View File
@@ -36,7 +36,6 @@ the main benefits for us are as follows:
REDIRECT_URI: "https://example.com",
},
ARC_AUTH_TOKEN: "unused",
ENABLE_SERVER_HTTPS: false,
OUR_URL: "https://example.com",
INVITE_CODE_CONFIG: {
BATCH_SIZE: 2,
@@ -44,7 +43,7 @@ the main benefits for us are as follows:
BETA_USER_BONUS: 5,
},
CDN_CONFIG: {
WEB_LOCATION: "http://127.0.0.1:9000/tachi-public",
WEB_LOCATION: "http://localhost:9000/tachi-public",
SAVE_LOCATION: {
TYPE: "S3_BUCKET",
ENDPOINT: "http://tachi-s3:9000",
@@ -161,18 +160,6 @@ If present, these define our OAuth2 Client data for interacting with these servi
Maybe a better solution would be to have the API_URL inside the OAUTH2_INFO. Ah well.
### ENABLE_SERVER_HTTPS
- Type: Boolean (optional)
Whether to use HTTPS. If this is set to true, the files `cert/key.pem` and `cert/cert.pem` will be
used as the privateKey and the certificate, respectively.
!!! note
In production, we use an Nginx reverse proxy which handles this.
A warning will be emitted if you are using HTTPS mode, as it's not generally meant to be used
at this level.
### CLIENT_DEV_SERVER
- Type: String
@@ -374,7 +361,7 @@ If no LOGGER_CONFIG is provided, this is not set.
Configures the CDN for the Tachi Server. Files are always stored in an S3-compatible bucket (AWS S3, Backblaze, MinIO, etc.).
For local development with `docker-compose-dev.yml`, run the `tachi-s3` MinIO service and point `SAVE_LOCATION.ENDPOINT` at it (from the `tachi-dev` container, `http://tachi-s3:9000`). Use a `WEB_LOCATION` URL that browsers can load (for example `http://127.0.0.1:9000/<bucket>` when MinIO’s API port is published to the host).
For local development with `docker-compose-dev.yml`, run the `tachi-s3` MinIO service and point `SAVE_LOCATION.ENDPOINT` at it (from the `tachi-dev` container, `http://tachi-s3:9000`). Use a `WEB_LOCATION` URL that browsers can load (for example `http://localhost:9000/<bucket>` when MinIO’s API port is published to the host).
```ts
interface CDN_CONFIG: {
@@ -414,7 +401,7 @@ If not set, this will log a warning and default to 8080.
### MONGO_URL
Where our mongoDB instance is. This would be `127.0.0.1:27017` if hosting on the same box.
Where our mongoDB instance is. This would be `localhost:27017` if hosting on the same box.
If not set, this will terminate the process with a critical error.
### SEQ_URL
docs/docs/contributing/components/core.md
+1 -1
View File
@@ -20,7 +20,7 @@ To run the client and server, use `just start`. You can hit `Ctrl+C` to stop the
## Editing the Client
With `just start` running, the client will listen for changes you make, and reload accordingly. You will see your changes reflected on http://127.0.0.1:3000.
With `just start` running, the client will listen for changes you make, and reload accordingly. You will see your changes reflected on http://localhost:3000.
## Editing the Server
docs/docs/contributing/components/documentation.md
+1 -1
View File
@@ -28,7 +28,7 @@ Other than that, our documentation is [markdown](https://www.markdownguide.org/b
## Running the Documentation
Use `just docs start` inside Tachi to start up a local documentation viewer on http://127.0.0.1:8001.
Use `just docs start` inside Tachi to start up a local documentation viewer on http://localhost:8001.
This will automatically refresh when you edit anything related to the documentation, so you can quickly see how your stuff goes.
docs/docs/contributing/setup.md
+3 -11
View File
@@ -158,21 +158,13 @@ You should now be properly authenticated!
With a terminal open inside the `Tachi` container you just cloned, run `just start`.
The frontend will be running on `http://127.0.0.1:3000`.
The backend will be running on `https://127.0.0.1:8080`.
!!! danger
The backend **always runs on HTTPS** in local development. This is because browsers
tend to _really_ hate HTTP mode nowadays, and it causes so many problems.
You **need** to navigate to your running instance of the backend in a browser, and tell
the browser that you trust these certificates. Otherwise, all client requests to
the server will silently be chomped by the browser.
The frontend will be running on `http://localhost:3000`.
The backend listens on `http://localhost:8080`, and the Vite dev server **proxies** `/api` and `/ir` there so the browser talks to the app on port 3000 only (same-origin HTTP, no self-signed certificates).
!!! tip
Type `just` in the terminal to see other available commands.
Navigate to http://127.0.0.1:3000 and check your Tachi instance!
Navigate to http://localhost:3000 and check your Tachi instance!
## 6. OK, Now what.