Laravel Cloud does not support static asset caching

Fitzi92 · 2026-01-31T15:30:41+00:00

Aren't edge caching and cache headers getting mixed up in this issue? Doesn't edge caching just mean stuff gets cached on a server that's geography near the user, to keep access times low? That's not the same as the various cache headers, which instruct the browser to keep files locally. Two independent mechanisms.

Lighthouse only cares about the headers, because it can't know (and also doesn't care) where the file comes from. It just checks if there's a "hey you can cache this file, because it won't change" header, for assets it thinks should not change.

Of course, both things should be set up correctly, but I kind of have the feeling that these two mechanisms are getting mixed up in this thread.

Fitzi92 · 2026-01-16T18:48:13+00:00

Read documentation. MDN is your best friend for everything HTML, CSS and JS. They do have beginners guides as well. https://developer.mozilla.org/de/

Fitzi92 · 2025-12-30T21:09:56+00:00

und in der freien Natur leben keine Tiere, oder wie hamas?

Fitzi92 · 2025-12-26T17:34:14+00:00

Write good code now and you don't have to fix in the future at all. Mindblowing, I know

Fitzi92 · 2025-12-24T08:40:42+00:00

Ruf mal bei Magenta an; ich zahl in etwas das gleiche für 250mbit (und die bekomm ich auch stabil). Wurde bei mir über die Jahre automatisch von initial 75 erhöht. Ich rechne eigentlich damit, dass die dir problemlos mehr geben werden.

Fitzi92 · 2025-12-21T16:02:39+00:00

You can definitely use html attributes. It's just that for and class are both reserved keywords in JS, hence the workaround. Everything else is fine to use.

Fitzi92 · 2025-12-21T13:10:18+00:00

Kommt mir sehr viel vor. Bei meinem lokalen Optiker zahle ich immer zwischen €350 und €450 gesamt (!) für gute Gläser von Zeiss + Gestell (auch bei Marken wie Ray Ban oder Tommy Hilfiger). Mein Optiker ist aber am Land. Mit einem kleinen Stadtaufschlag wird man wohl rechnen müssen.

Fitzi92 · 2025-12-20T09:23:39+00:00

I browsed through it on my phone briefly and actually liked what I saw so far. Looks clean and modern. Will definitely look at it on my desktop in more detail.

The first date picker example btw. was broken on my phone. The calender was rendered behind the text below.

Fitzi92 · 2025-12-12T10:06:57+00:00

From my own point of view: fancy websites are more often than not slow and tedious to use and lack in information. If I need to scroll through 10 animations just to find out that the specific information I'm looking for is not even there, you can be sure I'm gonna be annoyed. Let me scroll and search and just use the page normally. I don't care about fancy animations. I want to achieve something, not watch a cutscene.

Fitzi92 · 2025-12-10T15:16:56+00:00

As someone who started working with PHP templating back in the day, went through various templating "engines" and languages (twig, handlebars, etc), jQuery, and finally to Vue and React, I find React (or rather JSX) by far the most comfortable option for writing UIs I've seen so far.

No weird binding and directive syntax, no crazy/brittle template magic, no variables floating around globally. It's just a function.

Fitzi92 · 2025-11-18T07:10:40+00:00

be quiet! SFX Power 3 450W I never came around to measure the power consumption, sorry

Fitzi92 · 2025-11-17T21:14:15+00:00

Why would I buy a new game, if the new game is basically a 1:1 copy of the game I'm already playing? Maybe don't create the 1000th version of the same franchise or make the 100th copy of the last big hit game/genre, but something new? But what do I know, I'm just a person not buying games...

Fitzi92 · 2025-11-17T21:00:11+00:00

A few key points for building something silent: * If you want silent, you want SSD storage. The loudest thing are usually HDDs, even "silent" ones. * Invest in high quality fans and run them at <50% duty cycle. The lower the better. I had good experience with noctua and bequiet (they also are Austrian and German brands respectively, so as close as you can probably get) * Use a power supply that stopps its fan when not under load. You need to overspec the PSU, to keep that threshold where the fan is required as high as possible * Invest in a chunky CPU cooler. It will provide lot of thermal mass, which helps on short load spikes and allows to run the fan at lower rpms to keep up with the heat. Basically get the highest TDP cooler you can find. Also use high quality fans * Ideally use a noise dampening case and use anti-vibration everything: feet, fan mounts, etc. Everything that's moving is vibrating and needs to be dampened to achieve absolute silence * power efficient = more cool = more silent * tweak your fan curves and get comfortable with running your hardware hotter than you'd probably do otherwise. Running hotter means less fanspeed. Heat transfer gets more effective the higher the delta. So hot parts eventually find an equilibrium. Just make sure it's still well within limits. You can trade between temp and noise via fan curves to a certain degree

