disk space shortage.

i did some optimizations so docker would clean up after itself a little better. but i haven’t done a full dig.

i’d love some backseat sysadmin honestly.

2 Likes

+1 I would happily contribute as well

You might want to choose one or two volunteers to take a look. Just like it can be tough to see the road from the backseat, it can be tough to give server administration advice without SSH access.

3 Likes

gandi maybe ?

+1

I’ve just started donating to muffs for the same reason I’d be happy to donate here

even back to the original forum days this place has been a great help in so many ways

that being said I would be zero help with the server stuff otherwise :slight_smile:

just throwing this out there - a patreon account, which enables a monthly contribution to anyone, would be perfect for this. each of us who could afford it would only need to put in a couple bucks a month, and patreon would take care of the routing, withdrawls, etc. I use it to donate monthly to a podcast I love, and it works great without me having to remember to do anything.

6 Likes

just moved the server do a smaller DO droplet. now saving several hundred $ per year.

please let me know if anyone notices issues. e-mail info@monome.org is something is really super busted.

4 Likes

great news - glad that seems to have gone smoothly!

1 Like

over the last day or so, Ive been getting timeouts and often quite slow access, seems to be particular the initial connection - I’ve never had a problem in the past.
is this just me? or perhaps regional issue? (Im in southern Spain)

cpu, bandwidth, and disk have been reliably untaxed over the last 24 hours. may be a hiccup somewhere on the way to the server. let me know if it persists.

1 Like

Is there any chance we could move to using 100% HTTPS? Let’s encrypt certs are free and easy.

2 Likes

if you could point me towards some way to set this up for the discourse software, i’d be happy to do it.

https://meta.discourse.org/t/setting-up-lets-encrypt/40709/185 seems a little thorny

Not sure if you’re using nginx outside of docker, but if you are this guide is pretty swell. I’ve used the same for my own DO droplet.

ran out of space again today.

cleaned up a bit but we’re close to the edge. hopefully it’ll make it until tomorrow morning when i can really check out what’s the best approach.

i moved the DO server to a location that supports their new “Volumes” feature but integration might be a pain. will post updates here.

if space is an issue, the first thing that comes to mind is disabling binary uploads; images, audio files, zipped patch attachments. keep the db text-only. require 3rd-party hosting for those files, at least in the short term.

1 Like

should be able to do this tomorrow:

1 Like

added 40gb for uploads at minimal cost.

1 Like

just seen this after trying to upload images.

i edited the post but i can’t seem to be able to upload them. (nothing to worry about though, just gorgeous pictures of birds flying patterns)

1 Like

Yeah.
Something must be still happening:
I am seeing a lot of missing images, including avatar images (mine and others).
Perhaps the move/expansion is still propagating?