))
اشتراک گذاری
A quick update on this glorious hump day, just in time before I head out to the Atlanta PHP meetup (https://phpxatl.com). Tomorrow, May 21st at 11:30am EDT I’ll be chatting with Brian Casel (https://briancasel.com) about his recent launch of Instrumental Components (https://instrumental.dev). Join us in the stream and if you have any questions for Brian or myself you can get them answered live! Subscribe and join the stream: https://youtube.com/live/LyMjPhkHk3k I am also going to be streaming to https://stream.place, a new streaming platform geared towards the Bluesky/ATProto community. So it should be fun adding another destination to consume the stream from. And, I floated the idea out on LinkedIn to see if people would be interested in watching the stream there, but just waiting to see if I can get a good signal from there or not to justify adding it. Weigh-in on the LinkedIn stream: https://www.linkedin.com/posts/ryanhefner_jam-session-launching-instrumentaldev-activity-7331038582549147650-CmcP So, with that said, hopefully you can find the stream wherever you prefer to consumer your streaming content and we look forward to seeing you there. And, on the Starter Packs front, https://www.starterpacks.net, I ended up getting a pretty big hosting bill last month that would make the project unsustainable if it were that high moving forward, so in an attempt to reduce costs, and because I was meaning to explore it anyways to make navigating the site potentially faster, I converted all `/profile/...` pages to use ISR (Incremental Static Regeneration). My hope is that by rendering and caching these pages indefinitely, I will serve more cached versions of the pages and reduce some of the edge requests and function invocations previously required to serve those pages. It does introduce some complexity when it comes to revalidating those pages in the future, but this is just a means to try to cap costs, and if it works I can figure out how to keep everything fresh, while still being optimized. So stay tuned... Other links: https://www.skylounge.social https://www.linkedin.com/in/ryanhefner To follow along, you can find me at https://www.ryanhefner.com, follow me on Bluesky @ryanhefner.com (https://bsky.app/profile/ryanhefner.com) and keep up with the show on https://www.allplay.fm and @allplay.fm (https://bsky.app/profile/allplay.fm). Help yourself, while supporting the show, by trying some of the services that I use, and highly recommend: Transistor FM (https://transistor.fm/?via=allplay) Fathom Analytics (https://usefathom.com/ref/EKONBS) #buildinpublic #podcast #startups #webdevelopment #webdesign #bluesky #indiedev #bootstrapping #indiehackers…
001 — Default to Stacktion
Manage episode 416787686 series 3572783
محتوای ارائه شده توسط Ryan Hefner. تمام محتوای پادکست شامل قسمت‌ها، گرافیک‌ها و توضیحات پادکست مستقیماً توسط Ryan Hefner یا شریک پلتفرم پادکست آن‌ها آپلود و ارائه می‌شوند. اگر فکر می‌کنید شخصی بدون اجازه شما از اثر دارای حق نسخه‌برداری شما استفاده می‌کند، می‌توانید روندی که در اینجا شرح داده شده است را دنبال کنید.https://fa.player.fm/legal
On this episodes I dig into getting back into action and picking a stack to base the action on. In the past, I have built my products and prototypes in Laravel, using an SPA—typically built in React—for the majority of stuff, and I go into all the pros, and a few of the cons, I have experienced with that setup along the way.
Well, now the year is 2024 and as easy as it would be go back to that trusty old cocktail of sorts, I want to push myself to explore something new. I go into how I have been structuring my latest work utilizing Nx for the monorepo setup, and primarily using React + Next for the majority of the client apps.
I love the DX surrounding some of these newer hosting platforms, allowing for instant previews of branches that are in the works, and being able to have as many of those up and running, and viewable, while working on a project. That coupled with the fact that I haven't been working on PHP for the last 4+ years and all the changes that have been going on, in both PHP and Laravel, I feel a little behind the curve in that ecosystem, and honestly I really just like working in Javascript and not having to deal with the context switching between PHP and Javascript.
So, with all that said, I am not wasting any more time on the debate and am going to go all-in—at least on this first project—on the all Javascript setup, utilizing Nx to manage the monorepo for the project. React + Next for both the marketing site and app, which will be two separate apps deployed on the same push, utilizing shared libraries within the repo. And, will be trying out NestJS for the API, because—for a number of reasons—I think that is the way to go vs. utilizing API routes via Next to try to accomplish the external API.
References
- Laravel
- Stripe
- Lemon Squeezy
- Paddle
- Laravel Pulse (the one I couldn't think of)
- Laravel Reverb
- Next
- Vercel
- Render
- Netlify
- Laravel Shift
- Nx
- NestJS
To follow along, you can find me at ryanhefner.com, follow me on Twitter @ryanhefner, and keep up with the show on allplay.fm and onTwitter @allplayfm.
Help yourself, while supporting the show, by trying some of the services that I use, and highly recommend:
Transistor FM
Fathom Analytics
35 قسمت
))
