FeministWiki:Server setup: Difference between revisions

FeministWiki:Server setup (view source)

Revision as of 18:50, 18 August 2021

58 bytes added , 18 August 2021

→‎Put config files in place

Technician

Bureaucrats, Interface administrators, Administrators

1,084

edits

@@ Line 120: / Line 120: @@
 === Put config files in place ===
-The principle is simple: take all the config files from <code>/root/repo/etc</code> and put them where they belong in <code>/etc</code>.  However, since a new server might mean much newer software, it's possible that some config files aren't compatible anymore, or that some new sensible defaults might be overwritten by the old config.  Sadly figuring out these incompatibilities is a manual process: compare the new default config with the old default config and to our old config, to figure out what our new config should look like.
+The principle is simple: take all the config files from {{C|/root/repo/etc}} and put them where they belong in {{C|/etc}}.  However, since a new server might mean much newer software, it's possible that some config files aren't compatible anymore, or that some new sensible defaults might be overwritten by the old config.  Sadly figuring out these incompatibilities is a manual process: compare the new default config with the old default config and to our current config, to figure out what our new config should look like.
-There's one special thing to remember, which is that after copying in the new <code>/etc/aliases</code> file, you have to run the <code>newaliases</code> command for the changes to take effect.
+There's a number of things important to remember however:
+* After copying in the new {{C|/etc/aliases}} file, run {{C|newaliases}} for the changes to take effect
+* After populating {{C|/etc/letsencrypt/renewal-hooks}}, remember to {{C|chmod +x}} all the scripts
 === Initialize LetsEncrypt ===