this-might-be-offensive

KO | EN

gitlite — search

#react #typescript #machine-learning #linux #docker #macos #cli #kubernetes #awesome-list #pytorch #security #mcp #openai #open-source

this-might-be-offensive

(★ 32)

the stuff that makes tmbo tick

this-might-be-offensive Latest Version Download

Download Latest Version (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

This Might Be Offensive
=======================

Getting Started (Docker)
------------------------

1. Install Docker and Docker Compose
2. `git clone git@github.com:numist/this-might-be-offensive.git`
3. `cd this-might-be-offensive`
4. `./scripts/dev-setup.sh`
5. `docker compose up`
6. Point your browser to [`https://localhost/offensive`](https://localhost/offensive/) (accept the self-signed certificate warning)
7. Log in as `admin`/`[nsfw]`

To include cron jobs (for zip file creation, cleanup, and comment indexing):

```bash
docker compose --profile full up
```

**Services:**

- **nginx** - Web server (ports 80/443)
- **php** - PHP-FPM for application code
- **db** - MySQL 8.0 (exposed on port 3307 for local access)
- **redis** - Session and cache storage
- **realtime** - Node.js WebSocket server
- **cron** - Scheduled tasks (only with `--profile full`)

Getting Started (Vagrant - Legacy)
----------------------------------

1. Install vagrant and virtualbox. If you're on a Mac: `brew install Caskroom/cask/vagrant Caskroom/cask/virtualbox`
2. `git clone git@github.com:numist/this-might-be-offensive.git`
3. `cd this-might-be-offensive`
4. `vagrant up`
5. Point your browser to [`https://localhost:8080/offensive`](https://localhost:8080/offensive/)
6. Log in as either `admin`/`[nsfw]` or `asdf`/`[tmbo]`.

The codebase is installed in the vm at `~/sites/tmbo`

Common Gotchas
--------------

Realtime Data: Self-signed certs can pose a problem for realtime, but launching Chrome with `--ignore-certificate-errors` will get it working.

Hotlinking Restrictions: tmbo's content protection is the same in development as it is in production, which means if you browse to your instance by IP, you're not going to see any images. You should either disable the relevant section in the nginx config, or add the ip address you use to the allowed hosts.

Help
----

Problems with the web site are frequently well-documented by error messages emitted by trigger-error. Administrators see this output as part of the rendered page, but it is also recorded to the httpd's logs. On the VM they are located in `~/logs/`.

If you need anything to get running, help can usually be had in #tmbotech on EFnet.

this-might-be-offensive

this-might-be-offensive Latest Version Download

Today's picks

Was this content helpful?

Recent Feedback

this-might-be-offensive

this-might-be-offensive Latest Version Download

Today's picks

Was this content helpful?

Recent Feedback

Download README