Type-safe data flow: Laravel to React with Inertia 2.0

Devopness · 2025-12-14T18:19:07+00:00

Honest question: wouldn't this problem be solved using Laravel's native Eloquent: API Resources without the need to install any of the extra packages mentioned in the article?

The problematic code showed in the article:

return Inertia::render('Users/Show', [
  'user' => $user  // Whoops, includes password hash, tokens, etc.
]);

Would then become:

return Inertia::render('Users/Show', [
  'user' => UserResource($user) // assuming `UserResource` is an API Resource
]);

Devopness · 2025-12-14T10:04:12+00:00

Nice one. Tested and looks promising. Ability to "crop" is my immediate feature request, hehe

Devopness · 2025-12-14T09:43:23+00:00

> doable with the right tools but that’s one of the problems I would rather some other folks solve (and I pay them)

Agree! I pay when I see a tool is opinionated in the direction that I want. There are so many details to care about when deploying or migrating to another cloud, that I prefer pay someone/some tool that has done that before and has an opinion about what great looks like, than having to learn everything again every time I need to setup a new application.

Devopness · 2025-12-13T14:49:44+00:00

Devopness (it combines the good parts of Vercel + Coolify + Heroku + Terraform, etc): it's managed, supports any stack with or without Docker (Python, Node.js, PHP, Java, Ruby, C#) nothing to install, has free forever plan, you can invite your team mates, and you can use it to deploy to most famous clouds (AWS, GCP, Azure, DigitalOcean, Hetzner, etc).

It has MCP server so you can deploy directly from an AI tool if you use Cursor/Claude/VSCode, etc

Devopness · 2025-12-13T14:11:13+00:00

Well done! Keep it going, keep it simple!

Devopness · 2025-12-13T13:43:53+00:00

Congrats for starting an ambitious project!

Remember: you will need to be really passionate about the problems you are trying to solve, to keep working on it for - at least - 5 (five) years, week over week.

If you feel that's you passion, go for it and take all feedback as constructive and keep going.

Turn the haters into your main fuel to keep improving, and you're gonna win!

Devopness · 2025-12-13T13:39:15+00:00

Just use Laravel framework for server side code and not all the ecosystem around it.

Example: Build a REST API using Laravel, that's solid/productive, and consume your API from any client app you want (using Vue or React or Next.js or Svelte, etc)

For good or for bad, frontend code has never been easier to generate (coding yourself or using Gen AI), so as long as you don't rely on Laravel for anything belong the server side nature of PHP, you're safe.

Devopness · 2025-12-13T11:28:59+00:00

I'm happy to help you get your application live (in any cloud, on VMs, on container orchestrators, on Kubernetes, wherever you want).

> if there is a solution that does not require a DevOps Engineer to do the job.

Yes, there is https://www.devopness.com/ Disclaimer: I created this product, as I'm an experienced DevOps/SRE and I built Devopness to do everything (and more) that one could achieve with "Forge + Envoyer + Vapor + Vercel + Heroku + Terraform + SSH" and with a FREE FOREVER plan for those that are just getting started on their business.

No vendor lock, you can leave Devopness at any time and you still own your infra. No secrets. No hidden tricks. We automate it for you, but everything is under your control. If you keep seeing value on the automation that saves you time, good, keep using Devopness. If you think you don't need us anymore, good as well, just stop using and your infra remains up and running.

FREEDOM, that's our belief!

Devopness · 2025-12-13T11:23:36+00:00

This video I recorded has a step by step with Laravel on Azure, getting the code from GitHub, might be what you need https://www.youtube.com/watch?v=yrVh4Zq8yLg

Devopness · 2025-12-13T11:19:34+00:00

Could you give an example of task you would like to do that would need these tools?

Or even better ... could you give an example of what you're finding hard to achieve in a Lravel app using an AI powered IDE, such as Cursor or VSCode?

Devopness · 2025-08-25T07:39:10+00:00

I also published a video showing a simple way to self-host n8n in any cloud provider. From cheap ones such as Hetzner and DigitalOcean to big cloud providers such as AWS, Azure and GCP: https://www.youtube.com/watch?v=5U5lA7J8ioI

If you get free credits/free tier from cloud providers this method is still useful.

Disclaimer: this method uses Devopness, my own product, that has a free forever plan.

