this post was submitted on 28 Dec 2022
4 points (100.0% liked)

lemmyBB

93 readers
1 users here now

Official community for lemmyBB frontend.

founded 2 years ago
MODERATORS
nutomic@lemmy.ml
4
Some questions about a new installation of LemmyBB (fedibb.ml)
submitted 2 years ago by enrique@fedibb.ml to c/lemmybb@lemmy.ml
8 comments fedilink hide all child comments
 

Hello. As I've mentioned on my presentation post, I'm planning to host an instance of LemmyBB, and although I won't start the actual installation until all the holidays have ended, I'm already in the planning stage, and many questions are already popping out :

  1. I would have preferred to not use docker (i hate it), but seeing that the manual installation of the Lemmy backend is heavily discouraged, I'll get used to the idea. But as I don't have many experience using docker, some questions arise as I read the installation manual:
  • "mkdir /srv/lemmybb" Does this implies that all the data inside the docker image will be stored on this folder? I always install Linux with separate system/data partitions, so I need to know this. I'm ok with using the /srv folder.
  • Is the database inside the docker image? Can it be configured to use any PostreSQL? I may install more services in this server, and I don't like the idea of having many databases engines running on it, I'll prefer only one centralized DB.

  1. If I'm understanding correctly, the docker image exposes the service on http://127.0.0.1:8701/, and then is reverse-proxied to the outside world. Can this reverse proxy be carried with Apache? I've never used nginx, however I have lots of experience with Apache, including reverse proxies, so I would prefer to stick with what I know. I can build a configuration for it based on the config file for nginx, no problem on this, but I need to know if the actual software will tolerate this or fail spectacularly

  2. System and bandwidth requirements? I'll be using a bare metal server, and industrial PC with an Atom D510, 4GB of ram and 128 GB of total disk space. The connection is going to be my home connection, trough my home router

Thanks for the help.

you are viewing a single comment's thread
view the rest of the comments
[–] enrique@fedibb.ml 1 points 2 years ago

Aaaand, first failure!!

After installing rustup, using cargo to download+compile lemmy server, and configuring lemmy, when I try to execute lemmy-server it fails. After enabling the backtrace, this is what I get:

./lemmy_server

thread 'main' panicked at 'Couldn't initialize settings.: LemmyError { message: None, inner: No such file or directory (os error 2), context: "SpanTrace" }', /usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/lemmy_server-0.16.7/src/main.rs:55:35 stack backtrace:

0: 0x5617abcd7e20 - std::backtrace_rs::backtrace::libunwind::trace::he615646ea344481f at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/std/src/../../backtrace/src/backtrace/libunwind.rs:93:5

1: 0x5617abcd7e20 - std::backtrace_rs::backtrace::trace_unsynchronized::h6ea8eaac68705b9c at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5

2: 0x5617abcd7e20 - std::sys_common::backtrace::_print_fmt::h7ac486a935ce0bf7 at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/std/src/sys_common/backtrace.rs:65:5

3: 0x5617abcd7e20 - <std::sys_common::backtrace::_print:isplayBacktrace as core::fmt:isplay>::fmt::h1b5a095d3db2e28f at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/std/src/sys_common/backtrace.rs:44:22

4: 0x5617abcfb4fe - core::fmt::write::h445545b92224a1cd at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/core/src/fmt/mod.rs:1209:17

5: 0x5617abcd22a5 - std::io::Write::write_fmt::h55a43474c6520b00 at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/std/src/io/mod.rs:1682:15

6: 0x5617abcd7be5 - std::sys_common::backtrace::_print::h65d20526fdb736b0 at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/std/src/sys_common/backtrace.rs:47:5

7: 0x5617abcd7be5 - std::sys_common::backtrace::print::h6555fbe12a1cc41b at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/std/src/sys_common/backtrace.rs:34:9

8: 0x5617abcd947f - std::panicking::default_hook::{{closure}}::hbdf58083140e7ac6 at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/std/src/panicking.rs:267:22

9: 0x5617abcd91ba - std::panicking::default_hook::haef8271c56b74d85 at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/std/src/panicking.rs:286:9

