[Slackbuilds-users] New server for SlackBuilds.org

Robby Workman rworkman at slackbuilds.org
Sun Apr 30 20:19:42 UTC 2017

Top-posting this...

We're working on a contributors/ page now. Once again, we'd like to
say that our community is excellent. The new hardware is on order,
and once it's arrived and set up in the DC, we'll begin the fun
process of getting everything configured to make the switchover.
There will almost surely be some downtime associated with that,
but we'll provide as much advanced notification of that as we 
are able.

For the record, we have enough to send Pat a non-trivial amount
as a donation and keep a small cushion in the account just in
case there are unexpected out-of-warranty hardware issues later.

We'll leave the paypal link active in case anyone is inclined to
use it in the future, with the current plan being to keep that
cushion in place and forward any excess to Volkerding (after all,
Slackware is the reason this project even exists).

Sincere thanks to everyone who donated - we are honored that so
many think this little project is useful and worthy enough to
support. Without minimizing the impact of any other contributions,
we'd like single out one contributor in particular, if only due
to the fact that we were (pleasantly) surprised:
Distrowatch.com donated $400 to the effort! Thanks, Unsigned
Integer Limited :-)

Anyway, once we have the contributors page finished, we'll post
a note here for everyone to review it and suggest changes to it
(e.g. misspellings, name changes, remain anonymous, hyperlinks,

Thanks again, everyone, and happy Slacking!


On Wed, 26 Apr 2017 21:19:33 -0500
Robby Workman <rworkman at slackbuilds.org> wrote:

> SlackBuilds.org users,
> It's apparently time to again do something that I don't like doing.
> The server that hosts our website and rsync, well basically all of
> the things except DNS, mail, and mailing lists, as well as the
> slackwiki.com site, is showing its age.  You might have noticed
> some temporary downtime over the last couple of weeks due to httpd
> getting overloaded. The datacenter hosting us, onyxlight.net, is
> going to provide us with a new Dell R610 server with dual six-core
> processors and a fair amount of RAM. However, we have to buy our
> own drives and we'd like to add some more RAM to it [1].
> They (onyxlight) can get us six 900GB 10k RPM SAS drives for a
> little over $200 each with a one year warranty, and we can put
> about 48GB of RAM in there for another $360. With tax/shipping,
> we need about $1700.
> As I said before, I hate asking the community for money - that's why
> we've never had a donation button or anything along those lines; I'd
> rather wait and put out the beggar's bowl when we don't have a choice.
> Well, here it is.
> I created a paypal account for the project, and both erik and I
> (the project founders) will have access to it. Once we get enough
> for this current expense, I'll post an update here and we'll look
> at creating some sort of "contributors" page on the site to give
> much-deserved accolades to everyone who helps out. Any extra funds
> above what we need will be used wisely, but we've not really
> figured out what to do with them - we really don't have any ongoing
> expenses (onyxlight is awesome, ya'll, in case you haven't gathered
> that much already). We'd like to do something for Pat, of course.
> Ultimately, I hope we've earned enough of your trust over the years
> to know that we'll use whatever we get in a manner of which you will
> approve; if not, then the best advice I can give is to not donate.
> If I've not scared you off yet, you can donate by going here:
> https://paypal.me/SBoDevel
> -RW
> [1] In case you're curious, we're planning to compartmentalize
>     most services into virtual machines; essentially, each of
>     the network-facing services will be in its own VM such that
>     just in case there's a breach in one part, it's less likely
>     to affect other parts. There's also the benefit of an easier
>     upgrade path for various parts - if a particular service
>     can benefit from (or requires) a newer release of Slackware,
>     we can spin up a new VM, get it working there, and then
>     migrate over all at once with minimal downtime. At the very
>     least, it sounds like a good plan :-)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170430/b442c7c8/attachment.asc>

More information about the SlackBuilds-users mailing list