Selfhosted
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.
-
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
-
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require your active participation in selfhosting or related communities, or the post will be removed. No more than 10% of your posts or comments may be self-promotional, or your post will be removed. F/LOSS Exception: If your post is about a project that is completely open source & can be self-hosted in full without payment, and your account is at least 30 days old, your post is exempt from this rule as long as you continue to engage in comments.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
I have used both, can tell you that a template file of
/etc/iptables/rules.v4withiptables-persistentis the easiest way.if you go the full IaC route and have vars for the rules, remember to get iptables to save its state after you have applied your rules
Thank you! Templating rules.v4 is a pretty attractive option. Though my VPS has some portions of the file which should be unmodified, so I would have to avoid this method.
That's the point of the template, you change the bits the need change and the bits that are static get templated
How do I keep some of the existing firewall rules (which is dependent on host) in the remote file, and change the other parts?
You could either copy them to the top of your template, or you could take a look at the blockinfile module
The way I have my file, is a load of default stuff. Like block windows ports and allow SSH.
With a for loop that adds stuff for a specific host, like allow http/s for the web server.
Thanks a lot! I will go with the blockinfile, sounds promising.