Recent searches

No recent searches

Search options

Not available on lingo.lol.
lingo.lol is one of the many independent Mastodon servers you can use to participate in the fediverse.
A place for linguists, philologists, and other lovers of languages.

Administered by:

Server stats:

54
active users

lingo.lol: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.4.3

#SelfHosted

12 posts12 participants1 post today
Michael Jack

First steps in the BSD world!

1) OpenBSD on VPS (Amsterdam)
2) FreeBSD on Raspberry Pi 4 (home)

I'm running a Wireguard connection between the two.

Next step is setting up relayd on the VPS to point at services on the Raspberry Pi server.

#OpenBSD#FreeBSD#selfhosted
mastodon.raddemo.host

How to Install and Configure #Syncthing on #Debian VPS Server Easily (in 30 Minutes or Less)

This article presents a comprehensive guide detailing how to install and configure Syncthing on Debian VPS server. Upon conclusion, you will be able to install Syncthing on Debian VPS.
How to Install and Configure Syncthing on Debian VPS Server
Introduction
Overview of Syncthing

Syncthing is an ...
Continued 👉 blog.radwebhosting.com/install #selfhosting #selfhosted #installguide #vpsguide

How to Install and Configure Syncthing on Debian VPS Server Easily (in 30 Minutes or Less)
RadWeb, LLC · How To Install And Configure Syncthing On Debian VPS Server Easily (in 30 Minutes Or Less) - VPS Hosting Blog | Dedicated Servers | Reseller HostingThis article presents a comprehensive guide detailing how to install and configure Syncthing on Debian VPS server. Upon conclusion, you will be able to
*
joegarciar3a3294

Deploying Nextcloud on AWS ECS with Pulumi

lemmy.world/post/34172325

