Go to file
Sam e8d45ed4e9
feat(frontend): add names+pronouns to edit profile page, add robots.txt
2023-03-13 01:08:46 +01:00
backend feat(frontend): working Discord login + signup 2023-03-12 04:25:53 +01:00
frontend feat(frontend): add names+pronouns to edit profile page, add robots.txt 2023-03-13 01:08:46 +01:00
scripts feat(backend): use jsonb instead of composite type arrays 2023-03-12 01:31:10 +01:00
.gitignore chore: gitignore redis' dump.rdb 2022-11-20 15:35:23 -05:00
.prettierrc chore: clean up some stuff from the separate frontend repo 2023-03-12 05:05:43 +01:00
LICENSE initial commit 2022-05-02 17:19:37 +02:00
Makefile feat: read/write improved fields for users, read improved names/pronouns for users 2023-01-14 17:33:18 +01:00
README.md update README.md 2023-03-11 16:58:36 +01:00
go.mod feat(backend): use jsonb instead of composite type arrays 2023-03-12 01:31:10 +01:00
go.sum feat(backend): separate rate limits into buckets 2023-02-24 15:53:35 +01:00
openapi.yml docs: start writing OpenAPI definition 2022-12-12 14:18:36 +01:00
pronounscc.nginx feat: serve media on /media/, not separate domain 2022-12-22 15:42:43 +01:00

README.md

pronouns.cc

A work-in-progress site to share your names, pronouns, and other preferred terms.

Stack

  • API server is written in Go with the chi router
  • Persistent data is stored in PostgreSQL
  • Temporary data is stored in Redis
  • The frontend is written in TypeScript with Svelte, using SvelteKit for server-side rendering
  • Avatars are stored in S3-compatible storage (MinIO for development)

Development

When working on the frontend, run the API and then use pnpm dev in frontend/ for hot reloading.

Note that the Vite dev server assumes that the backend listens on :8080 and MinIO listens on :9000. If these ports differ on your development environment, you must edit vite.config.ts.

Building

Run make backend to build the API server, then run pnpm build in frontend/.

Running

Both the backend and frontend are expected to run behind a reverse proxy such as Caddy or nginx.

Every path should be proxied to the frontend, except:

  • /api/: this should be proxied to the backend, with the URL being rewritten to remove /api (for example, a request to $DOMAIN/api/v1/users/@me should be proxied to localhost:8080/v1/users/@me)
  • /media/: this should be proxied to your object storage. Make sure to rewrite /media into your storage bucket's name.

Development

Requirements:

  • Go 1.18 or later
  • PostgreSQL (any currently supported version should work)
  • Redis 6.0 or later
  • Node.js (latest version)
  • MinIO if testing uploads (not required otherwise)

Setup

  1. Create a PostgreSQL user and database (the user should own the database)
    For example: create user pronouns with password 'password'; create database pronouns with owner pronouns;
  2. Create a .env file in the repository root containing at least HMAC_KEY, DATABASE_URL, REDIS, PORT, and MINIO_ENDPOINT keys. (See below for an example)
  3. Create a .env file in the frontend/ directory containing DOMAIN=http://localhost:5173.
  4. Run make migrate to initialize the database, then optionally make seeddb to insert a test user.
  5. Run go run -v ./backend to run the backend.
  6. Create frontend/.env with the following content: API_BASE=http://localhost:8080
  7. cd into the frontend directory and run pnpm dev to run the frontend.
# Example env file
HMAC_KEY="`go run -v ./scripts/genkey`"
DATABASE_URL=postgresql://<username>:<pass>@localhost/<database> # PostgreSQL database URL
REDIS=localhost:6379
PORT=8080 # Port the API will listen on. Default is 8080, this is also default for the backend.
MINIO_ENDPOINT=localhost:9000 # This always needs to be set, it *does not* need to point to a running MinIO server.

License

Copyright (C) 2022  Sam <u1f320>

This program is free software: you can redistribute it and/or modify
it under the terms of the GNU Affero General Public License as published
by the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU Affero General Public License for more details.

You should have received a copy of the GNU Affero General Public License
along with this program.  If not, see <https://www.gnu.org/licenses/>.