johnnixon

joined 1 year ago
[–] johnnixon@rammy.site 2 points 1 year ago

That looks really good. I'll run this in docker and see if it works for our use case.

[–] johnnixon@rammy.site 1 points 1 year ago (1 children)

A fair question. The goal is to have a dozen different people able to input information. It should have some metadata so I can filter by every type (guest log, significant event, employee late to work, delivery, etc). A flat text file wouldn't do that. Plus it needs to be pretty idiot proof for the non savvy users.

 

I'm looking to replace the log book at work. I thought somebody must have made a simple docker container that allows someone to put in entries into a database for things like daily activities, guest logs, maybe even tracking fuel deliveries. Is there anything out there or and I going to need to remember how to make websites? Is been at least a decade.

I'm open to any other cloud solution as well.

[–] johnnixon@rammy.site 1 points 1 year ago (1 children)

Yes, that was the problem. I got it running in a LXC and it worked fine. Docker remains a hot mess for 90% of what I'm trying to run.

[–] johnnixon@rammy.site 1 points 1 year ago (2 children)

Sometimes you can't change the external port because it has to be where it's expected. Regarding being stuck in the community repo, try having up be restricted to what's available for LXC documentation.

I guess I could follow a 30 minute CLI procedure to spin up a container or I can run a command or two in Docker. If Docker simply had it's networking straight without having to do Linux surgery with oven mits on this wouldn't be a problem.

[–] johnnixon@rammy.site 2 points 1 year ago (5 children)

Pihole seems pretty unhappy about sharing an IP address/ports with it's Ubuntu host, so yeah, I'm set on giving it it's own IP.

 

I'm trying to get back into self hosting. I had previously used Unraid and it worked well to run VMs where needed and Docker containers whenever possible. This biggest benefit is that there is an easy way to give each container it's own IP so you don't have to worry about port conflicts. Nobody else does this for Docker as far as I can tell and after trying multiple "guides", none of them work unless you're using some ancient and very specific hardware and software situation. I give up. I'm going back to Unraid that just works. No more Docker compose errors because it's Ubuntu host is using some port requiring me to disable key features.