Jump to content

metRo_

Members
  • Posts

    8
  • Joined

  • Last visited

Reputation Activity

  1. Like
    metRo_ reacted to forestj in Self-hosting micro- (or regular) services, containers, homelab, etc.   
    I have been self-hosting my blog (ghost), git server (gogs), and a few other small things for years: https://sequentialread.com/.  I'm not using an SBC for it, rather a very old dell desktop, but I think the principle is the same. I use docker-compose to run the apps on my server.  I worked as a DevOps engineer for a couple years so I am intimately familiar with docker and linux containers in general.   So to me, setting up containers and what not (anything which is done inside the OS of the server) is the super duper easy part, its highly automatable, it can all be defined with code, like with ansible for example. 

    I think there are 2 main pain points for self hosting, both of which don't really have any great solutions out there on the world wild web:
     Configuring your router is a pain in the butt, especially for non-technical people & may not be possible for many users.  If you want to use your self-hosted services for something "mission critical" like email, you probably are going to want monitoring, observability, automated failover, etc.  These things are really complex and hard to set up, there's no "ez mode" button or framework that one can use, especially not anything designed for self-hosting. I actually started a project to try to address those pain points, starting with #1.  I wrote a bit about it years ago here: https://sequentialread.com/pragmatic-path-towards-non-technical-users-owning-their-own-data/
    I also decided to try to coin a term to describe what I'm trying to create, a "personal datacenter", basically like a personal computer, but instead of having a screen, keyboard, and mouse, it's a web server or group of web servers that are accessible on the public internet, and one can easily run various "apps" on these servers to make a blog, email server, online store, git server, etc.   I know  there are already other projects out there like nextcloud, freedombox, yunohost, etc, but I don't think any of those projects really address the hard pain points of self hosting, the network routing setup & failover.   I don't wanna go too much in depth with my project here, I'll probably make my own thread about it at some point. I don't quite have enough done to show it off properly yet
     
  2. Like
    metRo_ reacted to TRS-80 in Run Homeassistant on tinkerboard on SSD   
    I mean, you can do whatever you like. 
     
    But I never had problems with my few boards with Armbian running on sdcard nor eMMC.  However I make sure I take care of all important details like buying only certain brand name sdcards, and only from known good suppliers (which no longer includes Amazon, IMO), checking them thoroughly upon arrival, using good power supplies, etc...
     
    Basically everything in Getting Started section of docs.  Which I would hope you have read by now.  We wrote those for a reason, you know. 
     
    I never tried running from SSD, nor saw the benefit of that (and usually prefer to save my few available SATA / USB slots for hooking up storage drives) so I would be interested to hear anyone else who does that or thinks it's a good idea.  Now, I could be wrong, but my perception so far is that's not too common?
     
     
    By default, Docker will run as a service by the OS, storing it's images on whatever media that the OS is installed on (usually in /var/lib/docker).  Unless you were referring to the "volume" (persistent storage) for Docker being on your SSD.  Which would also work.  I don't know how much persistent storage HA needs, just some configs, right?  I wouldn't think a lot.
     
    Anyway to answer your question, something like this (Armbian on scdard) seems like a much more "normal" option to me.  Where you want to put persistent storage for HA is up to you but in my mind it's just some config text files, so very small.  And therefore I wouldn't want to waste a whole drive just for that.  Unless you were talking about storage for your Docker images.
     
    From your post, I suspect you had some problem with scdard corruption.  Armbian do a lot of things to mitigate this (like writing logs to zram, etc.) to minimize wear on your sdcard.  Maybe you know this already (and maybe this is why you decide to switch to Armbian) but if not, all of this info is also right there in the docs for you to study.
     
    Having said that, sdcards do wear out after some number of years.  So keep spare sdcards (also good for troubleshooting), make backups of your important data, etc.  But these things always apply and are not particular to Armbian.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines