You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
And many people think it is an error, and that something went wrong during the installation. We should either set it during the setup with the .env, or use a custom Rocket config from Rust code.
Plume version (and/or commit): 0.2.0
The text was updated successfully, but these errors were encountered:
Actually, I would like to use askama for templates in the future, which would make it harder to put them in their own repository… However, theming with some CSS could be allowed in the future too.
Maybe we could still put them in another repository and "load" them with a git submodule (So if you want custom templates, you would clone Plume without the submodule, then clone in the template dir (or whatever) the repo of the theme we want…)
Actually, I would like to use askama for templates in the future, which would make it harder to put them in their own repository… However, theming with some CSS could be allowed in the future too.
Templates are embedded in the binary with askama, they are not read from the file system when the app starts. So if you want to change them you should recompile the whole app (well actually it's true that's it is not more complicated, only a bit longer).
At each launch, Rocket tells us:
And many people think it is an error, and that something went wrong during the installation. We should either set it during the setup with the
.env
, or use a custom Rocket config from Rust code.Plume version (and/or commit): 0.2.0
The text was updated successfully, but these errors were encountered: