Uppy VS PM2

I just found uppy. This will be the next one I use. https://uppy.io/

I’m building a photo sharing website and want to make it incredibly easy to upload photos. Of course I could just utilize AWS official packages but that’s pretty bare bones. I could also use next-s3-upload which is purpose built for Next and simplifies some things but is still fairly basic. But then there’s things like uppy that provides everything you’d ever need in an uploaded (third party sources, camera, etc.) that would be nice to haves, but apparently doesn’t play well with Next without a separate Node server.

Media file uploads with the Uppy JavaScript uploader plugin

Check out Uppy and Uppy Companion: https://github.com/transloadit/uppy/

I would look at Uppy.js, I've used it in an enterprise application and it works super well, makes it super easy to do what you're trying to achieve with progress bars for each file.

I started to try out https://uppy.io/ but their lack of good documentation makes my life a bit difficult. However, uppy seems to be the only available solution out there in the React land (i dont want to implement it by myself).

🔀 Repositório no GitHub

Run the application using PM2 (ref: Process manager for Node.js)

There are plenty of ways to accomplish this: Docker, Kubernetes, Pulumis, etc., but I don’t like to add too much complexity. So for a basic app, I like to use PM2, a Node.js process manager with great features, including the ability to run our app in the background.

This project will consist of a single "index.js" file that you can deploy anywhere. I recommend using an Nginx reverse proxy and pm2 to keep the service running.

Your app should be running now. To be able to run the app in the background, I will use pm2. Stop your application using "Ctrl + C" and install pm2

https://www.npmjs.com/package/pm2 I found this package. It looks good and solves my problem, I think.

Usually, you have something that restarts it for you. This is what a "process manager" is for, e.g. https://www.npmjs.com/package/pm2 But in most more advanced systems, this is taken care of for you differently. E.g. lambdas are restarted automatically based on how many instances are needed. If you are in container-land, there's usually a health check endpoint on your server that gets pinged by the container orchestrator, and if there's no response, it will kill and redeploy the container.