Separate config files per site in Nginx - Cheat Sheet & Quick Revision

Recall & Review

beginner

Why use separate config files for each site in nginx?

Using separate config files helps organize settings, makes it easier to manage multiple sites, and allows enabling or disabling sites without affecting others.

beginner

Where are separate site config files usually stored in nginx?

They are typically stored in the /etc/nginx/sites-available/ directory, with symbolic links in /etc/nginx/sites-enabled/ to activate them.

intermediate

What command activates a site config in nginx when using separate files?

You create a symbolic link from /etc/nginx/sites-available/your-site to /etc/nginx/sites-enabled/your-site using ln -s /etc/nginx/sites-available/your-site /etc/nginx/sites-enabled/your-site.

beginner

How do you reload nginx after adding or changing a site config file?

Run sudo nginx -t to test the config, then sudo systemctl reload nginx to apply changes without downtime.

intermediate

What is the purpose of the include directive in nginx main config for separate site files?

It tells nginx to load all site config files from a directory, usually include /etc/nginx/sites-enabled/*;, so each site config is read automatically.

Where should you place individual site config files in nginx?

A /etc/nginx/sites-available/

B /var/www/html/

C /usr/local/nginx/conf/

D /etc/nginx/conf.d/

Site config files are placed in /etc/nginx/sites-available/ for organization and management.

How do you enable a site config in nginx after creating it in sites-available?

A Copy it to /etc/nginx/sites-enabled/

B Edit /etc/nginx/nginx.conf directly

C Create a symbolic link in /etc/nginx/sites-enabled/

D Restart the server without changes

Creating a symbolic link in sites-enabled activates the site config.

What command checks nginx config syntax before reloading?

A nginx -t

B nginx -c

C nginx -s reload

D systemctl status nginx

The command nginx -t tests the configuration syntax.

What does the include directive do in nginx config?

A Creates symbolic links

B Starts the nginx server

C Disables site configs

D Includes external files into the main config

The include directive loads other config files into nginx's main configuration.

Why is it better to use separate config files per site?

A To reduce server memory

B To organize and manage sites easily

C To speed up nginx startup

D To avoid using symbolic links

Separate files help keep site configs organized and easy to manage.

Explain how to set up nginx to serve multiple websites using separate config files.

Think about file locations, linking, and commands to reload.

Describe the benefits of using separate config files per site in nginx.

Consider how managing many sites is easier this way.

Practice

1. What is the main benefit of using separate config files per site in nginx?

easy

A. It makes nginx run faster by loading fewer files.

B. It allows nginx to serve only one site at a time.

C. It automatically secures each site with HTTPS.

D. It keeps the nginx setup organized and easier to manage.

Solution

1. Step 1: Understand config file organization

   Separate config files help keep settings for each site distinct and clear.

2. Step 2: Recognize management benefits

   This organization makes it easier to update or troubleshoot individual sites without affecting others.

3. Final Answer:

   It keeps the nginx setup organized and easier to manage. -> Option D

4. Quick Check:

   Separate configs = better organization [OK]

Hint: Separate files mean easier site management [OK]

Common Mistakes:

• Thinking separate files speed up nginx
• Assuming separate files enable HTTPS automatically
• Believing nginx serves only one site with separate files

2. Which nginx directive correctly includes all site config files from the sites-enabled directory?

easy

A. include /etc/nginx/conf.d/*;

B. include /etc/nginx/sites-available/*;

C. include /etc/nginx/sites-enabled/*;

D. include /etc/nginx/sites-enabled.conf;

Solution

1. Step 1: Identify the correct directory for active sites

   The sites-enabled directory holds active site configs linked from sites-available.

2. Step 2: Use the include directive properly

   Using include /etc/nginx/sites-enabled/*; loads all enabled site configs.

3. Final Answer:

   include /etc/nginx/sites-enabled/*; -> Option C

4. Quick Check:

   Include sites-enabled/* loads active sites [OK]

Hint: Include sites-enabled/* to load active sites [OK]

Common Mistakes:

• Including sites-available instead of sites-enabled
• Using wrong directory like conf.d for site configs
• Missing the wildcard * to include all files

3. Given the command ln -s /etc/nginx/sites-available/example.com /etc/nginx/sites-enabled/, what is the effect?

medium

A. It creates a symbolic link to enable example.com site.

B. It copies the example.com config to sites-enabled.

C. It deletes the example.com config file.

D. It disables the example.com site.

Solution

1. Step 1: Understand the ln -s command

   The command creates a symbolic link from the source to the target location.

2. Step 2: Link sites-available to sites-enabled

   Linking example.com config into sites-enabled activates the site in nginx.

3. Final Answer:

   It creates a symbolic link to enable example.com site. -> Option A

4. Quick Check:

   ln -s from sites-available to sites-enabled enables site [OK]

Hint: ln -s link enables site by linking config [OK]

Common Mistakes:

• Thinking ln -s disables the site
• Assuming ln -s deletes or copies files
• Confusing symbolic link with file copy

4. You added a new site config in sites-available but forgot to link it in sites-enabled. What happens when you reload nginx?

medium

A. The new site is ignored and not served.

B. Nginx throws a syntax error and fails to reload.

C. The new site is active and served by nginx.

D. Nginx deletes the config file automatically.

Solution

1. Step 1: Understand sites-available vs sites-enabled

   Sites-available holds configs but only linked sites in sites-enabled are active.

2. Step 2: Effect of missing link on reload

   Without a link, nginx ignores the new config and serves only enabled sites.

3. Final Answer:

   The new site is ignored and not served. -> Option A

4. Quick Check:

   Missing link means site ignored on reload [OK]

Hint: Link site config to sites-enabled to activate [OK]

Common Mistakes:

• Expecting nginx to auto-enable new configs
• Thinking nginx reload fails without link
• Assuming nginx deletes unlinked configs

5. You want to add a new site with config in /etc/nginx/sites-available/newsite. Which sequence correctly enables it and reloads nginx safely?

hard

A. Copy config to sites-enabled, then run nginx -s reload

B. Create symbolic link in sites-enabled, test config with nginx -t, then reload nginx

C. Edit nginx.conf directly to add newsite, then restart nginx

D. Move config to sites-enabled, then reload nginx without testing

Solution

1. Step 1: Enable site by linking config

   Create a symbolic link from sites-available/newsite to sites-enabled to activate it.

2. Step 2: Test nginx config before reload

   Run nginx -t to check for syntax errors and avoid downtime.

3. Step 3: Reload nginx to apply changes

   Use nginx -s reload to apply new config without stopping the server.

4. Final Answer:

   Create symbolic link in sites-enabled, test config with nginx -t, then reload nginx -> Option B

5. Quick Check:

   Link + test + reload = safe enable [OK]

Hint: Always test config before reload after linking site [OK]

Common Mistakes:

• Copying instead of linking config files
• Reloading nginx without testing config
• Editing nginx.conf instead of using sites-available