litter again, now in Go as a PWA --- a microblogging service without notifications and pesky messaging, just a raw mind flow

read more (a blog post)

backend/

• files related to REST API backend service, this API server is used by WASM client for fetching of app's data

config

• configuration procedures for various litter module packages

data/

• sample data files used to flush existing container data by make flush

frontend/

• app pages' files sorted by their name(s)

models

• various model declarations

web/

• static web files, logos, manifest

.env/.env.example

• environmental contants/vars for the app to run smoothly (in Docker)

http_server.go

• init app file for the app's backend side with REST API service

wasm_client.go

• lightened version of HTTP server, includes basic app router, lacks REST API service

• each user has to register (/register) and login (/login) to app for them to use it
• user is then logged-in and navigated to the flow (/flow) page when one can read other's mind flows
• user can change their passphrase or the about description on the settings (/settings) page
• any signed (by logged user) post can be written and sent by the post (/post) page
• user can logout too by navigating themselves to the logout (/logout) page

• toggable end-to-end encryption (JSON/octet-stream REST API and LocalStorage for service worker)
• in-memory runtime caches
• data persistence at container restart (on SIGINT)
• flow posts filtering using the FlowList --- simply choose whose posts to show
• can run offline (no data can be fetched from the server though)

• the service is reachable via (/api) endpoint (API auth-wall to be implemented)
• there are three main endpoints:

POST   /api/auth

POST   /api/flow
GET    /api/flow
PUT    /api/flow
DELETE /api/flow/:key

POST   /api/polls
GET    /api/polls
PUT    /api/polls
DELETE /api/polls/:key

POST   /api/users
GET    /api/users
PUT    /api/users
DE"ETE /api/users/:key

# create environmental file copy and modify it
cp .env.example .env
vi .env

# build docker image (Docker engine is needed)
make build

# run docker-compose stack, start up the stack
make run

# Makefile helper print
make info

# flush app data --- copy empty files from 'data/' to the container
make flush kill run

litter-backend container can be run locally on any dev machine (with Docker engine, or with the required tag-locked Go runtime)

make fmt build run

http://localhost:8093/flow

• implement infinite scroll for flow
• implement sessions (SessionsCache)
• implement custom logger goroutine
• healthcheck as a periodic cache dumper
• allow emojis in usernames?
• show offline mode notice
• swagger docs
• implement picture posting

• implement polls (create poll, voting)

• implement stats
• ensure system user unregisterable by the app logic (not hardcoded)
  • define data/users.json system users (regular users, but simply taken already by the init time)

• implement functional flowList editting via UI
• implement functional filtering using flowList
• fix dynamic stargazing and post deletion

• fix settings (broken pwd and about text change)
• fix register when given user exists already

• stabilize database (implement in-memory caches)
• fix layout (unwanted less-data page scrolling
• dump data on container restart/SIGINT

• use local JSON storage
• implement backend.authUser
• functional user login/logout
• functional settings page
• functional add/remove flow user

• Go backend (BE) --- server-side
• connect frontend (FE) to BE
• application logic --- functional pages' inputs, buttons, lists (flow, users)