Self-Hosted Main

Just to avoid advice I'm already aware of: I don't want to use a VPN, nor a cloudflare tunnel.

I want to self host, ideally docker compatible, piece of software which would utilize ssh port 22 on the local network to access devices on that LAN, and then forward the information through a reverse proxy and securely through https, into my browser window, where I can interact with it from anywhere. I know guacamole, but it seems a bit cluttered with functionality I don't need - RDP and VNC.

Greetings fellow self-hosters!

I wanted to see if other people might be interested in a project I've been working on - hopefully a few people on here will find it useful

​

I've tried a few different map, planners, and various gardening apps to try to manage my homestead better. I do a bit of orcharding, landscaping, and gardening, and wanted an app that would help me be able to keep track of where I've planted things, and what they were, as well as to keep track of critical infrastructure around my lot. I didn't really find an app that ticked all the boxes I needed for this, so I decided to learn python a bit and made GoGrow as a pet project over the last few months.

Image annotation

Journal

GoGrow allows you to upload any .jpg or .png image (DNG and RAW is supported right now but experimental) for annotation, and then add your own custom SVG markers/icons or basic lines of whatever color you choose onto the image. The GoGrow app makes a folder to store each uploaded image in with its own SQLite database for all of your marker and line data relating to that image, as well as another database for journal entries relating to these markers or line objects.

This flexibility in this system along with the built in rich text editor allows for journal entries to have relevant markers and lines data linked to them, making it easy to track progress on a project or homestead over time, and allow for building of knowledgebases around projects.

All of this data never leaves GoGrow, and can easily be exported out, something I was initially very concerned with when I was looking for apps with which to manage my own homestead and projects.

The GoGrow app is still in the early stages of development, but I feel that it's progressed enough that I'd like to get some feedback from people on what other features might be good, or if there are any UI or UX things in particular that can be improved on.

It's all open source, free, and self-hostable - and (I think) relatively easy to get going with docker or just running as a python flask app with a few command line commands. I might consider offering linux and windows executables in the future if people would want that

You can check out the GoGrow project on my github here

Feel free to message me with any feedback or suggestions.

Edit: removed some words. I need more coffee

I’m trying to change the color at the top of the page around the status bar area. I’ve seen other pages do it. Apologies in advance. I tried to Google, but I really didn’t know what keywords to put in, so my queries were basically word soup.

current

what I would like

I have been looking for a cheap cloud storage solution where I could store my backups and I've stumbled upon https://www.storj.io/ . Apparently it's some decentralized storage solution and I was wondering if someone was currently using it and what was their experience with it. (for backups or something)

They're 0.001 cent cheaper per GB than blackblaze which is the cheapest cloud I found, so i'm considering using them, it's not gonna make a huge difference for the amount i'm gonna use but I'm still a bit curious

I don't seem to be able to run the linuxserver Plex docker container correctly. The docker compose file is simple and copied below. The user PUID and group PGID are obtained from /etc/passwd entries or "id -u". The user with PUID and PGID has full permission to /myconfig and /mymovies in the host. I tried various different users, some with admin privileges.

The container runs, but in the PLEX account I don't see any option to find local media. There is a bunch of annoying TV and movie and streaming advertisements/promotions.

What am I doing wrong?

​

--- version: "2.1" services: plex: image: lscr.io/linuxserver/plex:latest container_name: plex network_mode: host environment: - PUID= 1026 - PGID= 100 - VERSION=docker volumes: - /myconfig:/config - /mymovies:/movies restart: unless-stopped

​

I was thinking about migrating my services to self management k8s cluster, mostly for education purposes. I have some low traffic services running on one dedicated server on Scaleway now - there's some nextcloud, portainer, hastebin (sort of pastebin) mysql database, personal wiki, couple of half-dead blogs, stuff like that. Nothing resources heavy, nothing that needs tight SLA. I plan to add a little of my own software anytime soon, but I don't expect it to be very needy as well.

I'm planning on going with 3 nodes with min. 2 cores and 4 GB of RAM, and an additional service for storage. Does anyone here had experience with self hostes kubernetes? Do you have any advices? Do you think nodes like these are enough or I should upgrade (or downgrade)? Can you reccomend some providers that could offer this setup at low cost?

Hey all,

I'm looking for a personal photo blog app, that I can self-host on my Synology.

It needs to be simple, allow me to manage content, and add simple text descriptions/comments.

Something in a style of https://len.to/ but with a CMS and login page.

Cheers!

currently i have few websites running on a single apache instance. everything works with the typical port forward setup. let say theres 5 websites with different domain names (some of it are sub-domain)

however, due to some special circumstances, some websites need to move to other server, different location, behind cgnat. i already set the tunnel up, however for whatever reason, it doesnt seems to work/point to the wrong websites/application, the default apache page to exact.

the domain/subdomain is not directly managed by me. but it is already pointed to my server through cname records. i do have other domain (unlrelated to the website) managed with cloudflare, thats what it tried to use with for the tunnel.

before: website1.com -> (cname) s1.server.net website2.com -> (cname) s1.server.net

after: website1.com -> (tunnel address) tunnel1.server.net website2.com -> (tunnel address) tunnel2.server.net

is there any proper/correct way to do this?

Hi there, I'm looking for a Windows VPS hosting, that has a 16 core cpu and around 64 gb of ram. Anyone got a provider? Or are there some small providers in here that can help me out?