10: 0x5617abcd9b78 - std::panicking::rust_panic_with_hook::hfd45b6b6c12d9fa5 at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/std/src/panicking.rs:688:13

11: 0x5617abcd9917 - std::panicking::begin_panic_handler::{{closure}}::hf591e8609a75bd4b at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/std/src/panicking.rs:579:13

12: 0x5617abcd82cc - std::sys_common::backtrace::__rust_end_short_backtrace::h81899558795e4ff7 at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/std/src/sys_common/backtrace.rs:137:18

13: 0x5617abcd9632 - rust_begin_unwind at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/std/src/panicking.rs:575:5

14: 0x5617aa954b93 - core::panicking::panic_fmt::h4235fa9b4675b332 at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/core/src/panicking.rs:65:14

15: 0x5617aa954e53 - core::result::unwrap_failed::ha17dbf463031a5e1 at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/core/src/result.rs:1791:5

16: 0x5617aaa40c38 - <core::future::from_generator::GenFuture as core::future::future::Future>::poll::hcb7bfc161c97891f

17: 0x5617aaa04412 - tokio::macros::scoped_tls::ScopedKey::set::h8de03f2f240f3d5e

18: 0x5617aaa41fd6 - <core::future::from_generator::GenFuture as core::future::future::Future>::poll::he5f1dd2a5ce2c685

19: 0x5617aa9fbcb5 - std::thread::local::LocalKey::with::he408026e1b71d96d

20: 0x5617aaa8c009 - tokio::runtime::basic_scheduler::Context::enter::h67191af49f86c93d

21: 0x5617aaa04079 - tokio::macros::scoped_tls::ScopedKey::set::h39adab473297f56f

22: 0x5617aaa8bc92 - tokio::runtime::basic_scheduler::BasicScheduler::block_on::h7649b0c951ad27b3

23: 0x5617aaa5e6bc - tokio::runtime::Runtime::block_on::h4d77652f512ef4e4

24: 0x5617aa9ee675 - lemmy_server::main::hcc83c6ed481ae235

25: 0x5617aaa66756 - std::sys_common::backtrace::__rust_begin_short_backtrace::h9790edc13cc3de5c

26: 0x5617aaa56e73 - std::rt::lang_start::{{closure}}::h48fcb55ce09f4a36

27: 0x5617abccdb9b - core:ps::function::impls::<impl core:ps::function::FnOnce for &F>::call_once::h072eb4cd8da964ba at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/core/src/ops/function.rs:286:13

28: 0x5617abccdb9b - std::panicking::try::do_call::h8eca204fe9266946 at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/std/src/panicking.rs:483:40

29: 0x5617abccdb9b - std::panicking::try::h12574e1b7b2cbacb at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/std/src/panicking.rs:447:19

30: 0x5617abccdb9b - std::panic::catch_unwind::hf71522d4448329d6 at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/std/src/panic.rs:137:14

31: 0x5617abccdb9b - std::rt::lang_start_internal::{{closure}}::h65b66ac9bff580f8 at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/std/src/rt.rs:148:48

32: 0x5617abccdb9b - std::panicking::try::do_call::hfff61e33ca3db9f1 at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/std/src/panicking.rs:483:40

33: 0x5617abccdb9b - std::panicking::try::he48c8ecead279cad at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/std/src/panicking.rs:447:19

34: 0x5617abccdb9b - std::panic::catch_unwind::hd510a26bfc950ccc at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/std/src/panic.rs:137:14

35: 0x5617abccdb9b - std::rt::lang_start_internal::hc680b25eab888da9 at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/std/src/rt.rs:148:20

36: 0x5617aa9ee6d5 - main

37: 0x7fbe6fad4d0a - __libc_start_main at ./csu/../csu/libc-start.c:308:16

38: 0x5617aa954fea - _start

39: 0x0 -

These variables are probably relevant:
CARGO_HOME=/usr/local/cargo
RUSTUP_HOME=/usr/local/rustup
PATH=/usr/local/cargo/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
RUST_BACKTRACE=full\

(Side note, the "code" and "quote" functions of the forum are cranky to say the least)

Any suggestion would be greatly appreciated.