Soloakel I seen but I have no way to help right now. I'm broke and my bank doesn't do digital transactions. I have a plan to get my mum to send money from me but I won't have that money for a long time yet.
Soloakel I seen but I have no way to help right now. I'm broke and my bank doesn't do digital transactions. I have a plan to get my mum to send money from me but I won't have that money for a long time yet.
I was able to contribute $10 and linked the office workouts to my HR department to send out, as our company theme this quarter is physical and mental wellness. If they send it out, it will be to roughly 1,000 employees.
Donating a $1 or $2 , or $5, is still helping out. I think sometimes when we think of donating, we think we have to give more. If everyone were to donate whatever they can, even if it's just $1, that's still all going to add up. It's like everything else on Darebee, it's about teamwork.
Shame to see this site at critical funding, but taking a quick look at the site settings there might be a few things you can do to quickly reduce bandwidth usage, and potentially things like bandwidth charges (or over-bandwidth charges) etc. If it does reduce it, it might mean you're able to reduce to a lesser server spec and save costs that way.
Not sure who this should go to so if anyone can tag-in the relevant member please do.
Set HTTP Cache Headers
- you can likely remove pragma: no-cache as it's essentially meaning any older browsers will request a fresh copy of all resources on every page load (e.g. images, html, JavaScript files)
- change from Cache-Control from no-store, no-cache, must-revalidate, post-check=0, pre-check=0 to something like Cache-Control: no-cache, private, max-age=1000 which will allow content to be cached within a browser for 1000 seconds
- you should likely also add X-Frame-Options: SAMEORIGIN for an unrelated issue
You may want to set the cache for different asset types, and also check how this works with the forum part of the site, but I think you're with Liquidweb so they might be able to advise on some caching setup.
This could further reduce your outgoing bandwidth and reduce charges, but may need some tweaking so it doesn't affect the forum or various parts of the site.
Host Static Content on a CDN
You could use a service such as https://www.digitalocean.com/products/spaces/ for a certain portion of your resources (e.g. PDFs, .zips, images) which could further reduce bandwidth depending on how much you currently use up. Looks like Digitalocean spaces charges $5 per month for 250GB of storage, 1TB of outbound transfer per month, then $0.01 per additional GB transferred after that.
Infrastructure changes might take some trial and error but depending on how much you're currently paying for hosting each month, changes like these could genuinely help you stay out of the critical zone for longer periods.
Shame to see this site at critical funding, but taking a quick look at the site settings there might be a few things you can do to quickly reduce bandwidth usage, and potentially things like bandwidth charges (or over-bandwidth charges) etc. If it does reduce it, it might mean you're able to reduce to a lesser server spec and save costs that way.
Not sure who this should go to so if anyone can tag-in the relevant member please do.
Set HTTP Cache Headers
- you can likely remove pragma: no-cache as it's essentially meaning any older browsers will request a fresh copy of all resources on every page load (e.g. images, html, JavaScript files)
- change from Cache-Control from no-store, no-cache, must-revalidate, post-check=0, pre-check=0 to something like Cache-Control: no-cache, private, max-age=1000 which will allow content to be cached within a browser for 1000 seconds
- you should likely also add X-Frame-Options: SAMEORIGIN for an unrelated issue
You may want to set the cache for different asset types, and also check how this works with the forum part of the site, but I think you're with Liquidweb so they might be able to advise on some caching setup.
This could further reduce your outgoing bandwidth and reduce charges, but may need some tweaking so it doesn't affect the forum or various parts of the site.
Host Static Content on a CDN
You could use a service such as https://www.digitalocean.com/products/spaces/ for a certain portion of your resources (e.g. PDFs, .zips, images) which could further reduce bandwidth depending on how much you currently use up. Looks like Digitalocean spaces charges $5 per month for 250GB of storage, 1TB of outbound transfer per month, then $0.01 per additional GB transferred after that.
Infrastructure changes might take some trial and error but depending on how much you're currently paying for hosting each month, changes like these could genuinely help you stay out of the critical zone for longer periods.
Comment