modules/

Details

Valid go.mod file

The Go module system was introduced in Go 1.11 and is the official dependency management solution for Go.
Redistributable license

Redistributable licenses place minimal restrictions on how software can be used, modified, and redistributed.
Tagged version

Modules with tagged versions give importers more predictable builds.
Stable version

When a project reaches major version v1 it is considered stable.
Learn more about best practices

Repository

gitee.com/vonway/leanote

README ¶

modules

Set of officially supported modules for Revel applications

Caution

this is a work in progress

Directories ¶

Path	Synopsis
auth A basic user authentication module for Revel list of concerns: - Separating out the interface and driver - Removing DB/Storage dependency - UUID as default identifier? - how to deal with password/secret or generally, method of authorization - default {views,controllers,routes} for register/login/logut ? - reset password in most basic ? - activation (and other features) in a second / more sophisticated driver - filter for checking that user is authenticated I think a driver is made up of 2 parts data prep and data storage register and password reset are part of data prep as is the auth hash method they don't care how the data is stored then there is the data store perhaps each auth user model should instantiate 2 drivers instead of 1? one for data prep components and one for storage so the security driver and the storage driver	A basic user authentication module for Revel list of concerns: - Separating out the interface and driver - Removing DB/Storage dependency - UUID as default identifier? - how to deal with password/secret or generally, method of authorization - default {views,controllers,routes} for register/login/logut ? - reset password in most basic ? - activation (and other features) in a second / more sophisticated driver - filter for checking that user is authenticated I think a driver is made up of 2 parts data prep and data storage register and password reset are part of data prep as is the auth hash method they don't care how the data is stored then there is the data store perhaps each auth user model should instantiate 2 drivers instead of 1? one for data prep components and one for storage so the security driver and the storage driver
driver/secret
csrf
app
db
app This module configures a database connection for the application.	This module configures a database connection for the application.
jobs
app/controllers
app/jobs A job runner for executing scheduled or ad-hoc tasks asynchronously from HTTP requests.	A job runner for executing scheduled or ad-hoc tasks asynchronously from HTTP requests.
pprof
app/controllers
static
app/controllers
testrunner
app
app/controllers

?	: This menu
/	: Search site
f or F	: Jump to
y or Y	: Canonical URL