28

Oh, no, I meant distribution provided packages for Apache/Nginx, PHP, MySQL/PostgreSQL, etc. “I’m running Ubuntu, but I decided to try out MySQL beta, and now tt-rss doesn’t work.” None of that.

As for tt-rss itself, git master or go home.

29

that makes sense, until you get someone running arch. :slight_smile:

30

Not a big fan.
From a developer perspective I understand your point.
But for the end users/admins who are not used to docker it will certainly increase complexity and I am not sure on whether this will increase problems or questions asked or make things easier.

Would appreciate to continue with syncing git. Was working without problems for me for quite some time…

31

Since everyone is jumping on the band wagon, I would hate to feel left out: I could not care less if it is docker or vanilla git with sysadmin mojo. If both work, I will stay on the later 'cause that is what I am used to and it works for me. If Fox decides to only support docker, I will move to that. If Fox moves to $whatever only, I will learn that and use it. In the mean time, I will continue to stoke up on fuel, weapons, and provisions expecting the coronavirus apocalypse to start soon…

32

tbh, I’m clueless to what docker (or Linux containers for that matter) is/are all about at this point so as_long_as I can continue to ‘git pull’ tt-rss to my self-hosted server all is good.
.

33

I’ll second this motion.

34

Actually, this is so tricky and user specific… I don’t like the idea too much, but I completely understand.
The user should have do most to identify problem first and be able to fully reproduce “on brand new distro installation” otherwise should dig their owns. But completely “fuck all non-container” isn’t good idea, by my opinion.

35

Isn’t the whole point of docker to reduce the complexity?

36

Depends on your point of view.
From the articles I read about docker it reduces complexity for hosting/web application providers or IT departments with several applications supported by docker.
In this case: yes it does.

When you just run TT-RSS on a VPS and nothing else and have no clue about docker, its dependencys and functionallity or what is persistent and what could be updated etc… I do not think it reduces complexity.

37

Prsonally I am happy with the git pull, but understand that others might want something simpler. I don’t want the extra overheard of another fpm, php, postgresql running but that is me. I don’t see that having the git pull and then docket container are at odds. we need the base source tree to create the container from. This means to me that creating the container is just a later step in the build process and that this isn’t an either or…

38

this is completely wrong.

installing via docker is orders of magnitude easier than going through all the motions to install fpm and required php packages, nginx, database server, git clone tt-rss into a correct location, fix permissions, etc etc etc.

let’s not even talk about all the stuff you need to know so this setup has some semblance of security and your host is not compromised in the next 5 minutes because you decided to put something like wordpress in /var/www next to tt-rss.

also, “having no clue” about containerization is not an excuse. go get a clue then. and stop deploying services directly on your host.

39

Please do me a favor and tell me, how we keep the underlying Docker-Container base image, php, fpm, nginx, … up to date as the process for dong it isn’t “apt-get update”.

40

we’ve already established that you don’t know what you’re talking about in your previous post itt, you don’t really need to dig yourself further.

also, imagine i probated you for questions you could easily google answers to.

41

Happy to do so if you could kindly provide me some spare time? :smiley:

42

Since you are both too lazy to do a simple good search, Let me point you to Docker’s home page’s “Get Started” page… As an added bonus, it takes like ten minutes to read.

Go get a cup of coffee (or tea, or whatever poison you like to drink), and read all those pages. As I said, it does not take longer than you would if you eat lunch at your desk and you can book that time in continuous improvement at work.

43

I currently run all my services in separate LXD containers on Debian, so I’m generally not opposed to the idea of containers. That said, running Docker within LXD, while supported, was finicky in oldstable Debian (AppArmor shenanigans) and I haven’t gotten around to trying it on Buster yet. Of course, that’s not really relevant to whether you should only support Docker.

I’ll probably stick with my current setup with the git master for as long as it stays working :slight_smile:

44

you’re running docker inside LXD? :face_with_raised_eyebrow:

45

I don’t usually hear of anyone doing a container within a container. (And if this is on a VPS, that’s a container within a container within a container.)

46

imagine doing all that in a nested KVM

47

Once - I wanted to run Guacamole and didn’t want to install Docker directly on the host when everything else was already LXD’d. Worked out okay after a bit of tweaking. I hear it’s better now and should Just Work™ but haven’t bothered trying yet.

Suppose I’ll do the same for tt-rss if the direct git master breaks in a way I can’t fix.

And yea the host is a dedi - I’m not quite that insane.

quietly purges KVM