feat req: way to deploy in no-docker style, as normal service

[mckaygerhard]

checked and try to compile seems need networking and its imposible to package and distribute as is for linux distributions in alpine and debian

also i need to deploy in no docker style.. i mean in a real service.. not as container

[ViBiOh]

hi @mckaygerhard ,

Indeed it needs networking when compiling, in order to download go.mod dependencies.

For the "no-docker" style, I've made a release with self-sufficient binaries. Let me know if it's good for you. I'll make it for ViBiOh/vith too

Edit: Hum the release will not be sufficient, you need the templates/ folder, I'll improve the README for that case

[mckaygerhard]

i need a way to compiling witout network dependency .. umm i guess there's two isues here, so let this related to "no docker" way and i'll open a new one about no-network dependency

[ViBiOh]

I'll not vendor every dependencies into the repository for compiling without network. It's a very special case. If you need it, you can fork the repository.

For the "no-docker", have you tried the binary release (and the associated templates folder specified by the -templates flag) ?

[mckaygerhard]

now i read the "no-docker" is supported, THANKS! @ViBiOh .. but for now documents is not featured specially i dont understand the part of "multiple backends" but for what? storage or users db? i can collaborate with you documenting and improve a wiki in same git repo..

about vendor dependency, ok if i wants to own.-compiled how i can put my own vendors dependency in my own fork? i m more interesting in my own compiling.. cos for distro handling is need!you developers thinks always that internet is widelly used and is a lie!

[mckaygerhard]

this are done.. about compiling and packagin i openned separate one 143 .. closing ! thanks!

i will put examples and user cases when you respond to my other issues! documentation is very poor i hope i can improve it but i need you help me too!