4 ms·

1) what is your budget? 2) how much stuff are you planning on hosting? 3) how much bandwidth do you need? nextcloud was (I've not checked recently) very hard

1) what is your budget? 2) how much stuff are you planning on hosting? 3) how much bandwidth do you need? nextcloud was (I've not checked recently) very hard to secure properly, so you'll probably want to hide it behind a VPN or some such. The other thing to think about is the amount of time you have budgeted for initial setup, and on going maintenance. you will need to have backups, and those backups need to be tested. For hosting, you need disk space, so if you have enough bandwidth at home, its car cheaper to have a low power server with a couple of big disks in it, than it would be to host that data on S3/other block storage. AWS will be much more expensive than linode or DO. assuming you are not using the managed services. finally, I would advise getting your physical instances controlled via ansible or terraform, and if you are using docker, get that config in some sort of repo, so you can teardown and bring up your infra on demand. This make disaster recovery much easier (or porting)

dspillett 4y ago
> nextcloud was (I've not checked recently) very hard to secure properly I've not heard of nextcloud being particularly onerous to lock down, compared to other systems of its ilk (and it should be easier than securing something string together from smaller parts). The main trick with “standard” packages like these, once you've done the initial hardening, is making sure you keep bang up-to-date with security patches from upstream. > its car cheaper to have a low power server with a couple of big disks in it, than it would be to host that data on S3/other block storage Though a good block storage provided should give your data more redundancy and a lower time-to-recovery than a pair of old drives in RAID1. Of course, you still want good backups on another provider, just in case. Check performance too: some block storage providers might be notably faster (SSD/RAM cached storage etc) or much slower (mostly traditional drives, high levels of contention on the storage arrays, latency between your app and the storage array) than those inexpensive local drives.
jtode 4y ago
1) Enough for what I'm proposing to do 2) My personal data. Who knows. Might end up needing a TB or more by the time I'm done snapshotting and whatnot, this is gonna be a process. 3) Enough lol Sorry to be flip, but at this point I have more abstract targets: -hoover up all photos taken by all my devices and place them in a central backup place with both cloud and local storage. Ideally some nice UI for browsing and organizing and such. -replace Google Docs/Sheets functionality, including public internet accessibility (though I may do the VPN, or an SSH tunnel maybe, these are not bad ideas at all) with a server I control. And yes, handling it with my own scripts and such has occurred to me as well, but you know how that ends up going. Nextcloud seems to be a popular tool that does these things. That's what I know. There's been a number of interesting suggestions in the comments that I'm now gonna look into before I act, though.
aborsy 4y ago
Can you clarify how nextcloud is very difficult to secure properly? I haven’t heard of such thing.

dspillett 4y ago

> nextcloud was (I've not checked recently) very hard to secure properly I've not heard of nextcloud being particularly onerous to lock down, compared to other systems of its ilk (and it should be easier than securing something string together from smaller parts). The main trick with “standard” packages like these, once you've done the initial hardening, is making sure you keep bang up-to-date with security patches from upstream. > its car cheaper to have a low power server with a couple of big disks in it, than it would be to host that data on S3/other block storage Though a good block storage provided should give your data more redundancy and a lower time-to-recovery than a pair of old drives in RAID1. Of course, you still want good backups on another provider, just in case. Check performance too: some block storage providers might be notably faster (SSD/RAM cached storage etc) or much slower (mostly traditional drives, high levels of contention on the storage arrays, latency between your app and the storage array) than those inexpensive local drives.

jtode 4y ago

1) Enough for what I'm proposing to do 2) My personal data. Who knows. Might end up needing a TB or more by the time I'm done snapshotting and whatnot, this is gonna be a process. 3) Enough lol Sorry to be flip, but at this point I have more abstract targets: -hoover up all photos taken by all my devices and place them in a central backup place with both cloud and local storage. Ideally some nice UI for browsing and organizing and such. -replace Google Docs/Sheets functionality, including public internet accessibility (though I may do the VPN, or an SSH tunnel maybe, these are not bad ideas at all) with a server I control. And yes, handling it with my own scripts and such has occurred to me as well, but you know how that ends up going. Nextcloud seems to be a popular tool that does these things. That's what I know. There's been a number of interesting suggestions in the comments that I'm now gonna look into before I act, though.

aborsy 4y ago

Can you clarify how nextcloud is very difficult to secure properly? I haven’t heard of such thing.