Skip to Content
Last modified by Alexandru Pentilescu on 2023/06/25 18:53
From version 3.1
edited by Alexandru Pentilescu
on 2022/06/11 21:20
Change comment: There is no comment for this version
To version 2.1
edited by Alexandru Pentilescu
on 2022/06/11 21:18
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -67,7 +67,7 @@
67 67  
68 68  Ideally, "/etc/nginx/sites-enabled" should only contain symbolic link files to actual physical files stored in "/etc/nginx/sites-available". This is to allow partially defined services being configured offline in their own directory and, only after the configurations are fully complete, can they be activated by creating a symlink to their file.
69 69  
70 -Moreover, whenever a service needs to be disabled again, its configuration file doesn't have to be physically deleted in its entirety. All that has to be done is deleting the symbolic link pointing to it from "/etc/nginx/sites-enabled" and, afterwards, the file itself will remain on the drive under "/etc/nginx/sites-available" where it can be edited afterwards, until it can be reactivated again by the re-creation of a new symlink to it.
70 +Moreover, whenever a service needs to be disabled again, its configuration file doesn't have to be physically deleted in its entirety. All that has to be done is deleting the symbolic link pointing to it from "/etc/nginx/sites-enabled" and, afterwards, the file itself will remain on the drive under "/etc/nginx-sites-available" where it can be edited afterwards, until it can be reactivated again by the re-creation of a new symlink to it.
71 71  
72 72  Handling symbolic links is very easy and straightforward.
73 73  
... ... @@ -82,6 +82,7 @@
82 82  
83 83  Now, time to write a configuration file from scratch for our bitwarden service!
84 84  
85 +
85 85  = Example of a service configuration file =
86 86  
87 87  Please take a look at the following configuration file for our Bitwarden endpoint: