DESCRIPTION
<BASE_DIR>/forge.example.com/:
This directory contains all data related to a particular forge instance running
at forge.example.com
<BASE_DIR>/forge.example.com/forgeinfo:
This file contains metadata pertaining to a forge.
The file format and file name is left to the discretion of the
implementer.
<BASE_DIR>/forge.example.com/john/:
This directory contains all data related to a user named "john"
on forge instance at forge.example.com.
<BASE_DIR>/forge.example.com/john/userinfo:
This file contains all metadata related to a user named "john"
on forge instance at forge.example.com.
The file format and file name is left to the discretion of the
implementer.
<BASE_DIR>/forge.example.com/john/repo-foo/:
This directory contains all data related to a repository named
"repo-foo" owned by user "john" on forge instance at
forge.example.com.
<BASE_DIR>/forge.example.com/john/repo-foo/repo-info:
This file contains all metadata related to a repository named
"repo-foo" owned by user "john" on forge instance at
forge.example.com.
The file format and file name is left to the discretion of the
implementer.
DESCRIPTION
add_user
Adds new user to DB. Implementers must ensure username
uniqueness scoped at forge instance level. When applicable, HTML
link to profile photo may be stored as we..
user_exists
Checks if a user exists in database. Optionally provide hostname
of forge instance to get forge-specific results.
SUMMARY
sqlite caused problems(panic) when trying to break its database URL
when trying to break it down into host, protocol, path and port,
etc. with crate::settings;:DatabaseBuilder. Bypassing
DatabaseBuilder and directly setting crate::settings::Database.url,
fixes this issue.
