| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
Embed the css directory alongside the templates and serve it with a
FileServerFS mounted on GET /css/. The directory name matches the url
prefix, so the file resolves without an fs.Sub and there is no error
path to handle. Adding js later is the same one line.
Cover the route in the handler tests, including that template sources
stay unreachable and that the href the home page emits resolves to a
file that is actually served.
|
| |
|
|
|
|
|
|
|
| |
Cover the defaults/system/user cascade, partial overrides, malformed
files and base-url validation, plus DefaultPath resolution. An empty
value in an ini file counts as unset, so that is pinned down too.
Add the first handlers tests: routing, the instance name reaching the
template, and escaping of operator-supplied config in the page.
|
| |
|
|
|
|
|
|
|
|
|
| |
Replace the hardcoded server.Config with an ini-backed config package
that reads /etc/openstore/openstore.conf then the user's config file, so
user settings override system ones and both override the built-in
defaults. Missing files are ignored rather than fatal.
Move route registration into a handlers package that owns the templates
and builds a Page view model, which removes the server -> handlers
import cycle along with the setter-based context injection.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
