Docker image coming?

[marendowski]

Hi, I'm playing around with feeds.fun, and so far loving it, but really would appreciate a docker image, because I wanted to integrate it into my docker-based homelab. I've read #84 and still want to ask: is docker image coming?

[Tiendil]

Hi!

Thank you for your interest in the project!

The difficulty with images is that there are numerous ways to organize them.

Can you describe what you want from a Docker image(s)? It will help me.

I think about two images:

• One for the Python backend, which can start the API server and workers. You may need to up a few services (one for API and at least one for background workers).
• One for the frontend. I see two options: an image with a Caddy instance, which serves static files; or an image that just copies static files on the volume you specified, to be served by your web server.

[marendowski]

Well, I would like to have one docker-compose that will just install and start up everything with minimal configuration. For example I'm now looking for a self-hosted RSS reader, I'm trying out a few of them at a time and don't have enough time to delve into everything in each one of them, where I could simply spin up a container and test it out (but this reader is worth the effort). I think that keeping it simple is the key and a Caddy instance is an overkill.

[Tiendil]

Thanks; it's much clearer now.

I will prepare something simple within a month.

[noahkiss]

Hey Tiendil, when I run locally with the current docker-compose, I get an 'unknown error' on my feed status. Any idea what could be causing that? Are there env variables which need to be defined but which aren't in the docker-compose file which may be causing that?

[Tiendil]

The docker compose file should work as is, no additional configuration required.

Where do you see an 'unknown error'? Logs (of running docker containers) or screenshots (of the GUI) would be helpful.

Also remember that the docker compose does not include worker processes that load feeds and populate them with tags.

Check the last step of this part of REDAME: https://github.com/Tiendil/feeds.fun?tab=readme-ov-file#run

P.S. I'm on a small vacation, so I may answer slowly this week.

[Tiendil]

Also. If you use dev docker compose file, you should comment tmpfs volume in postgres service and uncomment permanent volume. Otherwise your data will be stored only in RAM an lost on reboots/docker restarts.

[Tiendil]

Hey! It's done!

See instructions:

• single-user setup
• multi-user setup

There are two images:

• One for the backend, to run all that is required.
• One for the frontend, just to copy static files somewhere your reverse proxy (Caddy, Nginx, etc.) can find them.

But slightly more Docker services :-) I tried to find a balance between agility and simplicity.

The examples include fully working docker-compose files for single-and multi-user setups, suitable for experimenting, testing, etc.

There are some nuances related to hosting Feeds Fun as a permanently working service. For more details, see the example's README.md and comments in the files and configs.

I'm closing this issue, but feel free to ask if you have any questions; open issues, PRs, etc.

I'll be especially grateful for PRs (or just comments here) with documentation improvements based on your experience with self-hosting Feeds Fun.