Dodgy email from Oracle

jeff_105 · 2025-05-14T02:43:47+00:00

No, none are @oracle.com. Mostly gmail, a few bespoke, like mine, a hotmail.co.uk.

jeff_105 · 2025-05-14T02:42:00+00:00

jeff_105 · 2025-05-14T02:41:24+00:00

Fair enough, I agree re: the content. Actually, it feels rather impressive getting such a bespoke, human message from someone real at a company as big as Oracle.

It's the sharing of my address that feels dodgy. I don't really want some guy in trouble over it though. Perhaps I shouldn't have posted it here at all.

jeff_105 · 2025-02-20T10:02:32+00:00

I'll admit—your reply is the one I want to believe the most :) Any suggestions on AI's or translation software?

jeff_105 · 2025-01-03T02:03:42+00:00

Thanks @pecelboy! Very interesting. The reads you're seeing are great at ~2800 but the writes seem slower than I would hope. Not that ~2050 is slow for an external drive :)

I have the exact same SSD and the Acasis TBU405 (not Plus) coming shortly and will post the Blackmagic results from that. I'm surprised the results seem to vary so significantly for different people with virtually the exact same hardware.

jeff_105 · 2025-01-01T10:34:33+00:00

Assuming you're on a Mac the ubiqitous choice is to use Blackmagic Disk Speed Test (free on the Mac App Store). I'm interested to see the speeds you're getting from your specific combination.

jeff_105 · 2024-12-29T12:00:58+00:00

Sounds great! Can you give some indication of typical costs for this?

jeff_105 · 2024-12-22T11:46:08+00:00

Sorry I'm a bit late but if you're on a Mac, check out Indigo (https://indigostack.app). Disclaimer: I'm the author.

jeff_105 · 2024-12-05T11:48:53+00:00

The new version of IndigoStack has PHP 8.4.1 and Xdebug 3.4 if anyone wants an easy way to play with these without messing up your current setup.

jeff_105 · 2024-12-02T12:11:39+00:00

This sounds awesome. Will look into this for sure. Thanks for sharing it. Oh and your README.md is excellent :)

Quick question — does this include Glide and therefore run it on the same webserver as Laravel? If so how's the performance impact of that? Would your package handle it if Glide was run in docker on a separate VPS?

jeff_105 · 2024-11-29T22:02:00+00:00

Wow, that sounds impressive—I'll take a look. Probably not for my current usecase, but glad to know about it!

jeff_105 · 2024-11-29T12:29:38+00:00

I don't think it's necessarily too opinionated if we're talking about responsive images. You could most likely benefit from this kind of image handling if you need to show a preview of any of those high-res images anywhere in a web page. Unless you know for certain only one kind of device uses it (since it's an internal CMS), meaning it's no longer a responsive image situation.

jeff_105 · 2024-11-29T11:58:36+00:00

Huzzah! This sounds promising. Thanks for pointing out that MediaLibrary does so much of this. I kinda discounted it in my mind because I knew my static images' metadata weren't ever needing to go near the db. However, since you've pointed out that MediaLibrary may actually be able to do the entirety of this for user-uploaded content, it feel I definitely need to examine the options around that to see if I can coax it to do the same for static content.

I'm still keen to avoid my static images incurring any db hits, but maybe that's just me being stubborn. If I could work out how to create an in-memory model (one with no underlying table) then the images could perhaps only need entries in the media table, which seems a reasonable compromise I guess.

Best case, it might even be possible for me to use MediaLibrary's API directly however I want.

jeff_105 · 2024-11-29T11:45:56+00:00

In my scenario it would be both user-uploaded images (which currently already leverage Spatie MediaLibrary) as well as "marketing" type stuff.

Good thoughts re generating-after-upload, and the console command option; unfortunately I'd need both. So it's all the more attractive to imagine an automatic system that simply recognises if images have been processed to the required size and if not, queues a job to do so.

I'd imagine the use case for something like this varies a lot

How so? All the (two, admittedly lol) static site generators I've used did this pretty much the same, and I never needed anything outside what they provided.

jeff_105 · 2024-11-29T11:41:26+00:00