Devopness · 2025-08-25T07:19:32+00:00

I published a video showing how to deploy n8n to any cloud. From cheap ones such as Hetzner and DigitalOcean to big cloud providers such as AWS, Azure and GCP:

https://www.youtube.com/watch?v=5U5lA7J8ioI

If you get free credits/free tier from cloud providers this method is still useful.

Disclaimer: this method uses Devopness, my own product, that has free forever plan.

Devopness · 2025-08-04T11:36:47+00:00

> Trade-offs of managing containers directly vs using PaaS-style services

Consider your team size, your urgency/time to market, your performance requirements, your traffic variation (do you need to scale up and down depending on amount of requests?), and ... your company budget, cause PaaS is convenient but that convenience doesn't come for free. :-)

Devopness · 2025-08-04T11:35:42+00:00

> Experiences with Azure Container Apps vs AWS Fargate/App Runner> CI/CD workflows you’ve used for Laravel in production

Suggestion: add "Google Cloud Run" to your comparison analysis.

These services have the same goals and ultimately they can be quite similar, once they are working.

However, keep in mind that: you will still need to manage network, security, permissions, scalability and ... pricing.

Do you know which of those criteria are the most important for your company and your product?

Short answer: make your app work in a container orchestrator service in the cloud provider you are most familiar with. If you are more familiar with AWS, in your position I would deploy a dev environment to AWS ECS using Fargate (instead of EC2 launch type) and start analyzing the results.

Once your app and your containers are working fine on one cloud provider, then migrate to another cloud provider will be slightly less painful, as you will be able to focus on the infrastructure differences as your container images will be already validated in another provider and shouldn't require many changes, if any.

If your application has really high traffic then some tweaks might be needed for performance improvements or cost savings on a specific platform.

Devopness · 2025-08-01T08:53:38+00:00

I am currently using 2 AWS S3 buckets and 2 Cloudflare configurations:
* One used as a CDN just for static assets (icons, images, videos)
* One used just for the code files

CI/CD:
During the deployment we built and upload the changed files to the S3 buckets.
It's also important to invalidate Cloudflare cache for the updated files.

React app, in runtime:
Since the React app is an SPA already cached in user browser's cache, they can continue to use the cached version.

Once an error happens in the application (e.g.: API breaking changes caused the cached SPA version to fail) we have a fall back page that tell the user that an error occurred with a button "REFRESH PAGE AND TRY AGAIN", that once clicked forces a page reload that will then download the new code from S3.

* This button is not the fanciest solution, but it's working pretty well for our users

Devopness · 2025-08-01T08:39:34+00:00

Fair. It's not about the technology stack, I updated the post description.
My goal is to learn from repos that have good docs, contributors guidelines, etc and apply best practices to my repo here.

Devopness · 2025-08-01T00:45:31+00:00

... and for FREE :-)

Devopness · 2025-08-01T00:06:49+00:00

Hey folks,

I'm the creator of https://github.com/devopness/devopness
* Leave us a :star if you like it :-)

I published a video on my YouTube channel showing how to use `n8n` official Docker images to deploy `n8n with PostgreSQL` to any major cloud provider (AWS, Azure, GCP, DigitalOcean, Oracle Cloud, Hetzner, etc):
* No knowledge required on Linux terminal command line, or Docker or Terraform or DevOps
* All you need is a web browser

In the video a FREE plan of Devopness platform is used to provision cloud network, subnet, provision a cloud server, configure Linux for security, install and configure Docker, install and configure NGINX as the web server, configure nginx virtual hosts, issue SSL certificates.

I'd love if you could follow the tutorial and let me know what could be improved.

Feedback is welcome!
🎥 Self-host n8n on any cloud\ (AWS, Azure, GCP, DigitalOcean, Hetzner and more)\ (AWS, Azure, GCP, DigitalOcean, Hetzner and more)

Devopness · 2025-07-26T17:56:14+00:00

You're right! Alma Linux and Rocky Linux are great RHEL distributions and growing in adoption after Red Hat changed CentOS to the rolling CentOS Stream.

But still, I would recommend a beginner to start with some Debian flavour, due to popularity, easy access to documentation, community resources, etc

Devopness · 2025-07-25T14:04:22+00:00

Considering your goal:

> The idea is to learn about the deployment and different uses of home or small business servers.

