Yes, through Namecheap. Right now it's just hosting my personal site on WordPress, but I'm going to switch that soon due to Matt Mullenweg's drama or just take it down entirely.
I read the details. He has a decent reason to ask WP to pay as they got brought by private equity and significantly dropped their contributions to the WordPress which is open source and hence relies on the community to feed back into the product.
Ask, sure. Sue, maybe. Commandeer extensions, absolutely not.
If they don't like people using their open source project, they shouldn't offer that license.
You can always encrypt the backups you upload there.
Depending on the specs of the shared webspace it is possible to install some php based webdav software to easily sync files with it. KaraDAV for example.
$11/m is a lot. If you just want a small site on shared hosting, try namecrane.com. For storage use Hetzner Storage Box.
If there was a way I could leverage the unlimited bandwidth/storage as an offsite backup, that would be amazing, but I'm not sure it would be a great idea backing up stuff to a webserver where there best security I can add it via an .htaccess file.
Your off-site backup solution shouldn't have to care about that level of security because you should be encrypting your backups before they leave your network. Even if you have a solid backup host in the cloud, you still want to encrypt your backup data before you send it to their hosted repo.
Unless your vendor has a reason to read your backups, they shouldn't be able to.
Fair point. Currently, everything that requires off-site backup is sent to my father's Synology using hyperbackup. So off-site is sorta self-hosted already. Was thinking in terms of a second fallback option.
As others said, encrypt your backup before sending it to your server. And can't you upload the files to a folder outside of a document root or better outside of the www folder so there is no way to access it through the web server service?
I can upload files outside of the docroot, but if they stay there for too long, I get a nasty email from Dreamhost reminding me that this is for web space and not offsite storage (something they also sell). I haven't tried uploading something inside the docroot and just setting permissions to 400 or something!
Oh and regarding the large TIF files, what limits are you hitting? Most hosters allow to change the php settings like memory limit or max execution time.
I haven't played w/ memory limits, but when I tried messing w/ buld download of raw TIF files, it ran out of memory pretty quick. I may look into what I can to about the limits, though.
I did some experiments in the past. The nicer option I could find was enabling webdav API on the hosting side (it was an option on cPanel if I recall correctly, but there are likely other ways to do it). These allow using the webserver as a remote read/write filesystem. After you can use rclone to transfer files, the nice part is that rclone supports client side encryption so you don't have to worry too much about other people accessing files.
This is really helpful. I’ll look into that. Thanks!
I technically still have a hosted website, but it's rarely updated anymore. It's very low priority compared to my self-hosted stuff.
Same. I have a mediawiki install on the shared hosting still, but I haven't updated it in forever. For the $10.99/month I'm paying for shared hosting, I could save a little and do a more powerful VPS to host similiar stuff... Of just keep doing what I'm doing w/ my S12 pro & Synology. Might look at some kind of failover down the road.
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!