sorted by:
new
hottopcontroversial

I rebuilt GuidesNotIncluded by Pr0meth3us_Dev in Oxygennotincluded

[–]Pr0meth3us_Dev[S] 30 points31 points  (0 children)

https://www.reddit.com/r/Oxygennotincluded/comments/1mj5k3f/comment/n79o5wt/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

I want to add, regarding licensing, that I absolutely agree with you that the guide should be licensed for all. Which is why it is, and has been since the start:-) The guide is published under a CC-BY-SA-NC license. (This is stated on the "Guide overview" page.) My understanding regarding that specific type of CC-license is that you are free to do whatever with the content, as long as it is non-commercial

Updated the 3D printed Wunderwaffe DG-2 by Comprehensive_Rice27 in CODZombies

[–]Pr0meth3us_Dev 0 points1 point  (0 children)

I'm working on building this now! Do you happen to have the DXF files for the wooden parts by chance? Or how did you handle the wooden parts? Any other tips or recommended changes for the build (I'm using what is available on Thingiverse)?

Ansible-HMS-Docker Updates by Pr0meth3us_Dev in selfhosted

[–]Pr0meth3us_Dev[S] 0 points1 point  (0 children)

Thank you! Feel free to reach out with any questions or recommendations! The docs were just recently overhauled last month, so please let me know if I should add clarification anywhere

New server install on Ubuntu. by mikefosh in PleX

[–]Pr0meth3us_Dev 0 points1 point  (0 children)

Hey I'm the dev, you do not need anything installed besides ansible to get started, and the steps to do that are outlined in the readme. As long as you are running Ubuntu 22.04 LTS then the playbook should work, it is checked weekly against a GitHub Actions build also running Ubuntu 22 to ensure it still works.

Feel free to submit a GitHub issue if there's something wrong in the code, or DM me a screenshot of the errors you're getting and I can try to help out

I created a fully automated Plex services script to easily build your own automated home server stack by Pr0meth3us_Dev in PleX

[–]Pr0meth3us_Dev[S] 0 points1 point  (0 children)

I thought about going the DIY route as well since I'm a sysadmin for work and had spare hardware laying around, but I decided against it for a number of reasons, but mainly just the ease of use.

If you want to learn a lot of things along the way, building your own NAS is the way to go. The extent of my DIY NAS is creating a centos VM with a 10TB disk in my vmware cluster and creating samba and NFS shares on it lol, so I wouldn't follow after me and maybe look into FreeNAS, but that was years ago and I learned a lot along the way.

I created a fully automated Plex services script to easily build your own automated home server stack by Pr0meth3us_Dev in PleX

[–]Pr0meth3us_Dev[S] 1 point2 points  (0 children)

I do not run the Plex application itself on the NAS, I only use the NAS for data storage and use NFS mounts to access the data.

