[PT-BR]
Este commit implementa a rebranding completa do Forgejo para DATAWARE Forge, integrando as seguintes alterações:
- Atualização de mensagens, textos, variáveis e endpoints em comandos e arquivos de configuração (ex.: dump, serv, app.ini, scripts Docker, serviço systemd) para refletir a nova identidade DATAWARE Forge.
- Modificação dos nomes de temas e das referências a “Forgejo” e “Gitea” para “DATAWARE Forge” em diversos módulos, headers de API, webhooks, e testes (incluindo X-DatawareForge-OTP e X-DatawareForge-Object-Type).
- Ajustes nos modelos de usuário e configurações do sistema para reservar novos nomes (ex.: dataware-actions, DATAWARE Actions) e atualizar emails institucionais.
- Atualização do package-lock.json para refletir o novo nome do projeto.
- Inclusão e adaptação dos temas especiais de acessibilidade (para deuteranopia/protanopia e tritanopia) em light e dark modes.
- Correções diversas em mensagens de log e validações para garantir a consistência com a nova marca.
Esta atualização consolida a customização white-label para uso interno e futura distribuição a clientes, mantendo os créditos e a integridade do código original.
[EN]
This commit implements the complete rebranding from Forgejo to DATAWARE Forge, integrating the following changes:
- Updated messages, text, variables, and endpoints in commands and configuration files (e.g., dump, serv, app.ini, Docker scripts, systemd service) to reflect the new DATAWARE Forge identity.
- Modified theme names and replaced references to “Forgejo” and “Gitea” with “DATAWARE Forge” throughout various modules, API headers, webhooks, and tests (including X-DatawareForge-OTP and X-DatawareForge-Object-Type).
- Adjusted user models and system settings to reserve new names (e.g., dataware-actions, DATAWARE Actions) and update institutional email addresses.
- Updated package-lock.json to reflect the new project name.
- Added and adapted special accessibility themes (for deuteranopia/protanopia and tritanopia) in both light and dark modes.
- Various fixes in log messages and validations to ensure consistency with the new branding.
This update consolidates the white-label customization for internal use and future client distribution while preserving the original credits and code integrity.
Marcos A. Lucas <mlucas@dataware.com.br>
`http.ServeFile/ServeContent` handles `If-xxx`, `Content-Length`,
`Range` and `Etag` correctly
After this PR, storage files (eg: avatar) could be responded with
correct Content-Length.
Change all license headers to comply with REUSE specification.
Fix#16132
Co-authored-by: flynnnnnnnnnn <flynnnnnnnnnn@github>
Co-authored-by: John Olheiser <john.olheiser@gmail.com>
Why this refactor
The goal is to move most files from `models` package to `models.xxx` package. Many models depend on avatar model, so just move this first.
And the existing logic is not clear, there are too many function like `AvatarLink`, `RelAvatarLink`, `SizedRelAvatarLink`, `SizedAvatarLink`, `MakeFinalAvatarURL`, `HashedAvatarLink`, etc. This refactor make everything clear:
* user.AvatarLink()
* user.AvatarLinkWithSize(size)
* avatars.GenerateEmailAvatarFastLink(email, size)
* avatars.GenerateEmailAvatarFinalLink(email, size)
And many duplicated code are deleted in route handler, the handler and the model share the same avatar logic now.
