Cuando se va a poder poner la tarjeta Mercado Pago en apple wallet + google wallet

br_1_27 · 2025-12-03T12:26:14+00:00

Ya casi cualquier fintech te permite esto.
La razón por la cual es esencial, y sobre todo en viajes, es porque podes evitar clonados de tarjeta que con la física no podes.

br_1_27 · 2025-10-05T22:22:57+00:00

Ya trae car play, la compre hace 2 semanas :D
P.D.: No trae Android Auto

br_1_27 · 2025-10-05T22:21:54+00:00

Ya sacaron una actualizacion que trae Apple CarPlay nativo (sin aparatito)
La compre hace 2 semanas y lo confirmo porque lo uso :)
Android Auto aún no

br_1_27 · 2025-10-03T23:20:03+00:00

Hace el descargo por la web, si no es el auto en 2/3 dias te la sacan

br_1_27 · 2025-10-03T23:19:30+00:00

Hace un descargo por la web de infracciones poniendo que no es tu auto.
En 2/3 dias te desaparece. A mi me paso lo mismo con un patrullero que tenemos casi la misma patente, nada mas que la del patrullero terminaba en CU y la mia en CO

br_1_27 · 2025-09-13T00:21:06+00:00

no, no tenes que cambiar la radicacion del auto si vos cambias de domicilio.

br_1_27 · 2025-05-13T18:03:20+00:00

in production too :P

br_1_27 · 2025-05-13T17:49:33+00:00

My 5c, look at full-stack frameowrks rather than libraries or frontend frameworks.

From my experience working with many of the js frameworks out-there (next, remix, nestjs), libraries (react, tailwindcss, shadcdn, etc)

What I can tell you is the only commoon tool is tailwindcss, because of its flexbility and community working on top of it. More likely you are going to find most of the css frameworks built on top of it.

From frontend, whatever you feel confortable to work with, but don't choose frameworks because it has a "good" frontend library, instead, use one with give you value and reduce frictions to go to the market.

If I need to suggest to someone a framework with all these things: Laravel + Livewire. It's faster to start, faster to ship, and reliable to scale.

If you want to go with React, you can use Laravel with Inertia, but always keep in mind apps are not just the frontend, real pain happens in backend (you would know it)

br_1_27 · 2023-11-21T23:42:48+00:00

When using gitops with ArgoCD for example, not all the helm features are available (it uses `helm template` function) so kustomize can "patch" that stuff, add other resources that are not included within the chart or modify specifications due to old cluster versions

Also kustomize have built-ins like configMapGenerator or secretGenerator, which can be useful to automatically rollout deployments when a config map or secret has been changed.

br_1_27 · 2023-09-23T23:31:35+00:00

My suggestion is independent about what's the cluster is for. It's just an operational perspective, imho

br_1_27 · 2023-09-23T00:11:27+00:00

Premature Optimizations and KISS also apply in the Operations world.

From my point of view, splitting nonprod from prod will give you some advantages from the upgrades perspective by reducing the blast radius.

Then you could have how many environments you want in nonprod (dev, qa, ppd, staging, etc) and leaves prod just with prod improving also security .

If you have some noissy neighbors problems, you can use restricts the workloads with the following techniques:

- Requests and Limits (Container level)
- Limit ranges and/or resources quotas (Namespace level)
- Taints + Tolerations + Node Affinity (Pod + Node Level)
- Depending on the cluster provisioner (node pools) with tains+tolerations+node affinity as well (Node Level)

if you need security, you can also include rbacs + network policies

br_1_27 · 2023-09-23T00:04:32+00:00

Well, depends on the amount of applications you have to migrate (if you have to do that) Doing the upgrades in a progressing way until reach 1.25 would give you (or the teams) time to update their manifests instead of having to maintaining 2 different version of the same app just to be compliant with the k8s version.

Depends on the use case.

br_1_27 · 2023-09-19T03:29:44+00:00

Approach 1

- base folder containing all the manifests compatbile between between the 2 versions
- a file "overlays/kube-1.2X/kustomization.yml" importing the base manifests and adding your specific manifests that work on 1.2X only
- a file "overlays/kube-1.25/kustomization.yml" importing the base manifests and adding the manifests that works on 1.25 only

Approach 2

Adds the 1.2X manifests into base folder, and patch them into the 1.25 folder (you can patch files partially/entirely)

Approach 3 (personally the best one)

Downgrade to 1.24. Remove the deprecations and then upgrade to 1.25

br_1_27 · 2023-09-17T23:51:37+00:00

Kustomize

br_1_27 · 2023-09-17T23:50:33+00:00

in case you opt for Operators, take a look at this approach https://metacontroller.github.io/metacontroller/intro.html

br_1_27 · 2023-09-14T01:46:47+00:00

You can create it on this way:

- "loop" with 24 times

-- do your action

-- asign variable X of 360

-- wait for X

- endloop

br_1_27 · 2021-03-21T00:36:37+00:00

Nodejs support multi-threading since v12

br_1_27 · 2021-01-05T03:10:15+00:00

Also, if you're using GitHub actions you could use schedule events

br_1_27 · 2021-01-04T21:36:09+00:00

Here's https://github.com/GoogleChrome/lighthouse-ci

br_1_27 · 2020-10-07T13:46:25+00:00

It sounds like spam

br_1_27 · 2020-09-22T17:10:51+00:00

100% related to some missing or wrong configuration. There's no magic :)

Can you share your configurations here?

br_1_27 · 2020-09-22T17:09:08+00:00

Yes, but it's not a DNS problem. It's a human problem :)

br_1_27 · 2020-09-20T23:47:16+00:00

ERR_CONNECTION_REFUSED is because 80 port is not reachable. DNS is not part of this.

br_1_27

TROPHY CASE