the whitespace/margin issue exists on the per-app page in upaas too. increase its width by 50%. also double the height of the build log and the container log. move the build log to between "webhook url" and "environment variables" sections. put the container log above the deploy key.
("the whitespace/margin issue": on a big landscape monitor the page's content column is narrow, with large empty margins on both sides; filed for webhooker as sneak/webhooker#350.)
Definition of done, on an app's page:
The content container is 50% wider on large screens than today (the PR states the old and new maximum widths); at phone width nothing changes and there is no horizontal scrolling.
The build log and the container log boxes are each twice as tall as today.
The build log section sits between the "Webhook URL" and "Environment Variables" sections.
The container log section sits directly above the deploy key section.
Everything else on the page keeps its order and behaviour.
A browser check (headless Chrome at 1920 pixels and at phone width) confirms the width, heights and order.
Model: opus-5-5
sneak, 2026-09-29 in chat (verbatim):
> the whitespace/margin issue exists on the per-app page in upaas too. increase its width by 50%. also double the height of the build log and the container log. move the build log to between "webhook url" and "environment variables" sections. put the container log above the deploy key.
("the whitespace/margin issue": on a big landscape monitor the page's content column is narrow, with large empty margins on both sides; filed for webhooker as https://git.eeqj.de/sneak/webhooker/issues/350.)
Definition of done, on an app's page:
- The content container is 50% wider on large screens than today (the PR states the old and new maximum widths); at phone width nothing changes and there is no horizontal scrolling.
- The build log and the container log boxes are each twice as tall as today.
- The build log section sits between the "Webhook URL" and "Environment Variables" sections.
- The container log section sits directly above the deploy key section.
- Everything else on the page keeps its order and behaviour.
- A browser check (headless Chrome at 1920 pixels and at phone width) confirms the width, heights and order.
Model: opus-5-5
clawbot
self-assigned this 2026-09-29 12:13:19 +02:00
Plan. This runs after #243 lands on next, because both edit templates/app_detail.html.
Everything is in templates/app_detail.html:
Width: the page's <main> is max-w-4xl (56rem, 896px). Make it 84rem (1344px). static/css/tailwind.css is committed, has no build step in the repo, and has no class for 84rem. So set it inline (style="max-width: 84rem"), the same way the log boxes set their height, and drop max-w-4xl. px-4 and mx-auto stay, so phone width is unchanged. The site header in base.html stays as it is; other pages are not part of this issue.
Heights: the two log boxes (containerLogsWrapper, buildLogsWrapper) have max-height: 400px. Make both 800px.
Order: move the "Last Deployment Build Logs" section to between "Webhook URL" and "Environment Variables". Move the "Container Logs" section to directly above "Deploy Key". Move each section whole, with its Alpine bindings and x-refs unchanged. Nothing else moves.
Tests: a handler test that renders the page checks the new section order and the two heights.
Browser check, as a disclosure line with no screenshots or logs: headless Chrome in a throwaway container, at 1920 px wide and at 390 px wide, confirms the width, the heights, the order, and no horizontal scroll at phone width. Remove the container afterwards.
Model: opus-5-5
Plan. This runs after https://git.eeqj.de/sneak/upaas/pulls/243 lands on `next`, because both edit `templates/app_detail.html`.
Everything is in `templates/app_detail.html`:
- Width: the page's `<main>` is `max-w-4xl` (56rem, 896px). Make it 84rem (1344px). `static/css/tailwind.css` is committed, has no build step in the repo, and has no class for 84rem. So set it inline (`style="max-width: 84rem"`), the same way the log boxes set their height, and drop `max-w-4xl`. `px-4` and `mx-auto` stay, so phone width is unchanged. The site header in `base.html` stays as it is; other pages are not part of this issue.
- Heights: the two log boxes (`containerLogsWrapper`, `buildLogsWrapper`) have `max-height: 400px`. Make both 800px.
- Order: move the "Last Deployment Build Logs" section to between "Webhook URL" and "Environment Variables". Move the "Container Logs" section to directly above "Deploy Key". Move each section whole, with its Alpine bindings and `x-ref`s unchanged. Nothing else moves.
- Tests: a handler test that renders the page checks the new section order and the two heights.
- Browser check, as a disclosure line with no screenshots or logs: headless Chrome in a throwaway container, at 1920 px wide and at 390 px wide, confirms the width, the heights, the order, and no horizontal scroll at phone width. Remove the container afterwards.
Model: opus-5-5
Built in #247: the app page is at most 84rem wide instead of 56rem, both log boxes are 800px tall instead of 400px, the build log sits between the webhook URL and the environment variables, and the container log sits directly above the deploy key.
Model: opus-5-5
Built in https://git.eeqj.de/sneak/upaas/pulls/247: the app page is at most 84rem wide instead of 56rem, both log boxes are 800px tall instead of 400px, the build log sits between the webhook URL and the environment variables, and the container log sits directly above the deploy key.
Model: opus-5-5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
sneak, 2026-09-29 in chat (verbatim):
("the whitespace/margin issue": on a big landscape monitor the page's content column is narrow, with large empty margins on both sides; filed for webhooker as sneak/webhooker#350.)
Definition of done, on an app's page:
Model: opus-5-5
Plan. This runs after #243 lands on
next, because both edittemplates/app_detail.html.Everything is in
templates/app_detail.html:<main>ismax-w-4xl(56rem, 896px). Make it 84rem (1344px).static/css/tailwind.cssis committed, has no build step in the repo, and has no class for 84rem. So set it inline (style="max-width: 84rem"), the same way the log boxes set their height, and dropmax-w-4xl.px-4andmx-autostay, so phone width is unchanged. The site header inbase.htmlstays as it is; other pages are not part of this issue.containerLogsWrapper,buildLogsWrapper) havemax-height: 400px. Make both 800px.x-refs unchanged. Nothing else moves.Model: opus-5-5
Built in #247: the app page is at most 84rem wide instead of 56rem, both log boxes are 800px tall instead of 400px, the build log sits between the webhook URL and the environment variables, and the container log sits directly above the deploy key.
Model: opus-5-5