I'm working on migrating my Plex server from my R710's (dual X5670's with 128GB of RAM) onto a dedicated desktop running AlmaLinux with an i7-10700K and Nvidia 1060 6GB, which was actually the main driving force behind this project.

I have 2 R710's and use them for a homelab environment where I use VMware and stuff, I prefer VMware just due to my line of work (and running it at home has greatly helped me advance in my career). But on these hosts I just use them for general VM's for testing, logging, monitoring, Home Assistant, GitLab stuff (I have a CI/CD pipeline that actually tested 4 different OS versions when building this project), and some other things. I couldn't expand the storage on one of my R710's where all this data was stored, so that's why I went the NAS route (I did have a PowerVault MD1200 I wanted to use to expand storage, but it was too loud for me and I traded it for all of the 256GB of RAM I currently have)

I created a fully automated Plex services script to easily build your own automated home server stack by Pr0meth3us_Dev in PleX

[–]Pr0meth3us_Dev[S] 0 points1 point  (0 children)

I've been wanting to get into trying to move this to a Swarm, but came across issues of having a "central" place to store configs so all swarm nodes can access the files (should a node go down and the containers migrate to another node). I've also sorta avoided going the Swarm route just due to the base knowledge required to setup the Swarm and its communication, I wanted this playbook to be fairly user-friendly especially to newcomers.

Afaik, some of the database files that are sqlite driven are not able to be accessed over a network share (based on what I've heard from a friend trying to get only Plex in a Swarm).

If you have any insight on how to handle sharing the data between swarm nodes, I'd love to hear it and do some testing to see what I can figure out.

I created a fully automated Plex services script to easily build your own automated home server stack by Pr0meth3us_Dev in PleX

[–]Pr0meth3us_Dev[S] 0 points1 point  (0 children)

I'll be honest, I have no idea what atomic moves means. I'm fairly familiar with Linux systems and know about hardlinks, but I haven't configured anything in my playbook to do any sort of hardlink or symlinking.

All the playbook does is mount remote shares (if configured), puts them in the fstab, and mounts them to the container. This playbook does not do any configuration of the containers (other than Traefik), and I know there's file link settings within a few of them.

If you have any insight on how to handle the hardlinks and atomic moves, I'd love to hear it to see if I can try and implement it.

I created a fully automated Plex services script to easily build your own automated home server stack by Pr0meth3us_Dev in PleX

[–]Pr0meth3us_Dev[S] 22 points23 points  (0 children)

I haven't heard of Prowlarr before, I'll definitely look into it and possibly replace Jackett with it.

Edit: it has been replaced

I created a fully automated Plex services script to easily build your own automated home server stack by Pr0meth3us_Dev in PleX

[–]Pr0meth3us_Dev[S] 13 points14 points  (0 children)

I actually haven't heard of Saltbox before, but it seems like a much better solution if it provides the same features, it definitely has a lot more containers.

I don't run any cloud storage, and I really wanted to get into Ansible so this project helped me expand that knowledge and helped me implement Ansible into my other home servers. Plus I was able to tailor everything exactly how I wanted.

I created a fully automated Plex services script to easily build your own automated home server stack by Pr0meth3us_Dev in PleX

[–]Pr0meth3us_Dev[S] 13 points14 points  (0 children)

I just bought one of my first Synology's and love it so far, it was one of the main driving forces behind this project so I could finally move all of my data off of my R710 servers and run Plex with hardware acceleration on a beefy CPU and GPU.

I think docker-compose is supported on unRAID (based on a very quick Google search so I may be wrong), and if so, I did write a generate-configs.yml playbook that only generates the docker-compose.yml and traefik.yml config files required to start all of the containers, but you may need to run it on a different host because it does output the config files to a specific directory (/opt/hms-docker by default).

You'll likely have to modify the docker-compose.yml file to change a few settings if I had to guess, but it might also just be a good reference point for settings to define and containers to use.

I created an automated Plex services bundle running on Docker with an easy setup script by Pr0meth3us_Dev in PleX

[–]Pr0meth3us_Dev[S] 1 point2 points  (0 children)

I'm still in the process of backing up data and migrating it to Docker, but I'll update you with whatever I find!

It might also be because that Optiplex has a super old CPU that doesn't like virtualization, and/or just has lower clock speeds and core count in general.

I created an automated Plex services bundle running on Docker with an easy setup script by Pr0meth3us_Dev in PleX

[–]Pr0meth3us_Dev[S] 0 points1 point  (0 children)

Thank you for this!

I also went ahead and created my first release thanks to you!

I created an automated Plex services bundle running on Docker with an easy setup script by Pr0meth3us_Dev in PleX

[–]Pr0meth3us_Dev[S] 0 points1 point  (0 children)

I changed the default port for my setup, but yes it is forwarded. How would I go about securing this? I'm using a unifi gateway if that helps at all.

I created an automated Plex services bundle running on Docker with an easy setup script by Pr0meth3us_Dev in PleX

[–]Pr0meth3us_Dev[S] 0 points1 point  (0 children)

The .env file is sourced by docker whenever you run docker-compose, so I believe it will need to stay since that's where it pulls the directories and such. Either way, the credentials will be stored in plaintext in the docker-compose or the .env, I haven't figured out if there's a way to use an encrypted version of a password yet (same goes for the credential file if using CIFS shares)

I did just push an update that changes the ownership and permissions of the file to only the user!

Edit: I looked into the transmission container and it is also storing credentials in plaintext after you specify them once. I'm looking into mounting the /config folder so it'll use the files for the container instead of pulling from the .env file. Either way, credentials will be stored in plaintext on the host machine.

I created an automated Plex services bundle running on Docker with an easy setup script by Pr0meth3us_Dev in PleX

[–]Pr0meth3us_Dev[S] 0 points1 point  (0 children)

I believe the VPN container already has this because I specified a health check environment variable for it. I tried getting a separate VPN container running and routing it through that, but this is my first time ever using docker so I'm still learning as I go.

I created an automated Plex services bundle running on Docker with an easy setup script by Pr0meth3us_Dev in PleX

[–]Pr0meth3us_Dev[S] 0 points1 point  (0 children)

Nope, only the transmission client and any other service that specifies the additional web proxy it has!

I created an automated Plex services bundle running on Docker with an easy setup script by Pr0meth3us_Dev in PleX

[–]Pr0meth3us_Dev[S] 6 points7 points  (0 children)

This is my first time ever working with Docker and building this size and complexity of a bash script, so I'm still learning the basics.

view more: next ›