MiniWeb Template
Go to file
2024-07-18 00:45:21 +02:00
docker code: entity, migration, quick migration 2023-12-21 21:07:59 +01:00
docs docs: a bit better 2024-06-01 21:07:08 +02:00
entity wip: login, auth working, still need refactoring 2024-07-16 07:27:26 +02:00
migration code: database list, get, create, and fixed migration 2024-02-16 21:40:27 +01:00
rear wip: full editing support and login of user achieved, updated minijinja to v2, htmx, hyperscript 2024-07-18 00:45:21 +02:00
rear_auth wip: full editing support and login of user achieved, updated minijinja to v2, htmx, hyperscript 2024-07-18 00:45:21 +02:00
src wip: login, auth working, still need refactoring 2024-07-16 07:27:26 +02:00
static wip: full editing support and login of user achieved, updated minijinja to v2, htmx, hyperscript 2024-07-18 00:45:21 +02:00
strinto code: strinto 2024-01-26 11:27:05 +01:00
templates wip: full editing support and login of user achieved, updated minijinja to v2, htmx, hyperscript 2024-07-18 00:45:21 +02:00
.env.sample feature: extracting admin and services to 2024-02-28 14:01:09 +01:00
.gitignore ignoring .env 2023-10-09 00:54:36 +02:00
Cargo.lock wip: full editing support and login of user achieved, updated minijinja to v2, htmx, hyperscript 2024-07-18 00:45:21 +02:00
Cargo.toml wip: full editing support and login of user achieved, updated minijinja to v2, htmx, hyperscript 2024-07-18 00:45:21 +02:00
Justfile code: database list, get, create, and fixed migration 2024-02-16 21:40:27 +01:00
NOTES.md refactor: removed unused dependencies 2024-02-28 14:40:59 +01:00
README.md fix: fixing file_repository for new dyn layout, updating readme, deleting unused From for PrimaryKeyType 2024-06-01 20:48:36 +02:00
TODOS.md wip: full editing support and login of user achieved, updated minijinja to v2, htmx, hyperscript 2024-07-18 00:45:21 +02:00

MiniWeb

Abstract

This is a biased little project, that tries to establish a basic infrastructure to build a webservice.

The main objective is to build a basic template one can quickly start developing a service with

The project aims to implement approaches as simple straight-forward over generalized multi-purpose.

It assumes that you clone the code, and adjust it from there, without keeping up to date. So this is not thought of being a framework.

Choices

Philosophies

  • Semantic over Mnemonic
  • As flat HTML as possible

On the Backend

  • axum as webserver framework
  • minijinja as template renderer
  • sea-orm as database framework

On the Frontend

  • markdown.css to provide out of the box CSS for markdown
  • hyperscript for light weight event scripting
  • htmx for service interaction
  • Fomantic-UI as default CSS framework (once Semantic)

Features

The aims of the project for now are:

  • Template Rendering with Hot-Reload
  • Static-File Serving
  • Logging
  • 404 Handler
  • 500 Handler
  • Media File Serving
  • Admin Site with Registry
  • Storage based tools (for files and cloud)
  • Database
  • Redis / KV Store

Future Ideas:

  • Direct Markdown Sites as wikiserve with the storage tools
  • static-image and media-image Service for automatic thumbnails
  • User and Role Implementation
  • Event-Bus link to RabbitMQ

Windows 10

Env if using MINGW64;

export PATH=$PATH:"/c/Program Files/PostgreSQL/12/bin"
export PQ_LIB_DIR="C:\Program Files\PostgreSQL\12\lib"

Install a postgres: choco install postgresql12 --force --params '/Password:root'

Mugshot

Mugshot of Admin

Project Structure

Root Folders

  • docker: all about docker, atm. database docker image for development.
  • docs: place for all future documentation, including this.
  • entity: crate containing database models
  • migration: crate containing database migrations
  • rear: crate containing the main library for rear
  • src: crate containing a runnable project implementing rear as a demo project
  • static: static files used by rear
  • strinto: experimental crate for an idea.
  • templates: all templates for rear-admiral.