Discourse ohne Docker bereitstellen

Community-Wiki Systemadministratoren
,
7

@lion , versuchen Sie es mit diesem:\n\n```

frozen_string_literal: true

require “fileutils”

discourse_path = File.expand_path(File.expand_path(File.dirname(FILE)) + “/../”)

enable_logstash_logger = ENV[“ENABLE_LOGSTASH_LOGGER”] == “1”
puma_stderr_path = “#{discourse_path}/log/puma.stderr.log”
puma_stdout_path = “#{discourse_path}/log/puma.stdout.log”

Logstash-Logger laden, falls aktiviert

if enable_logstash_logger
require_relative “../lib/discourse_logstash_logger”
FileUtils.touch(puma_stderr_path) if !File.exist?(puma_stderr_path)

Hinweis: Möglicherweise müssen Sie die Logger-Initialisierung für Puma anpassen

log_formatter = proc do |severity, time, progname, msg|
event = {
“@timestamp” => Time.now.utc,
“message” => msg,
“severity” => severity,
“type” => “puma”
}
“#{event.to_json}\n”
end
else
stdout_redirect puma_stdout_path, puma_stderr_path, true
end

Anzahl der Worker (Prozesse)

workers ENV.fetch(“PUMA_WORKERS”, 8).to_i

Verzeichnis festlegen

directory discourse_path

An die angegebene Adresse und den Port binden

bind ENV.fetch(“PUMA_BIND”, “tcp://#{ENV[‘PUMA_BIND_ALL’] ? ‘’ : ‘127.0.0.1:’}3000”)

PID-Datei-Speicherort

FileUtils.mkdir_p(“#{discourse_path}/tmp/pids”)
pidfile ENV.fetch(“PUMA_PID_PATH”, “#{discourse_path}/tmp/pids/puma.pid”)

Statusdatei - wird von pumactl verwendet

state_path “#{discourse_path}/tmp/pids/puma.state”

Umgebungsabhängige Konfiguration

if ENV[“RAILS_ENV”] == “production”

Produktions-Timeout

worker_timeout 30
else

Entwicklungs-Timeout

worker_timeout ENV.fetch(“PUMA_TIMEOUT”, 60).to_i
end

Anwendung vorladen

preload_app!

Worker-Start und -Herunterfahren behandeln

before_fork do
Discourse.preload_rails!
Discourse.before_fork

Supervisor-Prüfung

supervisor_pid = ENV[“PUMA_SUPERVISOR_PID”].to_i
if supervisor_pid > 0
Thread.new do
loop do
unless File.exist?(“/proc/#{supervisor_pid}”)
puts “Kill self supervisor is gone”
Process.kill “TERM”, Process.pid
end
sleep 2
end
end
end

Sidekiq-Worker

sidekiqs = ENV[“PUMA_SIDEKIQS”].to_i
if sidekiqs > 0
puts “starting #{sidekiqs} supervised sidekiqs”

require "demon/sidekiq"
Demon::Sidekiq.after_fork { DiscourseEvent.trigger(:sidekiq_fork_started) }
Demon::Sidekiq.start(sidekiqs)

if Discourse.enable_sidekiq_logging?
  Signal.trap("USR1") do
    # Verzögern Sie das erneute Öffnen der Sidekiq-Protokolle
    sleep 1
    Demon::Sidekiq.kill("USR2")
  end
end

end

E-Mail-Synchronisierungs-Daemon

if ENV[“DISCOURSE_ENABLE_EMAIL_SYNC_DEMON”] == “true”
puts “starting up EmailSync demon”
Demon::EmailSync.start(1)
end

Plugin-Daemons

DiscoursePluginRegistry.demon_processes.each do |demon_class|
puts “starting #{demon_class.prefix} demon”
demon_class.start(1)
end

Daemon-Überwachungs-Thread

Thread.new do
loop do
begin
sleep 60

    if sidekiqs > 0
      Demon::Sidekiq.ensure_running
      Demon::Sidekiq.heartbeat_check
      Demon::Sidekiq.rss_memory_check
    end

    if ENV["DISCOURSE_ENABLE_EMAIL_SYNC_DEMON"] == "true"
      Demon::EmailSync.ensure_running
      Demon::EmailSync.check_email_sync_heartbeat
    end

    DiscoursePluginRegistry.demon_processes.each(&:ensure_running)
  rescue => e
    Rails.logger.warn("Error in demon processes heartbeat check: #{e}\n#{e.backtrace.join("\n")}")
  end
end

end

Redis-Verbindung schließen

Discourse.redis.close
end

on_worker_boot do
DiscourseEvent.trigger(:web_fork_started)
Discourse.after_fork
end

Worker-Timeout-Behandlung

worker_timeout 30

Low-Level-Worker-Optionen

threads 8, 32