SurrealDB
Replies: 9 comments 15 replies
-
|
I vote for the daemonization functionality within the SurrealDB command-line tool. |
Beta Was this translation helpful? Give feedback.
-
|
I can create the debians packages for linux debian, and ubuntu based system, x86 and raspberry pi arch I can change the Cargo.toml in surrealdb repo if is the desired approach Please create the issue |
Beta Was this translation helpful? Give feedback.
-
|
Hi @koakh what changes would need to be made to the Cargo.toml for the debian/ubuntu/raspberry packages? |
Beta Was this translation helpful? Give feedback.
-
|
Hello @tobiemh |
Beta Was this translation helpful? Give feedback.
-
|
This is a side slightly different feature to the daemonization functionality being built into the surreal command-line tool / server itself though yeah? Shall we add a new discussion for building debian/ubuntu/raspberry packages, or am I misunderstanding this? |
Beta Was this translation helpful? Give feedback.
-
|
Hello @tobiemh Currently in deb distros we use Makefile and deb tools to build debian packages, is a lot more complex, but its not hard Luckily in rust ecosystem we have the best tooling, and in this case we have cargo-deb With that we build the Debian package, with manifest and systemd service too, but in a friendly easy way I can start prepare everything for next release alpha6 that I suspect is comming soon :) We install and thats all, service will be running in background like all others sshd, samba, bind etc we use it like # install
$ sudo dpkg -i surrealdb.deb
# enable service and start service
$ systemctl enable --now surrealdb
# start
$ systemctl start surreald
# stop
$ systemctl stop surrealdb
etcI think I have time to do it later, and make a PR If surrealdb have a exposed log file please sent me the location, like /var/log/surrealdb.log We can have env variables in systemd service, to tweak systemd service to, like port etc, this way we can override port 8080, but for this think about a free port like 8228 |
Beta Was this translation helpful? Give feedback.
-
|
Yeah I know about the apt lists and yum. Does the package server have a specific folder structure, or can we set how we want the urls/packages/files to work? Currently we have a folder structure like this for downloads (for example): Could we put the deb/rpm packages in there? |
Beta Was this translation helpful? Give feedback.
-
|
I like the idea of a simple one line curl (like our install script)... |
Beta Was this translation helpful? Give feedback.
-
|
the structure is ├── Packages
├── Packages.gz
├── genPackages.sh
└── pool
├── clk
│ ├── a
│ ├── c
│ ├── c3
│ └── m
├── main
│ ├── l
│ ├── n
│ └── s
└── multiverse
├── m
├── n
└── sand its for me is always best to reverse proxy it, and have it's own subdomain, I thing best for right now until we start to think about to create packages servers for everything is using something like one line curl install for ex like $ curl https://download.surrealdb.com/v1.0.0-beta.5/debian/surrealdb-v1.0.0-beta.5.darwin-amd64.deb -o /tmp/surrealdb-v1.0.0-beta.5.darwin-amd64.deb && sudo dpkg -i /tmp/surrealdb-v1.0.0-beta.5.darwin-amd64.debor create a script user friendly like $ curl --proto '=https' --tlsv1.2 -sSf https://download.surrealdb.com/debian/install | shand obvious inside the script we have the first snippet that download and install (curl) in the meantime, until you think about I will start demonize and create the service for surrealdb Could we put the deb/rpm packages in there? I don't recommend package server right now, user must add it to /etc/apt/sources.list and apt update && apt install surrealdb |
Beta Was this translation helpful? Give feedback.
-
|
Awesome @koakh can you explain the server structure a little bit more (what each folder is for)? |
Beta Was this translation helpful? Give feedback.
-
|
Pool clk, main, and multiverse are folders for type of repositories
And inside every one, are inside first letter of package The c3 is our product and every package are prefixed with c3 ex c3-system-tailor |
Beta Was this translation helpful? Give feedback.
-
|
Personally, I don't like to install a package. I always prefer single binary and in my opinion daemonization functionality within the SurrealDB command-line tool is the right solution. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @ansarizafar yep this dep/rpm solution is only one solution to the daemonization issue - and is a good to have anyway. I've attempted adding daemonization within the binary itself, but it is a little more complex, and we would have to overcome some obstacles (the program currently crashes when attempting to open a webserver port after the daemon has been formed). |
Beta Was this translation helpful? Give feedback.
-
|
Hello @ansarizafar I understand your preferences But systemd service has other things like start service on reboot, is more user friendly, we can see logs, start, stop, enable, disable services, and this is what is used in linux distros everywhere But there is some binariea that have a flag for run in background to like -d etc In this case this solution is just a option for debian releases, and I think @tobiemh is open for other options to What is your OS? @ansarizafar in nix we can run commands in background, |
Beta Was this translation helpful? Give feedback.
-
Are there any updates about daemonization?I would like to use SurrealDB on production but I have concerns about when the server crash etc.
I agree, is it will be better if it can handle the demonization binary itself. |
Beta Was this translation helpful? Give feedback.
-
|
There are several aspects to this conversation
For the native support, it should be easy enough to add by using the POSIX For the install script, it looks like we would follow what @koakh has been proposing. For the systemctl script, we could definitely add this. I would also like to add that there is the option to call |
Beta Was this translation helpful? Give feedback.
-
|
I would encourage you to use any of the init systems provided by your operating system. If the Surreal CLI spawns the SurrealDB server and lets it run in the background, you lost control over it. Nothing will start it again in case something happens to it: server reboots, the kernel kills it because of OutOfMemory, it simply crashes... that's why the OSes provide Systemd and similar systems. |
Beta Was this translation helpful? Give feedback.
-
|
hello buddies in the past I use I thing is not a good practice, and a no way to go, we will pollute the surrealdb project with stuff that is not useful there (IMHO) maybe we can create a project with Makefiles and scripts to package the different formats When I have some free time, I can do the scripts for a .deb from a surrealdb stable binary, both can share systemd service etc when I arrive at home I can check my cargo-deb work that I made almost 14 months, what are your opinion? |
Beta Was this translation helpful? Give feedback.
-
|
that would be awesome. I created this issue about creating packages for different distros and versions: #2638 The original motivation for it (GLIBC version) I plan to solve it using another approach, but having We already have https://github.com/surrealdb/surrealdb/tree/main/pkg and I know Tobie was using |
Beta Was this translation helpful? Give feedback.
-
|
I only suggest the separation to not pollute surrealdb repo, and cargo-deb only work with......yes debs....even if we have other options in the future the repo will be polluted..... about GLIBC we can try build surrealdb with a Ubuntu 16.04 version that uses a old GLIBC, I think that it will work in next versions of GLIBC, we can try... UPDATE: I'm already build surreal db on a ubuntu 18.04 machine # check current glibc
$ ldd --version
ldd (Ubuntu GLIBC 2.27-3ubuntu1.6) 2.27when I have the bin can you try to try that it works higher GLIBC versions? cold build # all OS tests with same binary builded on ubuntu-1804
# build on ubuntu-1804
[cargo-make] INFO - ==================Time Summary==================
[cargo-make] INFO - build: 99.84% 632.02 seconds
[cargo-make] INFO - [Setup Env]: 0.08% 0.52 seconds
[cargo-make] INFO - [Setup Env - Crate Info]: 0.07% 0.44 seconds
[cargo-make] INFO - [Setup Env - Rust]: 0.01% 0.07 seconds
[cargo-make] INFO - [Setup Env - Git]: 0.00% 0.01 seconds
[cargo-make] INFO - [Load Makefiles]: 0.00% 0.00 seconds
[cargo-make] INFO - end: 0.00% 0.00 seconds
[cargo-make] INFO - [Setup Env - Duckscript]: 0.00% 0.00 seconds
[cargo-make] INFO - [Setup Env - CI]: 0.00% 0.00 seconds
[cargo-make] INFO - [Setup Env - Project]: 0.00% 0.00 seconds
[cargo-make] INFO - [Setup Env - Vars]: 0.00% 0.00 seconds
[cargo-make] INFO - init: 0.00% 0.00 seconds
[cargo-make] INFO - ================================================
# KO on ubuntu 16.04 with bin builded in ubuntu-1804 (Ubuntu GLIBC 2.27-3ubuntu1.6)
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.7 LTS"
$ target/release/surreal version
target/release/surreal: /lib/x86_64-linux-gnu/libm.so.6: version GLIBC_2.27 not found (required by target/release/surreal)
target/release/surreal: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version CXXABI_1.3.11 not found (required by target/release/surreal)
target/release/surreal: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version GLIBCXX_3.4.22 not found (required by target/release/surreal)
target/release/surreal: /lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.27 not found (required by target/release/surreal)
target/release/surreal: /lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.25 not found (required by target/release/surreal)
# OK on ubuntu 18.04 with bin builded in ubuntu-1804 (Ubuntu GLIBC 2.27-3ubuntu1.6)
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.6 LTS"
$ target/release/surreal version
1.0.0+20231116.690ebd32 for linux on x86_64
# OK on ubuntu 20.04 with bin builded in ubuntu-1804 (Ubuntu GLIBC 2.27-3ubuntu1.6)
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04.6 LTS"
$ /tmp/surreal version
1.0.0+20231116.690ebd32 for linux on x86_64
# OK on ubuntu 22.04 with bin builded in ubuntu-1804 (Ubuntu GLIBC 2.27-3ubuntu1.6)
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.3 LTS"
$ target/release/surreal version
1.0.0+20231116.690ebd32 for linux on x86_64
# OK on ubuntu 23.10 with bin builded in ubuntu-1804 (Ubuntu GLIBC 2.27-3ubuntu1.6)
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=23.10
DISTRIB_CODENAME=mantic
DISTRIB_DESCRIPTION="Ubuntu 23.10"
$ ldd --version
ldd (Ubuntu GLIBC 2.38-1ubuntu6) 2.38
$ ./surreal version
1.0.0+20231116.690ebd32 for linux on x86_64
# KO on
$ cat /etc/lsb-release
DISTRIB_CODENAME=stoat
DISTRIB_DESCRIPTION="NixOS 23.05 (Stoat)"
DISTRIB_ID=nixos
DISTRIB_RELEASE="23.05"
LSB_VERSION="23.05 (Stoat)"
$ target/release/surreal version
bash: target/release/surreal: cannot execute: required file not found
# OK rocky linux 9
$ uname -a
Linux localhost.localdomain 5.14.0-70.13.1.el9_0.x86_64 #1 SMP PREEMPT Wed May 25 21:01:57 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
$ ldd --version
ldd (GNU libc) 2.34
$ /tmp/surreal version
1.0.0+20231116.690ebd32 for linux on x86_64
# KO [alpine-315](alpine:3.15)
$ uname -a
Linux alpine-315.links-gram 6.1.57 #1-NixOS SMP PREEMPT_DYNAMIC Tue Oct 10 20:00:46 UTC 2023 x86_64 Linux
$ target/release/surreal version
bash: target/release/surreal: No such file or directory
$ ldd --version
musl libc (x86_64)
Version 1.2.2my notes of the build $ distrobox-create --name ubuntu-1804 --image docker.io/library/ubuntu:18.04
$ distrobox-enter ubuntu-1804
# check current glibc
$ ldd --version
ldd (Ubuntu GLIBC 2.27-3ubuntu1.6) 2.27
$ sudo apt install build-essential llvm-dev libclang-dev clang cmake git -y
$ curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
$ git clone https://github.com/surrealdb/surrealdb.git
$ cd surrealdb
$ make buildif anyone want to try to test this build version download the surreal standalone binary @ surreal.tar.gz so must power in a 29M binary, this is not real! must be surreal! pure black magic :) remember one company that I work in the past, that loves the shit made by M$ |
Beta Was this translation helpful? Give feedback.
-
|
for reference, this PR will build official binaries based on Ubuntu 18.04: #3014 |
Beta Was this translation helpful? Give feedback.
-
It would be useful to be able to start the SurrealDB server in the background, and use the SurrealDB command-line tool to stop the server in the background.
The first way to handle this would be to use the default shell syntax to start the server in the background and redirect the stdout to a logfile. We could then create a surreal-ctl command-line tool for managing the shell arguments easier.
Alternatively we could implement the daemonization functionality within the SurrealDB command-line tool itself, so that we don't have to create a separate command-line tool for managing the background process (using https://crates.io/crates/daemonize for example) with the following commands added:
and stop it with
Beta Was this translation helpful? Give feedback.
All reactions