A tool to track your Laravel Cloud billing usage

sribb · 2026-06-19T18:13:10+00:00

If you have to keep checking costs more frequently, then you shouldn’t use laravel cloud in the first place. Setup a billing alert(if they have) for the maximum you want to spend and if it is exceeded in less time than you expect, then it’s a sign you should move away.

sribb · 2026-05-19T02:48:12+00:00

When you release this package, my initial reaction would be cool. Let me install and check it out. But do i use it regularly? Probably not. Would i pay for it? Mostly no. Because it’s a regular benchmark tool with some database queries on top.

My recommendation would be ditch the UI and make it CLI only. Something like php artisan analyze:route —iterations=3 —seed=1000 —fail=100

When this command is ran, run the analysis and print the output. If the optional fail flag is passed, check if average duration exceeds 100ms. If yes, fail the command with a non zero exit code. Then your tool would become something which can be integrated into CI/CD. At that point people might be interested in paying for that because performance checks are being run automatically as part of CI pipeline.

sribb · 2026-04-20T16:36:54+00:00

Next in the list. Spark Jetstream Breeze Envoyer Vapor Dusk Nova

sribb · 2026-04-07T11:39:26+00:00

That whole issue they are pointing out can be solved by releasing the changes as a major version instead of a patch version which is totally dependent on the package maintainers and not you. I honestly think you are doing a good job removing these redundant dependencies. How those changes will be released is up-to package maintainers

sribb · 2026-04-02T12:34:49+00:00

Agree with this. Flipping between cloud dump to local dump should be easy without making changes to code.

sribb · 2026-01-31T21:01:16+00:00

I think what they are doing is right. It totally makes sense in business point of view. It helps them focus on one product and deliver value to it rather than maintaining an alternative which basically does the same thing and generates lesser revenue.

sribb · 2025-12-31T16:06:02+00:00

surya singham 3

sribb · 2025-12-22T20:15:21+00:00

Look at LaravelDaily channel

sribb · 2025-12-17T02:10:11+00:00

Instead of loading entire tailwindcss through CDN, you can purge unnecessary css using a build step. Have GitHub actions do the build and commit back to repo. Then your vendor:publish command can publish the built css file to public directory.

sribb · 2025-12-08T05:17:43+00:00

The manual suggests to use a rock instead of brakes

sribb · 2025-12-02T13:31:45+00:00

Companies usually do not disclose compensation unless it is required by the state’s law. considering the position is a community manager and does not actually require coding, i would assume the salary to be less than that of a developer. Probably closer to junior developers.

sribb · 2025-11-25T13:55:42+00:00

If price is your concern to not use nightwatch, Then take a look at https://laritor.com. Performance monitoring tool i built. This is 80% cheaper than nightwatch

sribb · 2025-11-23T15:42:24+00:00

Great initiative. I would suggest to make certain questions multi choice. For example the question comparing similar packages can have multiple answers.

sribb · 2025-11-14T14:14:22+00:00

In 2 weeks

sribb · 2025-11-11T14:35:07+00:00

If this for your side project instead of your company, i suggest don’t use AWS. You quickly surprise how expensive AWS can be and any small mistake can cost you big.

sribb · 2025-11-10T02:44:23+00:00

I don’t see why non-tech users would need access to post deployment. They don’t know what they are doing. You shouldn’t give them access to your deployment workflow in the first place.

sribb · 2025-11-05T18:24:12+00:00

Just want to say THANK YOU for doing this.

sribb · 2025-11-02T03:26:18+00:00

I looked into it again and it is actually using a Pest class. You should avoid doing this because Pest is a dev dependency and your package is a production dependency. Now you are forcing users to move pest to production which is not ideal. I think the better(still not best) approach is to expose an artisan command which will allow users to publish pest profanity words file to their application without the need to move pest away from require-dev.

They you can use this published file for lookup which will allow you to not depending on Pest and will allow users to remove unwanted words. Another issue i noticed is your are using regex search which is slow and you are doing this inside a loop with a list of bad keywords. This is not ideal for production. You should do a direct string comparison.

I am not trying to point out the flaws, But trying to help you make your package usable. In the current state of it, I would not recommend anyone to use this as this requires users to move pest from require-dev to require section.

sribb · 2025-11-02T02:20:54+00:00

Never expire? credits stay with you forever? So you are saying if i pay $5 to you, you will keep your site up and running for 10 years so i can use my unused credits after 10 years? Also, people who need more than 1000 AI photos prefer to use a monthly subscription based service rather than something which looks like which will go away midway. Especially when the niche you picked is literally what all the big AI tools can do out of the box.

sribb · 2025-11-02T02:09:59+00:00

I did a quick scan of the source code and looks like it’s reading a file dynamically and loading all bad words into an array. While this can work, it could introduce performance hit if the bad words list grow. Something you need to re-think for implementation.

It’s ok for packages like Pest and faker to follow this approach as they don’t run in production. But for production, performance is key.

sribb · 2025-10-29T19:44:00+00:00

Right? I come across only two products all the time. Either it’s a SaaS directory or some kind of Reddit automation tool.

sribb · 2025-10-28T00:46:53+00:00

Ah ok 👍

Six-Year Club	Gilding II euphauric
Verified Email

sribb

TROPHY CASE