I just was playing around with the Docker options on a Synology NAS (an x86 model - a DS720+) and trying to get Synchronet
installed on it. Seems that there's a whole whackload of common service ports that are reserved in Synology's DSM NAS OS
installed on it. Seems that there's a whole whackload of common service ports that are reserved in Synology's DSM NAS OSthat's why i built my own nas. to be honest, only thing that's actually good on the synologies are the UX, but freenas is just as good.
that require a lot of workarounds, even when you're not using those services on the NAS. I'm just wondering if anyone has
easier. Anyway, if anybody has any tips from their own experience, I'd welcome them, otherwise I'll just continue on with
the VM that I'm working with.
I just was playing around with the Docker options on a Synology NAS
(an x86 model - a DS720+) and trying to get Synchronet installed on
it.
Seems that there's a whole whackload of common service ports that are reserved in Synology's DSM NAS OS that require a lot of workarounds,
even when you're not using those services on the NAS. I'm just
wondering if anyone has any experience with that kind of deployment
and what kind of problems you ran into
and the conclusions you got to at the end of it all. I didn't spend
a whole lot of time on it, but I did try rerouting some of the web
ports, although I ended up getting the built-in nginx web server
giving remote application errors. I just found that using a full VM
is a whole lot easier.
Anyway, if anybody has any tips from their own experience, I'd welcome
them, otherwise I'll just continue on with the VM that I'm working
with.
personally, i wouls go with a VM or even an LXC container. an LXC
container might work well. I know it runs in one as that's what I
started running mine on while i was sourcing hardware. but that's
also probably because i have no idea about docker and have never
used it lol
started running mine on while i was sourcing hardware. but that'sDocker is mostly some really nice tooling around LXC and a few other pieces.
also probably because i have no idea about docker and have never
used it lol
used it lolDocker is mostly some really nice tooling around LXC and a few other pieces.
to be honest. as i say, never used it.. I just run lxc containers in my proxmox node for most my little things (torrent, apt mirror etc) the others i run full vms.
to be honest. as i say, never used it.. I just run lxc containers in my proxmox node for most my little things (torrent,some people are really into docker and some arent. I am fine with just running vms when i need to do something.
apt mirror etc) the others i run full vms.
some guy made a linux docker vm out of a windows rengade bbs i setup with a bunch of windows shit and made a big mess solol that's irony. I was just playing around with renegade last night in a DOS VM LOL I found my old ezycom stuff and my key, but started off playing around with renegade when i couldn't get ezy going because apparently my 1st gen key is no good for the last gen s/w lol
that spoiled it for me in the beginning. it just seems overcomplicated to do a docker container than setup something in a
vm.
lol that's irony. I was just playing around with renegade last night in a DOS VM LOL I found my old ezycom stuff and my key, but started off playing around with renegade when i couldn't get ezy going because apparently my 1st gen key is no good for the last gen s/w lol
if you want a ezycom reg code you can use the one i have for ezycomBBSv2.15g2
okay i just looked and now my reg code no longer works. so he did some weird stuff where my free code i requested only worked for a short time or something else is up. the guy who took over was a do-nothing and he was very weird about registrations so he probably did some funny business.
some people are really into docker and some arent. I am fine with just running vms when i need to do something.
some guy made a linux docker vm out of a windows rengade bbs i setup
with a bunch of windows shit and made a big mess so that spoiled it
for me in the beginning. it just seems overcomplicated to do a docker container than setup something in a vm.
Re: Re: Anybody ever try installing Synchronet on a prebuilt NAS viaDocke By: Charles Blackburn to MRO on Fri Sep 23 2022 07:11 am
lol that's irony. I was just playing around with renegade last night in a DOS VM LOL I found my old ezycom stuff and myyou don't really have to use renegade in a dos vm unless you are just playing around. you can make one that works in windows
key, but started off playing around with renegade when i couldn't get ezy going because apparently my 1st gen key is no
good for the last gen s/w lol
xp [don't do that] windows 7 or windows 10 32bit.
if you want a ezycom reg code you can use the one i have for ezycomBBSv2.15g2
okay i just looked and now my reg code no longer works. so he did some weird stuff where my free code i requested only
worked for a short time or something else is up. the guy who took over was a do-nothing and he was very weird about
registrations so he probably did some funny business.
if you want a ezycom reg code you can use the one i have for ezycomBBSv2.15g2
okay i just looked again and i needed to type in the fake sysop name i registered with. somehow it cleared out.
i talked to T1ny and he is going to ask the guy for a free code for everyone
to use. the author had the ole harddrive crash no backup thing.
Might be easier to think of it as really lightweight
application-specific VMs. In general it becomes a lot less complicated
in practice.
If I want to use a database, I can just spin up a container, I don't
need to worry about dependencies, or what they might do for my host
OS... and for more esoteric apps even more so.
Upgrades become easier too... since my data is outside the container, I
just stop, update to a newer image, and start with the same data directory... not separate OS upgrades, dependencies or application
updates all of which can effect one another and break in unexpected
ways. The application, database, server all have software that they
need and works together. Yeah it can take more storage overall, but with
a layered file system, containers with the same base image don't take up extra room.
Biggest headaches come from software that isn't designed to separate
data, configuration and application binaries/scripts. This becomes a
bit more difficult to byzantine under the covers... in the end it's
about presenting a more seamless experience overall though.
If you pink me on FB Messenger, I'd be happy to do a screen share, where
I can show you how I can connect/manage update etc my BBS in practice.
yeah i what how it is and how it works pretty much. i've played with
it. i've used some docker containers when playing around.
If you pink me on FB Messenger, I'd be happy to do a screen share,
where I can show you how I can connect/manage update etc my BBS in
practice.
i dont know what you mean by pink. i dont really use facebook or fb
msger that much.
i dont know what you mean by pink. i dont really use facebook or fb msger that much.
I meant "ping"
Sysop: | fluid |
---|---|
Location: | wickliffe, ohio |
Users: | 5 |
Nodes: | 10 (0 / 10) |
Uptime: | 201:31:35 |
Calls: | 50 |
Files: | 15,838 |
Messages: | 50,741 |