lemmy.worldDeploying Nextcloud on AWS ECS with Pulumi - Lemmy.Worldi am not a devops engineer. i appreciate any critique or correction. code: gitlab [https://gitlab.com/joevizcara/pulumi-aws] github [https://github.com/joevizcara/pulumi-aws] # Deploying Nextcloud on AWS ECS with Pulumi This Pulumi programme deploys a highly-available, cost-effective Nextcloud service on AWS Fargate with a serverless Aurora PostgreSQL database. ## Deployment Option 1 (GitOps) The first few items are high-level instructions only. You can follow the instructions from the hyperlinked web pages. They include the best practices as recommended by the authors. 1. A Pulumi [https://app.pulumi.com/signin] account. This is for creating a Personal Access Token that is required when provisioning the AWS resources. 2. Create [https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users_create.html] a non-root AWS IAM User called pulumi-user. 3. Create [https://docs.aws.amazon.com/IAM/latest/UserGuide/id_groups_create.html] an IAM User Group called pulumi-group 4. Add [https://docs.aws.amazon.com/IAM/latest/UserGuide/id_groups_manage_add-remove-users.html] the pulumi-user to the pulumi-group User Group. 5. Attach [https://docs.aws.amazon.com/IAM/latest/UserGuide/id_groups_manage_attach-policy.html] the IAMFullAccess policy to pulumi-group. The IAMFullAccess allows your IAM User to add the remaining required IAM policies to the IAM User Group using the automation script later. 6. Create [https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html] an access key for your non-root IAM User. 7. On your Pulumi account, go to Personal access tokens [https://app.pulumi.com/user/settings/tokens] and create a token. 8. Also create a password for the Aurora Database. You can use a password generator. 9. Clone this repository either to your GitLab or GitHub. 10. This works either on GitLab CI/CD or GitHub Actions. On GitLab, go to the cloned repository settings > Settings > Variables. On GitHub, go to the cloned repository settings > Secrets and variables > Actions > Secrets. 11. Store the credentials from steps 6-8 as AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, PULUMI_ACCESS_TOKEN, and POSTGRES_PASSWORD. These will be used as environment variables by the deployment script. 12. On AWS Console, go to EC2 > Load Balancers. The DNS name is where you access the Nextcloud Web Interface to establish your administrative credentials. > [!NOTE] > The automatic deployment will be triggered if there are changes made on the main.go, .gitlab-ci.yml, or the ci.yml file upon doing a git push. > On main.go, you can adjust the specifications of the resources to be manifested. Notable ones are in lines 327, 328, 571, 572, 602, 603, 640. ## Deployment Option 2 (Manual) 1. Install Go [https://go.dev/doc/install], AWS CLI [https://docs.aws.amazon.com/cli/latest/userguide/getting-started-prereqs.html], and Pulumi [https://www.pulumi.com/docs/iac/get-started/aws/begin/]. 2. Follow steps 1-8 above. 3. Add the required IAM policies to the IAM User Group to allow Pulumi to interact with AWS resources: sh printf '%s\n' "arn:aws:iam::aws:policy/AmazonS3FullAccess" "arn:aws:iam::aws:policy/AmazonECS_FullAccess" "arn:aws:iam::aws:policy/ElasticLoadBalancingFullAccess" "arn:aws:iam::aws:policy/CloudWatchEventsFullAccess" "arn:aws:iam::aws:policy/AmazonEC2FullAccess" "arn:aws:iam::aws:policy/AmazonVPCFullAccess" "arn:aws:iam::aws:policy/SecretsManagerReadWrite" "arn:aws:iam::aws:policy/AmazonElasticFileSystemFullAccess" "arn:aws:iam::aws:policy/AmazonRDSFullAccess" | xargs -I {} aws iam attach-group-policy --group-name pulumi-group --policy-arn {} 4. Add the environment variables. sh export PULUMI_ACCESS_TOKEN="value" && export AWS_ACCESS_KEY_ID="value" && export AWS_SECRET_ACCESS_KEY="value" && export POSTGRES_PASSWORD="value" 5. Clone the repository locally and deploy. sh mkdir pulumi-aws && \ cd pulumi-aws && \ pulumi new aws-go && \ rm * && \ git clone https://gitlab.com/joevizcara/pulumi-aws.git . && \ pulumi up ## Deprovisioning sh pulumi destroy --yes ## Local Testing The Pulumi.aws-go-dev.yaml file contains a code block to use with Localstack [https://www.localstack.cloud/] for local testing. ## Features 1. Subscription-free application - Nextcloud is a free and open-source cloud storage and file-sharing platform. 2. Serverless management - using Fargate and Aurora Serverless reduces infrastructure management. 3. Reduced cost - can be scaled and as highly available as an AWS EKS cluster, but with cost lower per-hour. 4. Go coding language - a popular language for cloud-native applications, eliminating syntax barriers for engineers. ## Diagramme [https://gitlab.com/joevizcara/pulumi-aws/-/raw/master/Screenshot_20250724_074840.png]
#selfhosted
*
Julian Oliver

This article points to a common misconception around self-hosting.

The author tries hosting at home for a few weeks, & proclaims it is not the way. They then go on to argue for community managed server infrastructure instead (which is very much self-hosting).

Self-hosting does not solely refer to home-hosting ('on-prem'), nor sole owner-operator. It scales up to server infra in a datacenter, run & governed by those using it

So yes, the future is very much #selfhosted!

drewlyton.com/story/the-future

Drew Lyton · The Future is NOT Self-HostedIn a world where corporations have detached buying from owning, one man attempts to do something radical: build his own cloud.
Firebase

Tired of streaming subscription overload? 📺

Self-host your media with Jellyfin! Enjoy your movies, shows, & music—completely FREE, open-source, with no ads or tracking. Access your library from anywhere.

Get started today: github.com/jellyfin/jellyfin

#opensource #media #streaming #selfhosted #devtools

Would you ditch your current streaming service for this?

The Free Software Media System - Server Backend & API - jellyfin/jellyfin
GitHubGitHub - jellyfin/jellyfin: The Free Software Media System - Server Backend & APIThe Free Software Media System - Server Backend & API - jellyfin/jellyfin
Christian

🐘 Hey Mastodon Admins! Want to supercharge your server’s timeline?

I’m Chris, and I run relay.uggs.io — a personally-managed, fast, and curated Mastodon relay, built with love for the Fediverse. 💖

✅ Free & open to join — anyone’s welcome!
✅ No corporate backing — just one nerd with solid hardware and a passion for federation.
✅ High-quality stream — inactive or broken instances are pruned regularly.
✅ Solid stack — PostgreSQL, Redis, SSDs, HTTP/3 via Caddy, and more under the hood.

You’ll get more diverse content, more interactions, and a more vibrant feed. 🌍
Got questions or need help setting it up? Ping me at @chris — always happy to help!

👉 Join here: relay.uggs.io/

Let’s grow the Fediverse — together! 🚀
#Mastodon #FediAdmin #MastodonAdmin #MastodonRelay #Fediverse #SelfHosted #SysAdmin #Federation

relay.uggs.iorelay.uggs.io: Home
layzerjeyt

selfh.st: improper etiquette by 2010 standards? (trackers, no RSS) Thoughts?

lemmy.dbzer0.com/post/50468258

lemmy.dbzer0.comselfh.st: improper etiquette by 2010 standards? (trackers, no RSS) Thoughts? - Divisions by zeroI went to https://selfh.st/ [https://selfh.st/] because someone posted a link to a github repo that had some tracking appended to the URL (?ref=selfh.st). OK your marketing worked on me I’m a mark. I still have an aversion to this kind of tracking. Maybe considering how old-fashioned it it compared to the undetectable and nearly impossible to evade tracking methods currently deployed, that’s wrong. Maybe this is just charming and quaint. Disregarding the above, I liked the site enough to subscribe to their RSS feed https://selfh.st/rss/ [https://selfh.st/rss/]. Well that was pointless, as there is no content in the feed. Each entry like this: > Self-hosted news, updates, launches, and content for the week ending Friday, August 1, 2025 > > Continue reading on selfh.st [http://selfh.st]… I kind of expect a meaningful RSS feed these days. It sign of participating in the Libre internet. Workaround: I have used Kill the Newsletter! [https://kill-the-newsletter.com/] (which kicks ass) to convert the email newsletter to an Atom feed which appears to work. Got the confirmation email, now need to wait for a post to be made. What do you all think? 1. Link tracking: yay or nay? 2. Placeholder RSS: Rude or acceptable?
#selfhosted
Elena Rossini on GoToSocial ⁂

🏕️ my adventures in #selfhosting: day 230 (disconnected edition) 🏝️

a micro blog post that celebrates the release of #Ghost v6 - and laments the fact I can’t upgrade to it at the moment (stranded in a remote place with spotty internet).

🔗: https://news.elenarossini.com/my-so-called-sudo-life/my-adventures-in-self-hosting-day-230-disconnected-edition/

HUGE congratulations to @index @johnonolan and the whole Ghost team 🥳

I’m starting a countdown and hope I can type “ghost update” in Terminal in 12-13 days or so.

Elena Rossini · 🏕️ my adventures in self-hosting: day 230 (disconnected edition) 🏝️
More from Elena Rossini ⁂
#MySoCalledSudoLife#MySoCalledSudoLifeInterrupted#selfhosted
Replied in thread
Paco Hope #resist

@socketwench As a bit of a clueless self-hoster, I’m using compose in my “prod” all the time. I have wanted to switch to swarm for a long time, but have been daunted.

The way i see it, when i go to self-host something, i look for the docker version. I usually see some idiotically long “docker run” command. Nobody is using THAT for production. So i end up converting it by hand into a compose file.

My self-hosting has multiple public IPv4s and multiple hosts (I’m a sort of micro-ISP). If I could transition to swarm mode I would. For now I am stuck with 3 hosts that have 3 distinct portainer installs and a bunch of compose files manually distributed/balanced across the hosts. It’s terrible. But I don’t know how to move it to swarm. I’d love to know how, but starting from scratch isn’t possible.

#selfhosting#selfhosted#homelab
*
gedaliyah

Automating Restic backups

lemmy.world/post/33912328

lemmy.worldAutomating Restic backups - Lemmy.WorldI’m having trouble automating the restic backup using systemd. I followed the linked guide, which seems pretty straightforward. Backup works fine when I run it manually, but when I try to run systemctl status restic-backup.service I get the following error: Fatal: parsing repository location failed: s3: bucket name not found I have triple-checked the file paths, and also added PassEnvironment=AWS_ACCESS_KEY_ID AWS_SECRET_ACCESS_KEY RESTIC_REPOSITORY RESTIC_PASSWORD_FILE B2_ACCOUNT_ID B2_ACCOUNT_KEY to the restic-backup.service file, which I saw used elsewhere. This is my first time using systemd, so I’m not sure if I am overlooking an obvious step or what. OS: Xubuntu restic: installed locally following these steps [https://www.backblaze.com/docs/cloud-storage-integrate-restic-with-backblaze-b2] backup: Backblaze B2 bucket with s3
#selfhosted
Otter Raft

Calibre-Web-Automated v3.1.1 - The Community Update 👬 Hardcover Integration 💜, Calibre Plugins 🔌, Split Library Support 💞, KoReader Sync 🗘 and much more! 📚

lemmy.ca/post/49093123

lemmy.caCalibre-Web-Automated v3.1.1 - The Community Update 👬 Hardcover Integration 💜, Calibre Plugins 🔌, Split Library Support 💞, KoReader Sync 🗘 and much more! 📚 - Lemmy.caIt looks like a massive update. Here are some excerpts, with more changes listed in the link above. I’m especially excited about the companion app: > “Calibre-Web Automated is extremely lucky and privileged to have such a large and vibrant community of people who support, enjoy and contribute to the project. The bulk of the new features and bugfixes this update brings were created by the best and brightest of our community and I want to celebrate that and their work here in the hope that our community only continues to grow!” - CrocodileStick > # Major Changes 🚀 > > ## NEW: Split Library Support 💞 > > - As promised, all CWA features are now fully compatible with Calibre-Web’s Split Library Functionality > - This enables users to store their Calibre Library in a a separate location to their metadata.db file > - To configure this, in the Admin Panel, navigate to Edit Calibre Database Configuration -> Separate Book Files from Library > - The use of Network Shares (especially NFS) with this functionality is discouraged as they sometimes don’t play well with CW & CWA’s SQLite3 heavy stack. Many users use network shares without issues but there aren’t enough resources to support those who can’t get it working on their own > > ## NEW: Hardcover API Integration 💜📖 > > - Hardcover [https://hardcover.app/] is now officially not only available as a Metadata Provider, but using Hardcover’s API, Kobo Shelves & Read Progress can now also be synced to a user’s Hardcover account! > > - Current workflow is scraping a book by title, you can then use the resulting hardcover-id identifier to search for editions of that book, by searching “hardcover-id:”. Edition results are filtered to exclude Audiobooks editions, and sorted by ebook then physical book. > > - If a shelf in CWA is selected for Kobo sync, when a book with id and edition identifiers is added to the shelf, it will also be added to Hardcovers want to read list. As the book is read on the Kobo device progress is synced to Hardcover as well when pushed to CWA. > > - To use Hardcover as a Metadata Provider, simply provided a Hardcover API Token in your docker-compose under the HARDCOVER_TOKEN Environment Variable > - To enable Kobo sync, a Hardcover API Token must be provided for each user in each user’s respective Profile Page > > - Thanks to demitrix [https://github.com/demitrix]! <3 > > ## NEW: Greatly Improved Metadata Selection UI 🎨 > > - Demitrix was really on a roll the last couple of months and also contributed some really cool functionality to the Metadata Selection UI > > CWA New Metadata Fetch UI - V3.1.0 [https://raw.githubusercontent.com/crocodilestick/Calibre-Web-Automated/refs/heads/main/README_images/V3-1-0_metadata_fetch_overhaul.png] > > - Much more Elegant & Readable UI, both on Mobile & on Desktop > - Improved CSS for the Fetch Metadata interface—making it easier and clearer for you to review and select metadata sources. > - Individually Selectable Elements > - Say goodbye to having to having all of your book’s metadata overwritten simply becuasse you wanted a better looking cover! > - As of V3.1.0, all metadata elements can be individually updated from multiple sources instead of the only option being to take everything for a single source! > > - Visual Quality Comparison Between the Cover Your Book Already Those Available from Metadata Providers > - Looking for a specific cover but not sure if the image file is low quality or not? As of V3.1.0, the resolution of cover images is now displayed on the bottom right corner of the preview, the background of which is colour-coded to indicate whether the available cover is of greater, lower or equal quality to the one already attached to the ebook! > > - Thanks to demitrix [https://github.com/demitrix] for their contributions to this! <3 > > ## NEW: KoReader Sync Functionality! 📚🗘 > > - CWA now includes built-in KOReader syncing functionality, providing a modern alternative to traditional KOReader sync servers! > - Universal KOReader Syncer: Works across all KOReader-compatible devices, storing sync data in a readable format for future CWA features > - Modern Authentication: Uses RFC 7617 compliant header-based authentication instead of legacy MD5 hashing for enhanced security > - CWA Integration: Leverages your existing CWA user accounts and permissions - no additional server setup required > - Easy Installation: Plugin and setup instructions are available directly from your CWA instance at /kosync > - Provided by sirwolfgang [https://github.com/sirwolfgang]! <3 > > ## NEW: Support for the Latest Versions of Calibre, even on devices with older Kernels! 🆕🎉 > > - ABI tag from the extracted libQt6* files removed to allow them to be used with older kernels > - Adds binutils to install strip for calibre-included Dockerfile. > strip libQt6*.so files of the ABI tag so that they can work with older kernels (harmless for newer kernels). > These libraries appear to still contain fallbacks for any missing syscalls that calibre might use. > add .gitattributes to enforce LF checkout on .sh files (useful for those who build on windows) > - Thanks to these changes, CWA now has much greater compatibility with a much wider range of devices & is able to keep up to date with the latest Calibre Releases! 🎉 > - Provided by FennyFatal [https://github.com/FennyFatal] <3 > > ## NEW: Calibre Plugin Support (WIP) 🔌 > > - Users can now install Calibre plugins such as DeDRM > - The feature is still a work in progress but users with existing Calibre instances can simply bind their existing Calibre plugins folder to /config/.config/calibre/plugins in their docker-compose file > > ## NEW: Bulk Add Books to Shelves 📚📚📚 > Contributed by netvyper [https://github.com/netvyper], you can now select multiple books from the book list page and add them to a shelf in one go! > > - New “Add to Shelf” button in bulk actions on the book list. > - Modal dialog lets you pick your shelf. > - Backend checks for permissions, duplicates, and provides clear success/error feedback. > > ## NEW: Better Docs Cometh - The Birth of the CWA Wiki 📜 > > - The documentation for CWA while for many enough, could really be better in helping as many users find the answers and information they need as quickly as possible > - Therefore We have started work on the CWA Wiki [https://github.com/crocodilestick/Calibre-Web-Automated/wiki] to strive towards this goal! > - While still very much a work in progress, submissions for pages, edits ect. are open to the community so if you stumble across something that seems wrong, missing or outdated, please jump in and change it if you can or let us know if you’re not sure :) > # Affliated Projects 👬 > > - In the spirit of community, I also wanted to give a shout out to some really great affiliate projects made by members of our community! > - As well as being featured here in the release, affiliated projects will now also be prominently feature on the CWA GitHub page to drive as much traffic & enthusiasm to them as possible > - If you’ve had an idea for a companion project for CWA, or want to get involved in helping improve CWA and/or it’s affiliated projects, please just do so! We’re all open-source here so you don’t need anyone’s permission, just go for it! :) > > <br> > > ___ > > ### Calibre-Web Companion [https://github.com/doen1el/calibre-web-companion] > > - Built with Flutter and using Material You, Calibre Web Companion [https://github.com/doen1el/calibre-web-companion] is an unofficial companion application for Calibre Web & Calibre Web Automated that allows you to browse your book collection and download books directly on your device, providing a much more modern, mobile-friendly UX than either service can currently provide on its own > > <br> > > Calibre Web Companion Preview [https://raw.githubusercontent.com/crocodilestick/Calibre-Web-Automated/refs/heads/main/README_images/cw-companion-screenshots.png]https://github.com/doen1el/calibre-web-companion > > <img src=“https://raw.githubusercontent.com/crocodilestick/Calibre-Web-Automated/refs/heads/main/README_images/google-play.png” alt=“Get it on Google Play” height=“80”> [https://play.google.com/store/apps/details?id=de.doen1el.calibreWebCompanion] > <img src=“https://fdroid.gitlab.io/artwork/badge/get-it-on.png” alt=“Get it on F-Droid” height=“80”> [https://f-droid.org/en/packages/de.doen1el.calibreWebCompanion/] > <img src=“https://raw.githubusercontent.com/vadret/android/master/assets/get-github.png” alt=“Get it on GitHub” height=“80”> [https://github.com/doen1el/calibre-web-companion] > ___ > > ### Calibre-Web Automated Book Downloader [https://github.com/calibrain/calibre-web-automated-book-downloader] > > - An intuitive web interface for searching and requesting book downloads, designed to work seamlessly with Calibre-Web-Automated. This project streamlines the process of downloading books and preparing them for integration into your Calibre library > > <img src=“https://raw.githubusercontent.com/vadret/android/master/assets/get-github.png” alt=“Get it on GitHub” height=“80”> [https://github.com/calibrain/calibre-web-automated-book-downloader] > > ## Supporting the Project ❤️ > > If you are in a position to, donations no matter how small are really appreciated & really help to keep the project going. Currently all money that has been and will be received is going towards a Kobo device so I can finally help out with the development & testing of CWA’s KoSync & Kobo specific features :) > > <img src=“https://storage.ko-fi.com/cdn/brandasset/v2/support_me_on_kofi_red.png” alt=“” height=“50”> [https://ko-fi.com/crocodilestick/tip]
#selfhosted
yuris

Migrated my Docker Compose homelab to OpenTofu

lemmy.ml/post/34043744

lemmy.mlMigrated my Docker Compose homelab to OpenTofu - LemmyI don’t usually post, but thought I’d share. I rebuilt my homelab with OpenTofu. Now my entire setup, from containers to networking, lives in a Git repo. The best part is that new services get published automatically. I just set a flag in the code, and it builds the Caddy proxy or Cloudflare tunnel for me. No more manual config editing. Here’s my quick write-up on it: https://yuris.dev/blog/homelab-opentofu [https://yuris.dev/blog/homelab-opentofu] And the code is all public if you want to see how it works: https://github.com/yurisasc/homelab [https://github.com/yurisasc/homelab] Hope this is interesting to someone. Happy to answer any questions if you have them. Curious to hear if anyone else has gone down this particular rabbit hole with IaC for their Docker stack.
#selfhosted
TrendingLive feeds
About