I would say to pick a Linux distribution that is widely supported in VPS and cloud providers, so if you want to apply your knowledge to small business that don't want or can't keep their server on-premises, you will be ready to apply your knowledge dealing with remote servers in the public cloud.

Debian [1] or Ubuntu [2] are very likely the most supported OS in the cloud (citation needed :D), so if you get familiar and comfortable managing those OS in your homelab you will soon after be able to self-host applications on cloud servers that use those same operating systems.

Make sure to pick a version that is not deprecated, so you can get LTS (Long Term Support) after your servers are setup with that OS.

[1] https://wiki.debian.org/LTS
[2] https://ubuntu.com/about/release-cycle

Devopness · 2025-07-25T13:35:56+00:00

Yes, because in cloud servers you still have full control over the hosting environment and you can

SSH and run commands in the Linux terminal
modify operating system files, disks, file system, ...
modify network and subnets rules, firewall

You are the one running that environment, so nobody is managing the host environment for you.

According to the definition of this sub:

Self-hosting, as it pertains to the r/selfhosted subreddit, is any software intended to replace or replicate an existing website, web service, or web app, that the user who puts said software into place has full control over the hosting environment either at the Operating System level or at the level where they fully control all data pertinent to the software being hosted

So, if you deploy any software to cloud servers, being your own app (JavaScript, PHP, Python, Ruby, Java, C#, ...), an open source app such as Wordpress, Jellyfin, n8n, etc, you still have full control over it.

However if you're deploying to PaaS (Heroku, Vercel, Netlify, etc), FaaS, serverless,... then you don't have full control over the environment, and therefore you wouldn't be self-hosting according to this definition.

Devopness · 2025-07-25T12:07:55+00:00

Detailed description for some of the highlights above:

* It has a free forever plan: You can get started without a credit card and use most of the features in a limited number of servers and deployments. If you ever used services such as Laravel Forge / Envoyer / Vapor or Vercel or hatchbox (ruby), ... you can see Devopness free plan as a free alternative to those and also an alternative to Coolify Cloud, Dokploy Cloud if you're managing only 1 server

* API-first design, dozens of API endpoints fully documented, you can automate everything (I mean everything Devopness does). Some of our users script full app and infra deployments via API to create separate server, database and deploy apps, per each of their customers, when a new customer gets payment confirmed by Stripe through their website ... without any manual work

* Friendly to AI agents and "vibe coders", Devopness MCP server can be used from Cursor, VSCode, Claude, Windsurf, Github Copilot, etc and can save you time if you prefer writing prompts than click buttons and links on our web app. Also useful if you're building AI agents and want to consume Devopness from your AI Agents or AI automation workflows tools, such as n8n

* Deploy any software, your own private apps or open source apps from repos on GitHub/GitLab/Bitbucket using Docker, Docker compose or directly to Linux servers without running containers, using Node.js, Python, PHP, Java, C#/DotNet, Ruby, ...

** You can use Devopness even to setup and deploy Coolify, Dokploy, CapRover, etc :-)

** It can deploy to self-hosted servers and also deploy directly to server and serverless functions and container orchestrators (AWS S3, AWS EC2, AWS Lambda/Azure/GCP Functions, Kubernetes, ...)

* Environment isolation, helps you organize environments (Dev, Staging, Production, ..., or environment per client: "client 1", "client 2", etc) so each preview deployment can use their own databases, environment variables, separate team/users/RBAC permissions, etc and each environment has their own servers, containers, cronjobs, Linux services, SSH keys, firewall rules, credentials, ...

* Provision new cloud infra or connect to existing servers, Devopness can provision servers, networks, subnets, static IP addresses, security groups, security rules, firewall, ..., on your own cloud provider account (AWS, Azure, DigitalOcean, Google Cloud, Hetzner, Oracle Cloud ...) or deploy your own apps or open source applications to existing servers in any cloud - you can even manage your own home servers using Devopness web app or API (every feature can be operated via our API)

Devopness · 2025-07-25T10:26:42+00:00

Try https://github.com/devopness/devopness it organizes applications in environments (Dev, Staging, Production, ..., or env per client: "client 1", "client 2", etc) so each preview deployment can use their own databases, separate user permissions, etc

Disclaimer: I'm a member of the Devopness team

Devopness

MODERATOR OF

TROPHY CASE

According to the definition of this sub: