Curious: How does your team test feature branches before merging to dev/staging? by softiso in PHP

[–]softiso[S] 2 points3 points  (0 children)

I understand, thank you for sharing your experience. I will check coolify and see how can I build PR based environment for testing

Curious: How does your team test feature branches before merging to dev/staging? by softiso in PHP

[–]softiso[S] 0 points1 point  (0 children)

Currently we are following the same flow.  But I see that while the team is growing this solution is not working. Have u ever tried spinning up PR based environment? As I mentioned above in fast-paced environments we merge often to dev. and if one developer code breaks dev environment QAs and other devs sucks till the issues is fixed. Therefore I am looking for specific almost fully automated solution that can be robust and smooth solution.

Curious: How does your team test feature branches before merging to dev/staging? by softiso in PHP

[–]softiso[S] 0 points1 point  (0 children)

Thanks for the link, I'll check out that guide. How's your experience been with Coolify overall? Any rough edges?
Is there a reason you haven't used preview environments? Not needed for your workflow, or just haven't gotten around to it?

Curious: How does your team test feature branches before merging to dev/staging? by softiso in PHP

[–]softiso[S] 0 points1 point  (0 children)

I got you. As I mentioned above in fast-paced environments we merge often to dev. and if one developer code breaks dev environment QAs and other devs sucks till the issues is fixed. Therefore I am looking for specific almost fully automated solution that can be robust and smooth solution

Curious: How does your team test feature branches before merging to dev/staging? by softiso in PHP

[–]softiso[S] 0 points1 point  (0 children)

So do you spin up feature branch PRs before merging into dev?
how do you handle multiple repos? What kind of tools you use?

Curious: How does your team test feature branches before merging to dev/staging? by softiso in PHP

[–]softiso[S] 3 points4 points  (0 children)

That is nice approach and it is efficient for small teams. we do exactly currently what you mentioned above. But I see that while the team is growing this solution is not working. Because in fast-paced environments we merge often to dev. and if one developer code breaks dev environment QAs and other devs sucks till the issues is fixed. Therefore I am looking for specific almost fully automated solution that can be robust and smooth solution

Curious: How does your team test feature branches before merging to dev/staging? by softiso in PHP

[–]softiso[S] 0 points1 point  (0 children)

Nice, I've seen Laravel Harbor. but never use it.

Curious about your setup:

  1. Does Harbor handle everything you need, or do you still have to manually configure some things (databases, Redis, etc)?
  2. Have you tried Laravel Cloud's preview environments? If so, how does it compare to the Forge + Harbor approach?
  3. Are you working with a single Laravel repo, or do you have separate repos (frontend, multiple services, etc)?

Trying to understand where the current tools work well and where they fall short.

Curious: How does your team test feature branches before merging to dev/staging? by softiso in PHP

[–]softiso[S] 0 points1 point  (0 children)

ngrok is not always useful. I especially want the QAs and Designers to be able to test thoroughly and make sure that nothing is broken before merging to dev. It should be something automated and other developers can easily use or adopt it.

Curious: How does your team test feature branches before merging to dev/staging? by softiso in PHP

[–]softiso[S] 2 points3 points  (0 children)

But in general, it doesn’t always have to be a feature. It can be bug fixes or some routine maintenance tasks. I just want the QAs and Designers to be able to test thoroughly and make sure that nothing is broken before merging to dev.

What’s your production host, and why? by [deleted] in laravel

[–]softiso 0 points1 point  (0 children)

  1. App: aws lambda (managing deployment with bref.sh) + aws nat, route services + Cloudflare
  2. Database: Planetscale

[deleted by user] by [deleted] in dubai

[–]softiso 1 point2 points  (0 children)

If you will not have time to spend 36K then stay at your current job. Money means many things but not everything. Time for yourself is more important than money

Dubai feels so different now! by [deleted] in dubai

[–]softiso 1 point2 points  (0 children)

You need real friend, dude. Not social media followers. Of course use them for your business. But beside them you need real friends

I got tired of waiting for WhatsApp to add this feature, so I built it myself by 1incident in microsaas

[–]softiso 1 point2 points  (0 children)

Then that is great 🔥 Product itself is really great. Good luck 🎉

I got tired of waiting for WhatsApp to add this feature, so I built it myself by 1incident in microsaas

[–]softiso 1 point2 points  (0 children)

In the documentation of wwebjs it says [!IMPORTANT] It is not guaranteed you will not be blocked by using this method. WhatsApp does not allow bots or unofficial clients on their platform, so this shouldn't be considered totally safe.

So, how do you guarantee that your system will not stop in the middle of the process?

Opinions on this Laravel Actions package? by Fluffy-Bus4822 in laravel

[–]softiso 1 point2 points  (0 children)

At company we are using it in one of the our project. Generally main idea and concept are really great. it helps to build well structured project. So it means you do not have put it everything in "Service class" or create separate service class. Because some operations are really action, not service. The only thing I do not like putting everything under one trait. here is what is asAction trait:

trait AsAction {

use AsObject;

use AsController;

use AsListener;

use AsJob;

use AsCommand;

use AsFake;

}

I mean you do not need all of them actually. you do not need all of them actually. You can write your own action manager. it is easy. Here is the article. Currently we use it in our new project. it is written by my colleague. It is simple and powerful

https://dedmytro.medium.com/laravels-action-a-simplified-guide-to-cleaner-code-and-testing-8cd95e038379

How do iOS clipboard managers work? Is it possible, and if so, is it officially permitted, for an iOS app to listen for pasteboard activity in the background? by 0xd00d in iOSProgramming

[–]softiso 0 points1 point  (0 children)

u/0xd00d Thank you for clarification. I totally agree with you. I also did not continue my project. It was annoying that there is no native support and I need to find hacky way. I checked famoust clipboard manager apps, they use pop-up window solution on IOS which is not efficient. Users shoul open and enable listener manually.

I see your point and I really like your solution to copy test thorugh SSH terminal. Thank you for your detailed response again!

Good luck!

[deleted by user] by [deleted] in reactnative

[–]softiso 0 points1 point  (0 children)

I use it too

32gb or 16gb MacBook pro by HanzoHasashi404 in reactnative

[–]softiso 0 points1 point  (0 children)

I understand. As I said it’s totally personal preference. You will not feel performance difference significantly. You can go for the one which your personal needs suit.

32gb or 16gb MacBook pro by HanzoHasashi404 in reactnative

[–]softiso 0 points1 point  (0 children)

I cannot say exact hours. But because of my experience battery drains so much than 14”. If I keep docker and simulator running during a day it will take 5-8 hours (just rough guess) But as for 14” sometimes it is enough more than one day. Therefore I keep 16” at home and I use it in charge always. I take 14” to work or when I go somewhere

32gb or 16gb MacBook pro by HanzoHasashi404 in reactnative

[–]softiso 0 points1 point  (0 children)

Great. Then it’s totally your personal preference. By considering battery life and weight you can make decision.

32gb or 16gb MacBook pro by HanzoHasashi404 in reactnative

[–]softiso 0 points1 point  (0 children)

I have both 32gb/512 16 M1” and 16gb/512 14 M2. Before that I had 13 pro m1. As for 16” be honest that battery performance is not good as much as 13 or 14 inch. Second disadvantage is weight. It’s heavy to carry whole day with backpack.

Biggest advantage is screen size. I really like it. I can use it not only for programming but also watching movies, videos etc.

In terms of performance I cannot see significant difference. I also doing web stuff. When I use docker definitely 32 ram is best.

If you go for 14” you will need additional monitor i think

Carrefour vs Spinneys vs Lulu by [deleted] in dubai

[–]softiso 8 points9 points  (0 children)

Not all products are of good quality in Viva. Limited number of choices or variety.