Hi, yes this is mentioned on the installation page of the website, below the Docker instructions. The app can be installed Dockerless using go install; if you choose this option you’ll have to provide and configure Postgres and Redis instances for the app to connect to. That said, Docker is the recommended and easiest option.
Shdwdrgn@mander.xyz 1 year ago
Looks like a fun project, but will you be providing any info on setting it up from scratch? I just don’t have an interest in docker containers.
mgdigital@lemmy.world 1 year ago
Shdwdrgn@mander.xyz 1 year ago
I saw that, but didn’t recognize the ‘go’ command as anything available on Debian. Just did some quick digging though and now I see it’s a new language and I believe I have an idea how to get it installed for compiling so I will give that a shot.
paris@lemmy.blahaj.zone 1 year ago
Golang v1.0 was released in March of 2012. Not sure I would consider it a new language.
Shdwdrgn@mander.xyz 1 year ago
Oh interesting… I thought I read something that said 2017. No worries, I’ll get it figured out now that I understand what it is.
cyberpunk007@lemmy.world 1 year ago
Out of curiosity, why not? I’ve come around.
Shdwdrgn@mander.xyz 1 year ago
I’ve just always used VMs for everything and set up each service to match my existing system. For example, my postfix servers have to all tie in to LDAP, mailman, and the host of services for authenticating email. It seems like the point of docker is to just have a completely preconfigured and self-contained setup. I guess I Just don’t see how that would work in my environment where I already have some services like databases or LDAP already running elsewhere, and I run multiple instances for redundancy. And if I have to reconfigure all that stuff in docker anyway, how is that any better than simply using my existing VMs?
cyberpunk007@lemmy.world 1 year ago
Used to be like you, then I moved from truenas core to scale where it’s now Linux and docker instead of freebsd and iocage jails.
So docker has this concept of persistent volumes. You configure all your settings in the initial setup command (docker compose) and define persistent volumes. This way you don’t lose your data.
Here’s an example, Plex. I run Plex in docker now. So my config directory is defined as a persistent volume. If I need to update Plex, or rebuild it or whatever, the container just updates and has all the data I need via the persistent volume. If the install is messed up or whatever I just get a newer image and run the docker compose and it fires up and mounts the persistent volume and off I go.
Basically it takes away the burden of having to figure out the OS configuration. Makes backups easier - and smaller. And the things are spun up, installed, and usable in seconds.
Shdwdrgn@mander.xyz 1 year ago
Not sure the OS configuration is really a burden :-) I have several servers I have to keep up to date anyway. And backups aren’t really an issue, I just run rdiff-backup on everything to provide a year’s worth of incremental backups, which doesn’t really take much extra space. Maybe one of these days when I catch up on other projects I’ll look into it though.
Dasnap@lemmy.world 1 year ago
I personally love containers (probably because I use them for work) but I can understand someone not wanting another layer of abstraction if they’ve worked bare-metal for a long time.