FossilOrigin-Name: 3f0b9969cca554540ca465095193b9d00d3c132627771b3cbdbf3d22464483e6
This commit is contained in:
me@ow.nekobit.net 2022-01-16 05:39:07 +00:00
commit 0e2c5f9e49
2 changed files with 43 additions and 0 deletions

16
Makefile Normal file
View file

@ -0,0 +1,16 @@
CC ?= cc
CFLAGS = -Wall
LDFLAGS = -lcurl
SRC = $(wildcard src/*.c)
OBJ = $(patsubst %.c,%.o,$(SRC))
TARGET = ratfe
all: $(TARGET)
$(TARGET): $(OBJ)
$(CC) -o $(TARGET) $(LDFLAGS)
$(OBJ): $(SRC)
$(CC) $(CFLAGS) -c $< -o $@
.PHONY: all

27
README.md Normal file
View file

@ -0,0 +1,27 @@
# RatFE
A pleroma frontend for rats.
The goal is to create a frontend that's lightweight enough to be viewed without JS, but
usable enough to improve the experience with JS.
RatFE uses C with FCGI, mastodont-c (another library that complements RatFE) for
communication, and plain JavaScript. It also uses sqlite3 to store any user-specific
information and groups.
## Isn't FCGI outdated?
No.
## Isn't Sqlite3 slow?
No, in fact, it may likely be faster than if it were using postgresql. The pleroma server
communicates using postgresql because there are lots of incoming requests and outgoing
requests on the server, and there can be multiple requests at once occuring, which get
queued. We don't need that kind of speed and we shouldn't interfere with it anyway.
Plus, Sqlite3 is only being used for user groups and possibly some session information.
## Rat?
Rats are c00l.