ea17bf3273
Two findings from one screenshot of a dead forgot-password page. The page is Gitea's own, and it will always say recovery is disabled: the SMTP details are the members area's, and Gitea is a different container with no mailer and no need for one. But every member reaches Gitea's sign-in form on the way in, and that form links to it — so the broken route is the one they find first. The theme now hides the link. Ours, which works, is /comunidad/recuperar. The footer on that page still advertised the software and its version, which proves the settings added days ago never reached the server. /srv/gitea/docker-compose.yml is a copy and nothing ever synced it: deploy-board.sh syncs the board's compose file, and the Gitea directory has been hand-made since setup. CORS, the theme, OpenID, the register button, the footer — committed, documented, never applied. The file stays valid and the container stays healthy, which is why nobody noticed. scripts/deploy-gitea.sh syncs it, restarts, and then reads the settings back out of the running container and prints them, because this session has lost three separate afternoons to settings that were accepted somewhere and read by nobody. Separately: an invitation was only ever issued when the app created the account. Make the account by hand, add the member with the box unticked, and no invitation exists and none can be made — which is exactly how somebody ended up with an account nobody knew the password to. Miembros now has "Enviar invitación" on any active member with an address, for that case and for a failed send, an expired link or a corrected address. Issuing a new token voids the old one, so a forwarded link stops working. Refused before a token is issued when there is no address, since otherwise a working invitation would be spent on one that cannot be delivered. 183 tests. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NizVpJ2dwzCbjCrTLCjeHn
118 lines
4.4 KiB
CSS
118 lines
4.4 KiB
CSS
/* Viena Latina colours for Gitea.
|
|
*
|
|
* Deltas only. scripts/gitea-theme.sh concatenates Gitea's own light theme —
|
|
* read out of the running container, so it matches the installed version — and
|
|
* then this file. Shipping the full theme instead would mean a copy of
|
|
* somebody else's stylesheet going stale in our repository, and an upgrade
|
|
* turning into a merge.
|
|
*
|
|
* Why this exists: members sign in to /comunidad/ through Gitea, so Gitea's
|
|
* sign-in form and authorize dialog are part of the journey whether or not
|
|
* anyone ever browses a repository. Unthemed, they are two dark screens in the
|
|
* middle of a cream-coloured site, and the platform stops feeling like one
|
|
* thing.
|
|
*
|
|
* The values come from themes/vienalatina/assets/css/main.css. If the brand
|
|
* colours change there, change them here too — Hugo fingerprints its CSS and
|
|
* Gitea serves this as a static file, so there is no way to share one source.
|
|
*
|
|
* Safe failure mode: anything Gitea renames is simply a declaration nobody
|
|
* reads, and that part keeps the light theme's value. The result of getting a
|
|
* variable name wrong is a corner that stays grey, not a broken page.
|
|
*/
|
|
|
|
:root {
|
|
/* Brand — #c0391c, with the darker and lighter steps Gitea expects for
|
|
hover, active and focus states. */
|
|
--color-primary: #c0391c;
|
|
--color-primary-contrast: #ffffff;
|
|
--color-primary-dark-1: #ad331a;
|
|
--color-primary-dark-2: #9a2a0f;
|
|
--color-primary-dark-3: #86240d;
|
|
--color-primary-dark-4: #731f0b;
|
|
--color-primary-dark-5: #5f1a09;
|
|
--color-primary-dark-6: #4c1507;
|
|
--color-primary-dark-7: #380f05;
|
|
--color-primary-light-1: #cd5137;
|
|
--color-primary-light-2: #d66a53;
|
|
--color-primary-light-3: #de836f;
|
|
--color-primary-light-4: #e69c8b;
|
|
--color-primary-light-5: #eeb5a7;
|
|
--color-primary-light-6: #f6cec3;
|
|
--color-primary-light-7: #fbe2db;
|
|
--color-primary-alpha-10: #c0391c1a;
|
|
--color-primary-alpha-20: #c0391c33;
|
|
--color-primary-alpha-30: #c0391c4d;
|
|
--color-primary-alpha-40: #c0391c66;
|
|
--color-primary-alpha-50: #c0391c80;
|
|
--color-primary-alpha-60: #c0391c99;
|
|
--color-primary-alpha-70: #c0391cb3;
|
|
--color-primary-alpha-80: #c0391ccc;
|
|
--color-primary-alpha-90: #c0391ce6;
|
|
--color-primary-hover: #ad331a;
|
|
--color-primary-active: #9a2a0f;
|
|
|
|
/* Page and panels — the site's cream background and white cards. */
|
|
--color-body: #f8f3ef;
|
|
--color-box-body: #ffffff;
|
|
--color-box-body-highlight: #fdf1ed;
|
|
--color-box-header: #f2ebe6;
|
|
--color-secondary-bg: #f2ebe6;
|
|
--color-menu: #ffffff;
|
|
--color-card: #ffffff;
|
|
--color-markup-code-block: #f2ebe6;
|
|
|
|
/* Type — the same near-black and muted brown the site uses. */
|
|
--color-text: #1a0d09;
|
|
--color-text-dark: #1a0d09;
|
|
--color-text-light: #5c3d37;
|
|
--color-text-light-1: #6b4a43;
|
|
--color-text-light-2: #7d5a52;
|
|
--color-text-light-3: #9a7870;
|
|
|
|
/* Borders — warm rather than the default neutral grey, which is most of
|
|
what makes an unthemed Gitea read as "a different website". */
|
|
--color-secondary: #e0cec8;
|
|
--color-secondary-dark-1: #d3bdb6;
|
|
--color-secondary-light-1: #ebdcd7;
|
|
--color-light-border: #e0cec8;
|
|
--color-input-border: #c2a89f;
|
|
--color-input-background: #ffffff;
|
|
--color-input-text: #1a0d09;
|
|
|
|
/* The top bar, which is the first thing anyone sees. */
|
|
--color-nav-bg: #ffffff;
|
|
--color-nav-hover-bg: #fdf1ed;
|
|
--color-nav-text: #1a0d09;
|
|
--color-header-wrapper: #ffffff;
|
|
--color-footer: #f8f3ef;
|
|
|
|
--color-accent: #c0391c;
|
|
--color-small-accent: #fbe2db;
|
|
}
|
|
|
|
/* The wordmark is wide, unlike Gitea's square cup, so it needs room. */
|
|
.logo {
|
|
height: 26px !important;
|
|
width: auto !important;
|
|
}
|
|
|
|
/* The dead "Forgot password?" link on the sign-in form.
|
|
*
|
|
* It goes to /user/forgot_password, which answers "Account recovery is
|
|
* disabled because no email is set up" and always will: the SMTP details live
|
|
* in the members area's environment, and this is a different container that
|
|
* has no mailer and does not need one. Recovery is at
|
|
* vienalatina.com/comunidad/recuperar instead, which works.
|
|
*
|
|
* Every member who forgets a password reaches the sign-in form first, so
|
|
* leaving the link there means the broken route is the one they find. Hidden
|
|
* in CSS rather than by overriding the template, because a replaced template
|
|
* has to be re-checked against every Gitea release, whereas an attribute
|
|
* selector that stops matching leaves the link visible — the state we are in
|
|
* today, not a broken page.
|
|
*/
|
|
a[href$="/user/forgot_password"] {
|
|
display: none !important;
|
|
}
|