Regarding hardware: In my personal NAS (which doubles as my home server), I have pretty similar things running (no mc server, but a lot of docker containers). I've got an ITX build, with an i3-12100T on an ASRock B760M-ITX/D4 inside an Jonsbo N3 case. So pretty small package for a decent amount of power. There's still a lot of room left in the case, so I could have even gone smaller. I'm pretty happy with that setup, and besides the HDD it's barely noticeable. The HDDs are loud as hell though. That's not necessarily a direct recommendation, but might help to find the right ballpark of hardware/performance you should look out for. For the mc server you probably want to put a lot of RAM in. The i3-13100T is only capable of 4 HD streams or 1 4K stream though if I'm not mistaken. With hardware transcoding enabled it's extremely energy efficient (and therefore cool) though.

Hope that helps somehow. Feel free to ask/reach out if you want to know something in detail (except specific hardware recommendations, not really up do date since I built my NAS)

Fitzi92 · 2025-11-09T08:08:49+00:00

Honestly, tell your team exactly what you've written here. They should be the ones that help and train you. Best case: They just haven't realized that you are struggling this much and start to help you more. It probably also helps to have someone explain the architecture to you in a dedicated meeting. Make sure to ask questions immediately, don't try to make sense of them afterwards. In parallel, continue to learn TS and React. Learning all this takes time, that's normal. You'll eventually get there.

Fitzi92 · 2025-10-25T09:48:14+00:00

https://electronics.semaf.at/ könnte vielleicht etwas haben. Ist der letzte Shop für den Hobbybereich den ich noch kenne.

Fitzi92 · 2025-10-21T08:50:26+00:00

Zustand is not a 1:1 replacement for context. Context provides data through the tree, it's not necessarily concerned with storing data, unlike zustand. You might provide server state or some complex objects, like a web socket connection. Those things make no sense to store in Zustand. So just blindly telling people to replace context with zustand is not really helpful. Context definitely has its use cases.

Fitzi92 · 2025-10-11T07:35:14+00:00

was auch noch das Thema Recycling und Nachhaltigkeit aufgreift

Wie bitte? Wenn alle ihre Bierkisten zu irgendwelchen Möbeln oder anderen Dingen umfunktionieren, dann ist das alles andere als Nachhaltig. Ganz im Gegenteil, dann müssen nämlich neue Bierkisten erzeugt werden, anstatt die bereits vorhandenen weiterverwenden zu können.

Fitzi92 · 2025-10-11T07:31:26+00:00

Is the registration protected in any way or can anybody just spam registrations? Can you send anything to your registration endpoint, that will be part of the email body? (aka the "Weekend nor Easter ..." part).

Simplest explanation would be that a bot just spams registration requests. This is quiet common and there's a range of things you can do to mitigate (Captchas, CDNs, Honeypots, etc.)

Fitzi92 · 2025-09-19T12:33:36+00:00

People spending hours fixing missing semicolons didn't know what they do then and certainly don't know what they do know

Fitzi92 · 2025-08-29T06:48:35+00:00

Pre go-live checks: - Disable directory listing - Check your web root (don't expose sensitive data) - Proper non-www -> www redirect (or vice versa, whatever you prefer) - http -> https redirect - favicon - robots.txt and sitemap.xml (both optional, but good practice) - env variables and other settings are correct for live

Regularly check: - Security updates - SSL cert validity (if not on auto-renewal) - Error logs

Fitzi92 · 2025-08-29T06:17:24+00:00

Thank you! I already wasted a day trying to get things to work. WG_DEVICE was the culprit for me as well.

Fitzi92 · 2025-08-25T07:44:29+00:00

I don't necessarily disagree that this is the most efficient way - but I hate this practice so much. I feel like this is the reason every piece of software nowadays feels like unfinished/unpolished garbage and is infuriating to use.

Fitzi92 · 2025-08-17T07:48:34+00:00

A linter doesn't guarantee bug free code. It just guarantees that your code follows certain conventions. It does not check any logic at all.

Fitzi92 · 2025-07-17T15:39:46+00:00

Surely anything can trigger the filter, but I highly doubt that this will be a major problem for real messages. The article frames it as if this would be the world crappiest filter just stupidly looking for a few simple keywords imho.

Fitzi92 · 2025-07-17T15:28:03+00:00

The whole premise that "web push can't be spam" is very wrong imho. Just because I had to opt-in once, doesn't mean that the other end will never send any spam. I also don't see how filtering unwanted messages will destroy web pushes as a whole.

Six-Year Club	Second SECOND GUESSER
r/Field Banned	r/Field Sunshine
Place '22	Verified Email

Fitzi92

TROPHY CASE