GP2040 VS flyctl

I think they use https://github.com/FeralAI/GP2040

I've had a great experience with Arduino Pro Micro's running the DaemonBite firmware, and the RPi Pico GP2040 firmware should be similarly great. Both have extremely low latency. The Brook Universal board is another good one. Other than that, I usually just use either a DualShock 3 pad over USB or a wired 360 pad. I also like the iBuffalo SNES pad and Logitech Precision pads.

My third revision of this and looking for feedback to improve. I'm using an secondary USB-C port here to test this schematic before using it on other builds where the Pico placement is constrained by board clearances and mounting holes. The Pico is running GP2040, https://github.com/FeralAI/GP2040, which allows the device to work on multiple systems. I'm new to PCB design and have grabbed some examples posted here before and hopefully following guidelines in the wiki.

It might also be worth checking out the pi pico as the brains, though I believe you need a second piece of hardware to make it work on ps4. The pi pico itself should only be 10$~ not sure how much the ps4 adapter thing would cost. The firmware to look into is https://github.com/FeralAI/GP2040

Hi, does anyone know how to add a PS Home button to your controller? I have a DURAL hitbox which uses GP2040 Firmware (https://github.com/FeralAI/GP2040). I was planning on going to an offline event and needed to make my controller PS4 proof for which I was hoping to use a PS3 to PS4 adapter. However I would still need the PS Home button because PS4 is weird. If anyone knows a solution help would be greatly appreciated.

Microsoft totally does. That's why GP2040, an open source controller firmware, doesn't support Xbox or PS. The way it's typically done now is to have a require a real controller to handle the authentication, with the 3rd party input in between the real controller and the console (passthrough in that chart)

To begin visit fly.io to create an account. Next install flyctl a command line tool for creating and deploying fly apps. macOS

For frontend deployment, I used Netlify (for the generous free package) and the recommended fly.io for server + database (also cheap package).

Create an account on Fly.io.

You can learn more about fly.io and tigris, we will need to create an account on both platforms for this project regardless. Anyway with the theory out of the way let's get started in the next section as we create our accounts and start building the app.

Fly.io is a platform that helps you run your apps and databases closer to your users all around the world. It takes your app code, packages it up neatly, and puts it on virtual machines that can be quickly started or stopped. This makes your app faster for users and more reliable. Fly.io is easy to use, works well for small projects or personal apps. It's a great way to make sure your app runs smoothly for people no matter where they are.

In this post, we'll start from scratch, running FerretDB locally via Docker, trying out the connection with mongosh and the MongoDB Node.js client, and finally deploy FerretDB to Fly.io for a production ready set up.

2- fly.io

Fly is a cloud platform that focuses on global edge computing. Fly specializes in high-performance hosting and provides a global network of edge locations. Fly is known for its scalability and performance optimizations.

But videototextai.com is built using NextJS + Firebase auth + Firestore and a backend deployed at fly.io . Fly makes it really easy to deploy docker containers and that is IMO the fastest way to develop, you can setup a local setup

Alternatives explored: * northflank: While running the wrk test, requests were taking 3-7 seconds. Couldn't repeat Heroku's phenomenon of "400ms-800ms" during such a load test. * fly.io: Reliability: It’s Not Great * render.com: I remember the time when indiehackers.com was down because of an outage on Render, not sure if it's worth trusting.