My lazy ass, nowadays.
My lazy ass, nowadays.
Next evolution, just a one line bash script.
Me: install it, doesn't work, read the docs, screw with all the missing things, doesn't work, read the forms, install something else I missed, doesn't work, find more forums, find the right answer, patch it up, get it working, figure out that the application is slow, missing critical features, and really just doesn't do what I needed to do.
127All-in-all a weekend well spent
72It’s like I’m still in c/selfhosted
1
Or it does work, and then I never actually end up using it again.
And then months later I'll have to do something similar and I've forgotten I even installed something that can do that, so I install another related thing.
14really just doesn’t do what I needed to do.
This has been my experience, or sort of does what I want it to do, but I have to rethink what I need it to do instead of something really simple. Like a "new type of shared file system" that replaces NFS/Windows sharing. So instead of files in a standard file system one can manage with a file browser, it has "indexed" your files in such a way that the actual files are renamed into data chunks, and one "finds" files by their non-intuitive search engine that can't do even basic search engine tricks like "AND/OR" searches, wildcards, and the results are hit and miss. "But it's faster and more elegant!" So how do you restore from backup when the system fails? "When the system does whatnow?"
Yeah, no thanks. I can recover files from a file system much easier than some proprietary encoded bullshit fronted with a bad search engine over a proprietary and buggy index.
6I asked the other week if anyone made a system that left files alone and just indexed them and gave you a place to store meta without moving them. Options do seem to exist, but they need LOTS of extra work
5
When the project installation steps start with a 'git clone'.
44Nah, to much work, use curl to download a script and blindly run it...
4I have a couple scripts running in containers. I’m too lazy to do a proper CI build and I only run it on one system anyway so I just got pull and docker build. Sorry if i offend you.
Though if i keep this up I’ll probably just start to use my generic python container and commit a shell script to docker run with . mounted to /project or something, and set the entry point to pip install project/requirements.txt; python project/main.py.
2
I was blown away how a relatively unknown project like immich provides one Docker compose file to bring up a whole self-hosted
Google photosphoto management suite, complete with tagging, mapping, transcoding and semantic search. Local, offline semantic search.38Tell me more
7I'm having a hard time getting into software that doesn't use traditional folder structures. I wish I could point immich to my NAS Pictures folder and have multiple places to seen the same exact files, immich when I want, nextcloud maybe, or just a file browser pointed to my NAS.
I'm having the same issue with paperless-ngx. I set it up and it's cool, but why can't I just point it to my Documents folder? I'm getting all of my 2023 taxes ready and now I have to upload them into two places, paperless-ngx for my records and Nextcloud so I can ultimately share a link with my accountant.
Am I old man yelling at cloud-ing right now? Why get rid of basic folder structures I just don't get it
3
I got into the idea of selfhosting my photos, and wanted facial recognition to search them. I also wanted a selfhosted chat server. Nextcloud came as the obvious choice that did both. After days of tinkering and fixing errors in the log one by one, everything worked except the facial recognition which said everything was fine but the faces just didn't get recognised. Also the mobile experience for Memories wasn't the best. Then luckily I came across immich and it was up and running in about 5-6 mins of configuration max, and it has better facial recognition than the main big commercial option. Insane. For chat I got a synapse server with coturn which also took about 15 mins of docker composing and setting configurations/accounts to my liking.
(I still think Nextcloud is cool but it's overkill and loaded with too many features I don't need + installation is a task & documentation/online support communities are scattered between the various methods of installation)
6
I'm the opposite because I've had nothing but bad luck with docker. I should really spend more time with it but ugh
38It's definitely worth learning. I had the damnedest time with docker until I went to a meetup and had someone ELI5 to me. And it wasn't that I wasn't technical. I just couldn't wrap my head around so many layers of extraction.
The guy was very patient with me and helped me get started with docker compose and the rest is history.
14Abstraction?
6
Permanently Deleted
13I was the same with Kubernetes until I started using Lens to monitor the clusters.
5Honestly portainer isn't really necessary as you can just have some folders with docker compose.
0
I'm like that. It feels like a total waste of resources, and introduces unneeded complexity for backup, updates, file access, networking and general maintenance.
I would take a deb repo over docker any day of the week.
4What's wrong with it
1I think it's black magic but I also use containers at work so I'm biased.
0
For me it's more like new interesting self hosted project and then find out it's only distributed as a docker container without any proper packaging. As someone who runs FreeBSD, this is a frustration I've run into with quite a number of projects.
35Eh even as a Linux admin, I prefer hand installs I understand over mysterious docker black boxes that ship god knows what.
Sure, if I'm trialing something to see if it's worth my time, I'll spin up a container. But once it's time to actually deploy it, I do it by hand.
18Same. Frustrating when you have to go digging for non-Docker instructions.
7If it’s an open-source project, usually the dockerfiles are available for reading.
Do you audit every line of code that you run in production? If you are trying some new python/django/sql app, are you reviewing all that?
I’d assume with a python based project, you’d be able to at least look at requirements and tell there’s something that sets off red flags. And you are either familiar/trust the maintainer, or you are reviewing the actual python itself?
Beyond that, the dockerfile is essentially just installation instructions for getting it running on a virgin system of X distribution. I wouldn’t call that a black box.
If the container isn’t part of an open source project, then this is a moot point then. The project itself is a black box.
3
Does Qemu work for you?
2Virtualization in general? Sure, I can. I've tried it a bit with bhyve. But it's definitely a lot heavier since I'm now running a full Linux os and dedicating resources to it to run docker just to run a python or node app.
Learning the project is in Go though is a sigh of relief. Professionally I've moved to Go (from Python) just because it's so damn easy to build and distribute.
I just wish there was better support for the other *nix's. While the language support them just fine, docker on the other hand strangles it. =(
7
This oh my God. Just the other day I tried to install a project off git, it had a nice little .bat file to install all the requirements except half if them just didn't exist or were so niche I couldn't find anything on them after searching. Would love more dockers please.
33.bat?
*starts loading shotgun.
Surely you mean .sh, right?
51Ah well, maybe he used to much aliases? starts sweating in penguin costume
22Naw they only had windows projects. I run all my stuff through VMware. Gotta have windows for stupid easy anti-cheat. Trust me I only use it when I have to, please put the gun down mr railcar!
7
I believe this to be true for nearly all products. It has to be super simple to test, because you need to assess if it fits your needs. The mental model for a priori assessment is not strong enough usually.
28It’s because I’ve seen What people can do with a simple docker container that I completely agree. It’s too nice to go back.
27I'd agree more if most docker stuff didn't depend on running as root.
7
As someone that uses FreeBSD as its main server, it's kinda the other way around haha
14Masochist
5
Building a docker container isn't normally to hard. I usually will create a PR with a dockerfile and docker compose
4As a NixOS user, I pick whatever is supported well as a NixOS package.
4Sometimes I'm too lazy for that :p
2
Yeah nah no thanks I'm not wasting my time with that
4I was so surprised by how easy it was to install Yacy--I'd thought a self-hosted search engine would be tough, but I made a docker-compose file and pointed my reverse proxy to the server, works perfectly so far!
3Yeah no thanks I actually enjoy customizing my installs and not relying on docker for config management which it really shouldn't be used for.
Only container I have that was well worth it is the OSX vm which makes it easy to swap versions and options without having to coax the crappy apple software.
Which I also only have because I thought it'd be funny to demo bluebubbles to my friends.
0unpopular opinion docker is the worst creation in webdev besides js and react
-7Permanently Deleted
29I find docker to be very useful as it makes the environment highly predicable while allowing your code to run anywhere
14Explain?
7I despise docker/containers.
1Docker for webdev? You know that Docker is server side right?
1
Stop pushing the popularity of Docker. It is proprietary software and runs completely opposite to the ideals of GNU/Linux.
-31Docker is open source, licensed under Apache-2.0. Not really sure what you're talking about.
23While docker is open source I have no idea why systemd nspawn containers aren't more popular. Most systems have this built in without needing to install 3rd party software. And I find using it so much easier. I assign each container an IP address and manage them all with ansible. It provides isolation and convenience while not trying to reinvent the wheel.
6