brut 0.16.0.pre.pre → 0.17.0

data/docs/assets/jobs.md.Bc7Y1YpK.js

@@ -1 +0,0 @@
-import{_ as a,c as r,o as s,j as e,a as t}from"./chunks/framework.C4nOkCZI.js";const m=JSON.parse('{"title":"Background Jobs","description":"","frontmatter":{},"headers":[],"relativePath":"jobs.md","filePath":"jobs.md"}'),n={name:"jobs.md"};function i(l,o,c,d,u,p){return s(),r("div",null,[...o[0]||(o[0]=[e("h1",{id:"background-jobs",tabindex:"-1"},[t("Background Jobs "),e("a",{class:"header-anchor",href:"#background-jobs","aria-label":'Permalink to "Background Jobs"'},"​")],-1),e("p",null,"Brut provides little direct support for background jobs. Currently, Brut recommends Sidekiq, since it is battle-tested, well-supported, and open source.",-1),e("p",null,"When you set up your Brut app, it should ask if you want Sidekiq support and add the necessary configuraiton.",-1),e("p",null,[t("It will expect jobs in "),e("code",null,"app/src/back_end/jobs"),t(".")],-1),e("div",{class:"warning custom-block github-alert"},[e("p",{class:"custom-block-title"},"WARNING"),e("p",null,"The way Sidekiq is configured with Brut is effective and reliable, but it is complex. It currently involves several moving parts to make it work properly. This will be an area for improvement.")],-1)])])}const k=a(n,[["render",i]]);export{m as __pageData,k as default};

data/docs/assets/jobs.md.Bc7Y1YpK.lean.js

@@ -1 +0,0 @@
-import{_ as a,c as r,o as s,j as e,a as t}from"./chunks/framework.C4nOkCZI.js";const m=JSON.parse('{"title":"Background Jobs","description":"","frontmatter":{},"headers":[],"relativePath":"jobs.md","filePath":"jobs.md"}'),n={name:"jobs.md"};function i(l,o,c,d,u,p){return s(),r("div",null,[...o[0]||(o[0]=[e("h1",{id:"background-jobs",tabindex:"-1"},[t("Background Jobs "),e("a",{class:"header-anchor",href:"#background-jobs","aria-label":'Permalink to "Background Jobs"'},"​")],-1),e("p",null,"Brut provides little direct support for background jobs. Currently, Brut recommends Sidekiq, since it is battle-tested, well-supported, and open source.",-1),e("p",null,"When you set up your Brut app, it should ask if you want Sidekiq support and add the necessary configuraiton.",-1),e("p",null,[t("It will expect jobs in "),e("code",null,"app/src/back_end/jobs"),t(".")],-1),e("div",{class:"warning custom-block github-alert"},[e("p",{class:"custom-block-title"},"WARNING"),e("p",null,"The way Sidekiq is configured with Brut is effective and reliable, but it is complex. It currently involves several moving parts to make it work properly. This will be an area for improvement.")],-1)])])}const k=a(n,[["render",i]]);export{m as __pageData,k as default};

data/docs/assets/roadmap.md.CJsbUmK_.js

@@ -1 +0,0 @@
-import{_ as t,c as o,o as a,ag as i}from"./chunks/framework.C4nOkCZI.js";const h=JSON.parse('{"title":"Roadmap to 1.0","description":"","frontmatter":{},"headers":[],"relativePath":"roadmap.md","filePath":"roadmap.md"}'),l={name:"roadmap.md"};function r(s,e,n,d,c,m){return a(),o("div",null,[...e[0]||(e[0]=[i('<h1 id="roadmap-to-1-0" tabindex="-1">Roadmap to 1.0 <a class="header-anchor" href="#roadmap-to-1-0" aria-label="Permalink to &quot;Roadmap to 1.0&quot;">​</a></h1><p>A lot of Brut is solid, but there&#39;s several things missing from what I would call a 1.0 release. Here are some ideas of what I think is needed:</p><h2 id="better-dev-experience" tabindex="-1">Better Dev Experience <a class="header-anchor" href="#better-dev-experience" aria-label="Permalink to &quot;Better Dev Experience&quot;">​</a></h2><ul><li>The output of <code>bin/dev</code> isn&#39;t great.</li><li>otel-desktop-viewer is cool, but not the easiest to figure out issues as compred to good &#39;ole logging.</li><li>Error pages in the app are <em>really</em> bad.</li><li>CLI apps are OK, but could be fancier.</li></ul><h2 id="more-tests" tabindex="-1">More Tests <a class="header-anchor" href="#more-tests" aria-label="Permalink to &quot;More Tests&quot;">​</a></h2><ul><li>Unit tests for all/most classes are needed. There&#39;s only a few now.</li><li>Integration test of <code>mkbrut</code>, all automated.</li><li>Web component/custom element tests need to be re-thought.</li><li>Test output is a wall of text stack trace and this sucks.</li><li>Improvements in access to Playwright features.</li><li>Playright is the worst E2E testing tool except all the rest. Would love a better option here.</li></ul><h2 id="more-complete-web-features" tabindex="-1">More Complete Web Features <a class="header-anchor" href="#more-complete-web-features" aria-label="Permalink to &quot;More Complete Web Features&quot;">​</a></h2><ul><li>Content security policy doens&#39;t allow for hashes, which can be limiting in some situations. I want everyone to be running with a CSP, so it has to be configurable to some degree.</li><li>Websockets, server-push, etc. should be possible or at least have a recipe.</li><li>Learn more about importmaps.</li></ul><h2 id="client-side-improvements" tabindex="-1">Client-Side Improvements <a class="header-anchor" href="#client-side-improvements" aria-label="Permalink to &quot;Client-Side Improvements&quot;">​</a></h2><p>BrutJS is woefully incomplete. I&#39;d like developers to be able to accomplishe certain tasks without needing a framework:</p><ul><li>Hooks into asset building to e.g. enable TailwindCSS or other tools.</li><li>Better use of <code>fetch</code> in more situations</li><li>Server-generated HTML replacement</li><li>Better support for &quot;API&quot; style back-end when a framework <em>is</em> going to be used.</li></ul><h2 id="deployment" tabindex="-1">Deployment <a class="header-anchor" href="#deployment" aria-label="Permalink to &quot;Deployment&quot;">​</a></h2><p>Out of the box support for more deployment mechanism, at least:</p><ul><li>Normal Heroku/<code>Procfile</code>-based deploy</li><li>Digital Ocean-style hosting</li><li>VPS?</li></ul><h2 id="documentation" tabindex="-1">Documentation <a class="header-anchor" href="#documentation" aria-label="Permalink to &quot;Documentation&quot;">​</a></h2><ul><li>More recipes for how to do things</li><li>More complete API docs with examples</li><li>A unified look and feel across the board</li><li>Get rid of VitePress for something less client-heavy, but still great</li><li>Dash-accessible API docs</li></ul><h2 id="misc" tabindex="-1">Misc <a class="header-anchor" href="#misc" aria-label="Permalink to &quot;Misc&quot;">​</a></h2><ul><li>More direct Sidekiq support</li></ul>',18)])])}const p=t(l,[["render",r]]);export{h as __pageData,p as default};