31–40 of 49 posts
Am I missing the "mark all as read" button? That would be helpful vs going through 13 years of old posts and marking read page by page (albeit quickly at 500 at a time).
Earlier quoted context omitted.
> Node 21 with NPM > Sveltekit, shadcn-svelte > Echo, GORM > gofeed And the documentation literally specifies it requires docker. How did this become "minimal dependencies"?
Hi. Just to clarify. > Node 21 with NPM > Sveltekit, shadcn-svelte The front-end things are used during the build process. You don't need them when deploy. > And the documentation literally specifies it requires docker. Fusion can be deployed as a *single binary*. Docker is just the recommended way. Maybe we need to make documentation clearer.
And what's good about a single binary if you're going to recommend Docker?
Earlier quoted context omitted.
Hi. Just to clarify. > Node 21 with NPM > Sveltekit, shadcn-svelte The front-end things are used during the build process. You don't need them when deploy. > And the documentation literally specifies it requires docker. Fusion can be deployed as a *single binary*. Docker is just the recommended way. Maybe we need to make documentation clearer.
Why recommend Docker if it's a single binary? And what's good about a single binary if you're going to recommend Docker?
Earlier quoted context omitted.
Hi. Just to clarify. > Node 21 with NPM > Sveltekit, shadcn-svelte The front-end things are used during the build process. You don't need them when deploy. > And the documentation literally specifies it requires docker. Fusion can be deployed as a *single binary*. Docker is just the recommended way. Maybe we need to make documentation clearer.
Why recommend Docker if it's a single binary? And what's good about a single binary if you're going to recommend Docker?
Earlier quoted context omitted.
Why recommend Docker if it's a single binary? And what's good about a single binary if you're going to recommend Docker?
it's still easier to manage docker containers if they're 50 MB instead of 300MB and if the rest of the fleet is being managed via docker-(whichever) then there's something to be said about consistency. managing everything through one interface is easier than remembering all the special cases. but to each their own.
Compared to all that, the current PHP app I use for RSS looks lighter. Especially since my VPS already runs PHP and PostgreSQL.
Great project. Spun the docker version up on an Oracle always free VPS instance (server class: potato) in a few seconds and it runs great with my imported OPML with a few hundred feeds. As the enshittification of feedly continues I'm keen to find a replacement. Am I missing the "mark all as read" button? That would be helpful vs going through 13 years of old posts and marking read page by page (albeit quickly at 500…
But large page size can cause page performance problems.
Does it produce a rss feed itself?
You can create an issue about it on GitHub so we can evaluate how much it is needed.
Earlier quoted context omitted.
Hi. Just to clarify. > Node 21 with NPM > Sveltekit, shadcn-svelte The front-end things are used during the build process. You don't need them when deploy. > And the documentation literally specifies it requires docker. Fusion can be deployed as a *single binary*. Docker is just the recommended way. Maybe we need to make documentation clearer.
It's an interesting difference in backgrounds, maybe? I tried to build this on OpenBSD where we don't have docker and we use 'make' instead of random shell scripts. For what it's worth, this is from the build log: error code 1 error path /home/holsta/3rdparty/fusion/frontend/node_modules/@sveltejs/kit error command failed error command sh -c node postinstall.js error /home/holsta/3rdparty/fusion/frontend/node_modules…
There is nothing we can do about it at the moment. Maybe in the future we will change the tech stack to reduce the complexity of the front-end.
Earlier quoted context omitted.
it's still easier to manage docker containers if they're 50 MB instead of 300MB and if the rest of the fleet is being managed via docker-(whichever) then there's something to be said about consistency. managing everything through one interface is easier than remembering all the special cases. but to each their own.
The image is 200 MB... There's 100 packages in there, including bash, perl, ext filesystem utilities, and the APT package manager. Compared to all that, the current PHP app I use for RSS looks lighter. Especially since my VPS already runs PHP and PostgreSQL.
Earlier quoted context omitted.
The image is 200 MB... There's 100 packages in there, including bash, perl, ext filesystem utilities, and the APT package manager. Compared to all that, the current PHP app I use for RSS looks lighter. Especially since my VPS already runs PHP and PostgreSQL.
You can use the standalone binary (18 MB) to run it. Docker is just one deployment method.
Hold on, I'm back to my earlier comment.