this post was submitted on 10 Apr 2025
27 points (96.6% liked)

Selfhosted

59897 readers
526 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam.

  3. Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.

  4. Don't duplicate the full text of your blog or git here. Just post the link for folks to click.

  5. Submission headline should match the article title.

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

I am currently looking into ansibles to store my configurations and deploy services more easily.

I have couple of iptable rules in /etc/iptables/rules.v4, which I can easily restore. Meanwhile, ansible has iptable role for configurations - hence, I am confused on what approach to take.

How do I persist this rules, especially across reboots? Should I rerun ansible every time on each reboot? I am at loss on how to best manage iptables, as other services can interact with it. How do you folks handle this? Thanks in advance!

you are viewing a single comment's thread
view the rest of the comments
[โ€“] vegetaaaaaaa@lemmy.world 1 points 1 year ago (1 children)

Ansible should only run to make changes to a existing system.

No. Ansible is fine for provisioning and initial deployment.

[โ€“] possiblylinux127@lemmy.zip 0 points 1 year ago* (last edited 1 year ago)

I miss phrased this

My existing system I mean some sort of Linux install. Don't use Ansible to start a service on startup.