Selfhosted

39256 readers

176 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

ruud@lemmy.world

Loki@lemmy.world

CannaVet@lemmy.world

HybridSarcasm@lemmy.world

devve@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

If you use Proxmox, check out these scripts. There are dozens of helper scripts that will automate configuring Proxmox and creating LXCs and VMs for popular services. (tteck.github.io)

submitted 1 year ago by RotaryKeyboard@lemmy.ninja to c/selfhosted@lemmy.world

7 comments fedilink hide all child comments

From the Github Repo Readme: These scripts enable users to build a Linux container or virtual machine in an interactive manner, offering options for both basic and advanced configurations. The basic setup utilizes default settings, whereas the advanced setup empowers users to alter these default settings. Through the use of the whiptail command, options are presented to users in a dialog box format. After the user makes their selections, the script collects and verifies the user's input in order to generate the final configuration for the container or virtual machine.

top 6 comments

sorted by: hot top controversial new old

[–] Saik0Shinigami@lemmy.saik0.com 12 points 1 year ago* (last edited 1 year ago) (1 children)

I use these religiously...

However it should be noted... Always check scripts before you run them from the internet. Having said that... I mirror the whole repo I use it so damn much.

[–] mike@werm.social 1 points 1 year ago

Great tip to setup a mirror!

[–] node815@lemmy.world 2 points 1 year ago

I just migrated over from OpenMediaVault to Proxmox VE and it's a game changer for me. I was running Home Assistant in a KVM instance in OMV, and Docker images on the host OS for well over a year but it kept locking up. I wanted to start fresh, so I went to Proxmox the other day and have been well impressed so far. I ran into those scripts almost immediately and it got me started off on the right foot. So, now I have TWO VM's one for Home Assistant and one for my Docker instance. Then to replace the NAS, setup my NFS shares on the host which works well.

[–] Stijn@lemmy.antemeridiem.xyz 1 points 1 year ago (1 children)

I wish i found this a month ago.

[–] RotaryKeyboard@lemmy.ninja 1 points 1 year ago

I discovered it after installing a lot of my LXC containers, too. What I did was test the script and see if it made a better container than I did. If so, I just deleted the other LXC container. I also used it as a way to quickly change the LXC and VM IDs so that they would match the last octet of my internal IP address.

And don't forget that you can run the Proxmox settings and cleanup scripts at any time.

[–] jason@lemm.ee 1 points 1 year ago

running scripts like these make me nervous, especially on the host machine of a hypervisor. My (limited) understanding is that a compromised host system compromises all the VMs and containers within. Seems like you could be one command away from letting an attacker into everything.

load more comments