Location of service and nginx files

SayakMukhopadhyay · June 23, 2022, 10:50am

I have 2 blogs hosted on my server and both are running Ghost 4.48.2. I have ghost-cli 1.21.0 installed. Lets call the 2 blogs “Old” and “New”. Both of these are running behind nginx with SSL. But today I noticed that old/system/files has 3 files, a .service file which is symlinked from /lib/systemd/system and 2 nginx .conf files which are symlinked from /etc/nginx/sites-available`.

But I don’t see these files in my New blog. Even the files folder is not present in the new/system folder. Instead the Nginx config files are directly created in sites-available and the service file is directly created in the systemd location.

I tried removing the nginx conf files from the sites-available folder and recreating them for my New blog using the ghost setup nginx command but it just recreated the files in that exact location. I haven’t tried doing the same for my Old blog.

Looking at the cli source code makes me think that the behaviour shown in the Old blog should be the correct one. What exactly is going on here?

P.S. Stuff is working, nothing is broken. This is just a professional curiosity.

markstos · June 23, 2022, 3:49pm

The current Ghost CLI behavior is to symlink a Nginx file into sites-available, but that step could be skipped if Nginx is already set up.

github.com

TryGhost/Ghost-CLI/blob/d9ecd383f4c7f5f2cd7bebac15b5234cce4b8bfd/extensions/nginx/index.js#L113


      
              const confFile = `${hostname}.conf`;
          
          
    const generatedConfig = conf({
                  url: hostname,
                  webroot: rootPath,
                  location: pathname !== '/' ? `^~ ${pathname}` : '/',
                  port: instance.config.get('server.port')
              });
          
          
    await this.template(instance, generatedConfig, 'nginx config', confFile, `${nginxConfigPath}/sites-available`);
              await this.ui.sudo(`ln -sf ${nginxConfigPath}/sites-available/${confFile} ${nginxConfigPath}/sites-enabled/${confFile}`);
              await this.restartNginx();
          }
          
          
setupSSL({instance, argv}) {
              const parsedUrl = url.parse(instance.config.get('url'));
              const confFile = `${parsedUrl.hostname}-ssl.conf`;
          
          
    const acme = require('./acme');
          
          
    const rootPath = path.resolve(instance.dir, 'system', 'nginx-root');

A systemd file is created directly in /lib/systemd/system from a template.

github.com

TryGhost/Ghost-CLI/blob/d9ecd383f4c7f5f2cd7bebac15b5234cce4b8bfd/extensions/systemd/index.js#L24


      
          }
          
          
setup() {
              return [{
                  id: 'systemd',
                  name: 'Systemd',
                  enabled: ({instance, argv}) => !argv.local &&
                       (instance.config.get('process') === 'systemd' || (argv.stages && argv.stages.includes('systemd'))),
                  task: (...args) => this._setup(...args),
                  skip: ({instance}) => {
                      if (fs.existsSync(`/lib/systemd/system/ghost_${instance.name}.service`)) {
                          return 'Systemd service has already been set up. Skipping Systemd setup';
                      }
          
          
            return false;
                  },
                  onUserSkip: ({instance, ui}) => {
                      ui.log('Systemd setup skipped, reverting to local process manager', 'yellow');
                      instance.config.set('process', 'local').save();
                  }
              }];

SayakMukhopadhyay · June 24, 2022, 4:44am

Do you mean that in the current behaviour, the file in sites-available is symlinked from somewhere else or is the file in sites-available a normal file?

Cause if the file in sites-available is symlinked from somewhere, where is it symlinked from? Moreover, this is not the behaviour that I see.

markstos · June 24, 2022, 11:16am

From reading the source code, there is a template for an Nginx config file stored within the Ghost CLI project.

That template gets rendered into a file stored in sites-available, and then the file in sites-available is symlinked into sites-enabled.

Here’s that piece of code:

github.com

TryGhost/Ghost-CLI/blob/d9ecd383f4c7f5f2cd7bebac15b5234cce4b8bfd/extensions/nginx/index.js#L100


      
                          return single ? 'Nginx config file does not exist, skipping SSL setup' : true;
                      }
          
          
            return false;
                  }
              }];
          }
          
          
async setupNginx({instance}) {
              const {hostname, pathname} = url.parse(instance.config.get('url'));
              const conf = template(fs.readFileSync(path.join(__dirname, 'templates', 'nginx.conf'), 'utf8'));
          
          
    const rootPath = path.resolve(instance.dir, 'system', 'nginx-root');
              const confFile = `${hostname}.conf`;
          
          
    const generatedConfig = conf({
                  url: hostname,
                  webroot: rootPath,
                  location: pathname !== '/' ? `^~ ${pathname}` : '/',
                  port: instance.config.get('server.port')
              });

Topic		Replies	Views
Example Nginx config for Ghost 1.x? Developer help	3	876	May 2, 2018
Ghost setup ssl = "Nginx config file does not exist, skipping SSL setup" Installation	9	3455	October 27, 2021
Ghost as a sub directory using NGINX Developer help	11	7842	June 29, 2018
Cannot access our newly created blog Installation	6	1403	May 3, 2018
Systemd: additional site on same server - ghost gone Installation	4	602	March 5, 2019

Location of service and nginx files

Related Topics