<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote gmail_quote_container"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><br><blockquote type="cite">
<div dir="auto">
<div dir="auto">...<br>
</div>
<div dir="auto">Would you like a hand building up some DR or
deployment automation so you can avoid needing to remember
settings? IT automation is one of my primary skillsets, so if
you'd like any sort of help setting it up, let me know. For
instance, it's not too hard to put together automation scripts
to run on a provisioned box to stand up the web server, ftp
server, etc so that you don't need to manually edit files and
the like.</div>
</div>
</blockquote>
That would be useful. That could be a way to escape my dependence on
and fight with Plesk.<br></div></blockquote><div><br></div><div>Let me know what your needs are, and we can work together to put something in place to manage things.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>
<blockquote type="cite">
<div dir="auto">
<div dir="auto"><br>
</div>
<div dir="auto">Alternatively, have you considered an
alternative way to host the data? You could probably build a
Container image with all the files in it and host that on
something like Amazon Container Service or any of the many
cloud Kubernetes hosts around. A container image would also
make it easy for someone to grab the whole collection and make
it available in an offline context the way they can with the
old CD images Troy used to distribute. <br>
</div>
</div>
</blockquote>
I have looked at alternatives in the past, but it may be worth
looking again. When I last looked, AWS was more expensive at my
traffic levels and site counts than using a rented dedicated server.
Another alternative might be hosting at my house when (if?) Hawaiian
Telephone makes good on its promise to bring fiber Internet to my
neighborhood. (It is actually available about a half mile away,
right now, but I haven't seen them working on it around here.)<br></div></blockquote><div><br></div><div><div><br></div><div>Here's one example: <a href="https://src.thehellings.com/greg/sword-container">https://src.thehellings.com/greg/sword-container</a></div><div><br></div><div>You
can use this repository to build a (Docker, Podman, Kubernetes, etc)
container that serves up any repository over HTTP. I've built example
repositories that each contain modules from CrossWire's main repo,
Xiphos's repo, and your eBible.org repo. Running one of the pre-built containers locally with the
command `podman run -it -p 8080:80 --rm
<a href="http://registry.thehellings.com/greg/sword-container/http-ebible.org:latest`">registry.thehellings.com/greg/sword-container/http-ebible.org:latest`</a>
will make a copy of your eBible.org repository available locally over
HTTP on port 80. Rebuilding the container just requires you to put the
Containerfile and nginx.conf file in the same folder as your mods.d and
modules folders and do a podman build or docker build.</div><div><br></div><div>Anyone can use this to build up a container image to serve any repository content that they want from their local machine, not just those 3 repositories. It can make a very simple way for people to share custom modules or install across a network without needing to fully understand configuring a web server or FTP server on their local system. Just a pair of build/run commands and they can be up and running.</div><div><br></div><div>It might be worthwhile keeping an image around so you can quickly get a system up and running in the case of a future disaster recovery. Similar work can be done with a container to serve FTP content.</div><div><br></div><div>--Greg</div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>
<blockquote type="cite">
<div dir="auto">
<div dir="auto"><br>
</div>
<div dir="auto">Or even put the files into an object storage
container if you're dedicated to eliminating FTP access
eventually. With just a small shell script you can push the
needed files and their indexes into an S3, Ceph, etc object
storage service and then you wouldn't need to run a dedicated
server with them to manage uptime. All of those services offer
ways to expose the files over HTTPS.</div>
<div dir="auto"><br>
</div>
<div dir="auto">As I said on Facebook, I'm happy to lend a hand
if there's anything I can do to help smooth your
infrastructure! I can even host an emergency mirror if need
be, as I have pretty reliable Internet and electric when my
neighbors don't drive into the electric poles. This year I'm
dedicating some of my time to working on home electric
backups!</div>
</div>
</blockquote>
<p>Thank you, Greg. I may take you up on that...</p>
<div>-- <br>
<p><font color="#000000">Peace,<br>
<b><big><i>Michael Johnson</i></big></b></font><b><br>
<font color="#000070">
26 HIWALANI LOOP • MAKAWAO HI 96768-8747</font></b><font color="#000070"> • USA<br>
<a href="https://mljohnson.org/" target="_blank">mljohnson.org</a> • <a href="https://eBible.org" target="_blank">eBible.org</a> • <a href="https://WorldEnglish.Bible" target="_blank">WorldEnglish.Bible</a> • <a href="https://PNG.Bible" target="_blank">PNG.Bible</a><br>
Signal/Telegram/WhatsApp/Telephone: +1 808-333-6921<br>
Skype: kahunapule • Telegram: @kahunapule • <a href="https://www.facebook.com/kahunapule" target="_blank">Facebook:
fb.me/kahunapule</a></font></p>
</div>
</div>
</blockquote></div></div>