295
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 28 Jun 2023
295 points (99.7% liked)
Asklemmy
42525 readers
1214 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 5 years ago
MODERATORS
I decided to host my own because I was on lemmy.world and we got blocked by beehaw, which had many of the communities I wanted to be a part of. I run mine on a server that's in my house, so the only thing I'm paying for is electricity. And I have solar panels.
How difficult is it to host your own instance? Can you still use apps like Connect with it?
Yes to the last question
It was really annoying to set up if I'm being honest. If I hadn't taken classes on Docker, I would have never figured it out. Luckily they have been improving the process recently. It already much easier now than it was a week ago. Hopefully by the next major release it is easy peasy.
Good to know! Sounds like another reason for me to start learning Docker.
It's an amazing software. Just today I needed to spin up a super simple webserver just to share a file with another program who needed to download it via https. Literally one command and I had an Apache server serving an arbitrary folder with a specified SSL certificate for HTTPS. And then one more command to shut it down, and it's gone. No software to uninstall when I don't need it anymore. No leftover files (well, the images are cached, but that's super easy to clear).
And then just a few hours later, I wanted to test the same program using a samba share instead of https. One command, bam. Sharing the same folder with samba. And then one command and it's gone.
And say you want to upgrade your apache version later, you don't need to worry about if your package manager is pointing to the newest version. You just restart your container with the latest tag and you have the latest version.
I'm actually rewriting a lot of my services to be in containers. I host a few discord bots for a community that my wife is an admin of. I accidentally updated my server's version of python once and nuked a few bots (Discord's API updated and I had to change some code in the new version). I containerized my bots, and now they will always have their own python version independent of my server's version. And I made sure to specify a version tag rather than using the latest tag, so they will never change. It makes it way easier to make sure it never breaks.
As long as you have a domain or IP address for the instance, the apps should be able to connect to it.