62
Cost-cutting tips?
(discuss.tchncs.de)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 11 Oct 2023
62 points (98.4% liked)
Selfhosted
37779 readers
590 users here now
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:
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS
My favorite cost cutting tip is to avoid big webapps running on docker, and instead do with small UNIX utilities (cron instead of a calendar, text files instead of note taking app, rsync instead of a filehosting dropbox-like app, simple static webserver for file sharing, etc). This allows me to run my server on a simple Raspberry Pi, with less than 500mb of used RAM in average, and mininal energy consumption. So, total cost of the setup:
With that, I run all services I need on a single machine, and I have a backup plan for recovery of both hardware and software.
Getting used to a UNIX shell and to UNIX philosophy can take some time, but it's very rewarding in making everything more simple (thus more efficient).
What do you mean by that?
Do you use crontab to save events?
Basically, yes. You can configure most cron programs to mail task output to you (it's usually done by setting the
MAILTOvariable in the crontab, provided sendmail is available on your system).I use that to do things like:
It sends me a mail, and I can see the upcoming events with
crontab -l. If it's not a recurring event, I then delete the rule.And to expand further on simplicity, one can avoid using email and send messages over ntfy with just a POST curl call.
I like your setup!
This is excellent. Thank you
Damn, I'm doing *nixes for nearly 30 years. But never went to that level of minimalism. Nice trick.
Yeah, and that's the problem for me. See my comment above. Nextcloud and those services are "bloated", yes, but very convenient. I never worked in an IT-environment, so I'm a total noob.
But stuff like NC AIO give me a whole pre-set-up LAMP stack without needing to know how everything works, and that's unbelievable for me.
Honestly I've worked in technical fields (either support or engineering) for most of my life and sometimes I don't feel like reinventing the wheel. Sure I could combine rsync and crontab and sync files around that way on a regular basis, add lighthttpd for web browser access to the folder, and I do sometimes, but I'd also like to do things OTHER than more work. I know how to do those things, but I don't want to do those things.
Ask yourself what part of this is your hobby. Is it building the thing and making it do as much as possible with as little as possible? Is it getting a self hosted cloud that's polished like Google's? Is it something else like photography or music and this is just the way you want to share or archive that? Those are all three different scenarios and is make different suggestions for each.
The usage for curl is quite interesting. Personally, perhaps I'd like a simple GUI where I can select the date and time and the message for the reminder.
I use
nfsor samba for filesharing, but a webserver works well too.What is your opinion on OCI container orchestration tools? Specifically Podman. I am of the opinion that containerisation is a most excellent idea because it uses hardware to the fullest extent without polluting the base system. Also the "use like cattle" philosophy. For example: I would be much more comfortable having the GUI for
cronin a container.