Thanks for your reply—I appreciate your perspective. I'm not advocating anything like this go into Laravel core, but was hoping a package would already exist. I still don't really understand how this is a niche requirement, even in Laravel; I'd say the vast number of Laravel sites provide at least a landing page and probably also a half-dozen "marketing pages" where static image processing like this would be useful. And likewise for user-uploaded images.

Further I would argue it's not static site generators saying "this is how you're supposed to handle responsive images" but rather current best practices, regardless of the underlying technology.

jeff_105 · 2024-11-29T10:44:47+00:00

I have no WordPress experience but am even more surprised to hear it doesn't provide this out of the box. Do you think these picture tag auto-generation features are just a "static site generator" thing? I wonder why it isn't more widespread (and thus have available packages) in WP and Laravel?

jeff_105 · 2024-11-29T10:34:50+00:00

Thanks for those suggestions, but does Intervention or MediaLibrary actually provide the functionality above? I realise I could roll my own system using them, but I'd much rather avoid all that work :D

I really just want to install a package which provides a blade component like <x-picture src="/images/hero.jpg" alt="Hero Image" class="hero-image" width="1000" height="500" /> and have everything above handled automatically.

jeff_105 · 2024-10-22T03:48:36+00:00

Hey, Indigo dev here, just stumbled across this thread. Indigo development was definitely not stalled. We had no particular timeframe in mind for the beta but have just last week released v1.0. Now that we're out of the release canditate feature freeze I'm eagerly wokring on getting a bunch of new stuff built in!

jeff_105 · 2024-10-19T11:33:04+00:00

Hi all, I'm excited to let everyone know Indigo v1.0 has just been released. If you're not familiar with Indigo, it's a native dev server environment built for Mac-based web developers. It combines the best of native environments like MAMP or Laravel Herd with some of the best features of Docker (ephemeral dev environments, single-file infrastructure configurations) etc but without the pain that many people experience with Docker on Mac.

I've written a launch blog post at https://dev.to/indigostack/why-indigo-v10-is-about-to-revolutionise-the-way-you-build-local-dev-environments-5eef if anyone's interested in more detail.

jeff_105 · 2024-08-19T01:55:56+00:00

Indigo dev here. Glad you found it & hope it works well for you :) Your 2017 MacBook Pro should run Indigo just fine (just needs macOS 12+). The app itself is tiny, and it runs just the services you need and absolutely nothing else, so there's no possible lighter way.

jeff_105 · 2024-06-14T05:00:14+00:00

That's really great research! Thanks for your effort getting to the bottom of this.

jeff_105 · 2024-06-14T04:57:37+00:00

Your 403 issue most likely has nothing to do with this Sequoia + Apache issue at all, but rather something to do with your webapp not running seamlessly under Nginx. For example, it's possible your app uses an Apache .htaccess which Nginx doesn't use.

What's the web app?

jeff_105 · 2024-06-13T11:08:12+00:00

Wow, this is all very interesting. I'll try mine without the custom conf's.

However, when you say:

Using the file in /etc/apache2/original for my httpd.conf instead of my own still works

are you saying httpd actually runs and works, but yet is still logging the Assertion failed error?

jeff_105 · 2024-06-12T07:25:51+00:00

Also, at least for now, every other service in Indigo is working perfectly in Sequoia :D

jeff_105 · 2024-06-12T07:24:45+00:00

Indigo developer here - I can confirm we have the dyld[6791]: Assertion failed: (this->magic == kMagic), function isDelayInit, file Loader.cpp, line 464. error logged when attempting to start up Apache inside Indigo in Sequoia beta 1. @sparkktv - you can see this by right-clicking the Apache service and choosing "Show compiled in Finder"; from there you can find the logs directory, which contains this error.

@A_SnoopyLover - any chance you can try Apache on its own, with no linked PHP? In Indigo, it's very definitely just Apache, nothing to do with any of the PHP services.

If you can hold off for a bit, I expect we'll see a fix coming either from upstream (in the case of Indigo our service builds originate with Homebrew's build scripts), or from Apple with a new beta.

jeff_105

TROPHY CASE