Wait, the optimization does not leave the browser. There isn’t any need for a web server.
If this can be used as an offline PWA, it doesn’t even need to be ‘self-hosted’, except for keeping it up to date.
Edited: removed reference to “device”, to avoid confusion.
Fair enough!
While I appreciate the sentiment, I do think that despite being well-intentioned this could just contribute to today’s digital illiteracy. It also downplays the app’s privacy, I almost dismissed it as a cloud service the moment I saw that.
Perhaps you could use “open” and “save”, which is widely understood and probably more appropriate.
That said, the app is a great initiative, and I’ll certainly give it a look once I get in front of a computer, and probably recommend it to students.
I’m confused, isn’t this running locally? Why are you using the words “upload” and “download”?
If you do go this route, the best way is to make a fork of the main Umami github repository, then link that to railway. When you want to update, you can just sync new changes to the repo, and railway will rebuild your instance.
I’m running Umami on Railway (so not self-hosted), for two small websites. Works pretty well. I think Railway changed their pricing, but I’ve been grandfathered in with a free plan.
Edit: all of my websites are also on Netlify.
Depends on the license.
While there is something that attracts me to dumbphones, my problem is that their main function, calling, is something I almost never do.