5 ms·

Hi. Just to clarify. > Node 21 with NPM > Sveltekit, shadcn-svelte The front-end things are used during the build process. You don't need them when deploy. >

Hi. Just to clarify. > Node 21 with NPM > Sveltekit, shadcn-svelte The front-end things are used during the build process. You don't need them when deploy. > And the documentation literally specifies it requires docker. Fusion can be deployed as a *single binary*. Docker is just the recommended way. Maybe we need to make documentation clearer.

drusklo 2y ago
Looks good! I am curious on why you recommend to deploy using docker, being a single binary with no external dependencies I find the deployment simple enough. I write all my personal projects using Go and one of the things I most like is that it compiles to a binary without external dependencies.
- rook1e_dev 2y ago
  That's mostly for Windows users. The SQLite driver uses cgo, so we use both Ubuntu and Windows Server in CI to avoid cross-compiling. However, we still can't confirm that it's 100% ok on Windows. If any weird bugs occur on Windows, we don't have much experience or energy to deal with them. The Docker image is based on Debian, we are more familary with it.
  - drusklo 2y ago
    That makes a lot of sense, thanks for taking the time to explain it.
  - _lvbh 2y ago
    For the SQLite driver, check out the one by modernc for pure Go
holsta 2y ago
It's an interesting difference in backgrounds, maybe? I tried to build this on OpenBSD where we don't have docker and we use 'make' instead of random shell scripts. For what it's worth, this is from the build log: error code 1 error path /home/holsta/3rdparty/fusion/frontend/node_modules/@sveltejs/kit error command failed error command sh -c node postinstall.js error /home/holsta/3rdparty/fusion/frontend/node_modules/rollup/dist/native.js:84 error throw new Error( error ^ error error Error: Your current platform "openbsd" and architecture "x64" combination is not yet supported by the native Rollup build. Please use the WASM build "@rollup/wasm-node" instead.
- rook1e_dev 2y ago
  It seems like the compiler used in project's front-end framework doesn't support OpenBSD. There is nothing we can do about it at the moment. Maybe in the future we will change the tech stack to reduce the complexity of the front-end.
remram 2y ago
Why recommend Docker if it's a single binary? And what's good about a single binary if you're going to recommend Docker?
- fragmede 2y ago
  it's still easier to manage docker containers if they're 50 MB instead of 300MB and if the rest of the fleet is being managed via docker-(whichever) then there's something to be said about consistency. managing everything through one interface is easier than remembering all the special cases. but to each their own.
  - remram 2y ago
    The image is 200 MB... There's 100 packages in there, including bash, perl, ext filesystem utilities, and the APT package manager. Compared to all that, the current PHP app I use for RSS looks lighter. Especially since my VPS already runs PHP and PostgreSQL.
    - rook1e_dev 2y ago
      You can use the standalone binary (18 MB) to run it. Docker is just one deployment method.
      - remram 2y ago
        But then why... Hold on, I'm back to my earlier comment.
        fragmede 2y ago
        Consistency is key. it's easier if you're using docker to run all the things, then docker ps shows all the things running, instead of having to check docker, and then also check this other thing over here that's different
        ralferoo 2y ago

drusklo 2y ago

Looks good! I am curious on why you recommend to deploy using docker, being a single binary with no external dependencies I find the deployment simple enough. I write all my personal projects using Go and one of the things I most like is that it compiles to a binary without external dependencies.

rook1e_dev 2y ago
That's mostly for Windows users. The SQLite driver uses cgo, so we use both Ubuntu and Windows Server in CI to avoid cross-compiling. However, we still can't confirm that it's 100% ok on Windows. If any weird bugs occur on Windows, we don't have much experience or energy to deal with them. The Docker image is based on Debian, we are more familary with it.
- drusklo 2y ago
  That makes a lot of sense, thanks for taking the time to explain it.
- _lvbh 2y ago
  For the SQLite driver, check out the one by modernc for pure Go

holsta 2y ago

It's an interesting difference in backgrounds, maybe? I tried to build this on OpenBSD where we don't have docker and we use 'make' instead of random shell scripts. For what it's worth, this is from the build log: error code 1 error path /home/holsta/3rdparty/fusion/frontend/node_modules/@sveltejs/kit error command failed error command sh -c node postinstall.js error /home/holsta/3rdparty/fusion/frontend/node_modules/rollup/dist/native.js:84 error throw new Error( error ^ error error Error: Your current platform "openbsd" and architecture "x64" combination is not yet supported by the native Rollup build. Please use the WASM build "@rollup/wasm-node" instead.

rook1e_dev 2y ago
It seems like the compiler used in project's front-end framework doesn't support OpenBSD. There is nothing we can do about it at the moment. Maybe in the future we will change the tech stack to reduce the complexity of the front-end.

remram 2y ago

Why recommend Docker if it's a single binary? And what's good about a single binary if you're going to recommend Docker?

fragmede 2y ago
it's still easier to manage docker containers if they're 50 MB instead of 300MB and if the rest of the fleet is being managed via docker-(whichever) then there's something to be said about consistency. managing everything through one interface is easier than remembering all the special cases. but to each their own.
- remram 2y ago
  The image is 200 MB... There's 100 packages in there, including bash, perl, ext filesystem utilities, and the APT package manager. Compared to all that, the current PHP app I use for RSS looks lighter. Especially since my VPS already runs PHP and PostgreSQL.
  - rook1e_dev 2y ago
    You can use the standalone binary (18 MB) to run it. Docker is just one deployment method.
    - remram 2y ago
      But then why... Hold on, I'm back to my earlier comment.
      - fragmede 2y ago
        Consistency is key. it's easier if you're using docker to run all the things, then docker ps shows all the things running, instead of having to check docker, and then also check this other thing over here that's different
      - ralferoo 2y ago