cross-posted from: https://programming.dev/post/684345

> Word never really got out about Discuss.Online which was set up to handle a huge influx on signups. But the signups haven't materialized. Here's what the admin has to say. > > cross-posted from: https://discuss.online/post/198448 > > > # Timeline and reasoning behind recent infra changes > > > > Recently, you may have noticed some planned outages and site issues. I've decided to scale down the size and resilience of the infrastructure. I want to explain why this is. The tl;dr; is cost. > > > > ## Reasons > > > > - I started discuss.online about 4 weeks ago. I had hoped that the reaction to Reddit's API changes would create a huge rush to something new, for the people, by the people; however, people did not respond this way. > > - I built my Lemmy instance like any other enterprise software I have worked on. I planned for reliability and performance. This, of course, costs money. I wanted to be known as the poster child for how Lemmy should operate. > > - As I built out the services from a single server instance to what it became the cost went up dramatically. I justified this assuming that the rush of traffic would provide enough donors to supplement the cost for better performance and reliability. > > - The traffic load on discuss.online is less that extraordinary. I've decided that I've way over engineered the resilience and scale. Some SubReddits that had originally planned to stay closed decided to re-open. I no longer needed to be large. > > - The pricing of the server had gotten way out of control. More than the cost of some of the largest instances in Lemmy while running a fraction of the user base. > > > > ### Previous infrastructure > > - Load balancer (2 Nodes @ $24/month total) > > - Two front-end servers (2 Nodes @ $84/month total) > > - Backend Server (1 Node @ $84/month total) > > - Pictures server (1 Node @ $14/month total) > > - Database (2 Nodes @ $240/month total) > > - Object Storage ($5/month + Usage see: https://docs.digitalocean.com/products/spaces/details/pricing/) > > - Extra Volume Storage ($10/month) > > - wiki.discuss.online web node ($7/month) > > - wiki.discuss.online database node ($15/month) > > [Total cost for Lemmy Alone: $483 + Usage] > > > > > > Additionally: > > - I run a server for log management that clears all lots after 14 days. This helps with finding issues. This has not changed. ($21/month) > > - Mastdon server & DB ($42/$15/+storage ~ $60 total/month) > > - Matrix server & DB ($42/$30/+storage ~ $75 total/month) > > > > Total Monthly server cost out of pocket: ~$640/month. > > > > The wiki, Mastodon, Matrix, & log servers all remained the same. The changes are for Lemmy only and will be the focus going forward. > > > > ## First attempt > > > > As you can see it was quite large. I've decided to scale way down. I attempted this on 7/12. However, I had some issues with configuration and database migration. That plan was abandoned. This is what it looked like: > > > > ### Planned infrastructure > > - Single instance server (1 Node @ $63/month total) > > - Includes front-end, backend, & pictures server. > > - Database server (1 Node @ $60/month total) > > - Object Storage ($5/month + Usage) > > - Extra Volumes ($20 / month total) > > > > [Total new cost: ~$150 + Usage] > > > > ## Second attempt > > > > I had discovered that the issues from the first attempt were caused by Lemmy's integration with Postgres. So I decided to take a second attempt. This is the current state: > > > > ### Current infrastructure > > - Single instance server (1 Node @ $63/month total) > > - Includes front-end, backend, & pictures server. > > - Database server (1 Node @ $60/month total) > > - Object Storage ($5/month + Usage) > > - Extra Volumes ($20 / month total) > > - wiki.discuss.online web node ($7/month) > > - wiki.discuss.online database node ($15/month) > > > > [Total new cost for Lemmy alone: ~$170 + Usage] > > > > New total monthly server cost out of pocket: ~$330 > > > > My current monthly bill is already more than that from previous infrastructure @ $336. > > > > ## Going forward > > Going forward I plan to monitor performance and try to balance the benefits of a snappy instance with the cost it takes to get there. I am fully invested in growing this community. I plan to continue to financially contribute and have zero expectations to have everything covered; however, community interest is very important. I'm not going to overspend for a very small set of users. > > > > If the growth of the instance continues or rapidly changes I'll start to scale back up. > > > > I'm learning how to run a Lemmy server. I'll adjust to keep it going. > > > > ## Here are my current priorities for this instance: > > 1. Security > > - This has to be number one for every instance. Where you decide to store your data is your choice again. You must be able to trust that your data is safe and bad actors cannot get it. > > 2. Resilience & backups > > - Like before, it's your data and I'm keeping it useable for you. I plan to keep it that way by providing disaster recovery steps and tools. > > 3. Performance > > - Performance is important to me mostly because it helps ensure trust. A site that responds well mans the admin cares. > > 4. Features > > - Lemmy is still very new and needs a lot of help. I plan to contribute to the core of Lemmy along with creating 3rd party tools to help grow the community. I've already began working on https://socialcare.dev. I hope to help supplement some missing core features with this tool and allow others to gain from it in the process. > > 5. User engagement > > - User engagement would be #1; however, everything before this is what makes user engagement possible. People must be using this site for it to matter and for me to justify cost and time. > > > > ## Conclusion > > > > If you notice a huge drop in performance or more issues than normal please let me know ASAP. I'd rather spend a bit more for a better experience. > > > > Thanks, > > Jason > > > >

Track your wishlist items and get notified across multiple amazon stores