Docker-free instruction #2
Labels
No Label
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Kieran/void-cat-rs#2
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I'll see if I can figure it out...
Are you looking for a
systemd
-like setup?Indeed, I usually have it run with systemd and nginx. I assume it's just something like cargo build...
What I got so far:
sudo apt install build-essential libx264-dev libwebp-dev libvpx-dev nasm libclang-dev libwebp7
libvpx7
doesn't exist on Ubuntu 24.04--prefix=$HOME
insteadPKG_CONFIG_PATH=$HOME/lib/pkgconfig RUSTFLAGS='-L $HOME/lib' cargo build -r
Try out with
LD_LIBRARY_PATH=$HOME/lib target/release/void_cat
Yea it should be whatever is in the dockerfile, the ffmpeg fork is not required afaik, its just so i can compile a smaller binary for inside docker.
The main distro release of ffmpeg should also work.
After that you just build with
cargo build --release
Then files should be in
./target/release
Ah that sounds a lot simpler.
Do you have sample nginx file? Especially with regard to which
location
entries need which CORS headers.(though I guess that's already handled by
cors.rs
)Yes it should be a simple
proxy_pass
just make sure to set theclient_max_body_size
andproxy_read_timeout
If this doesnt work i can get you the same config as https://blossom.nogood.studio/
I think it's working, though I'm getting a
Invalid auth string
when trying to post with https://nostrify.dev/upload/blossom - it did work withhttps://blossom.primal.net/
. It doesn't work withhttps://blossom.nogood.studio/
either, so maybe a protocol issue?Thats weird, ill look into this:
I think it's because you require NIP44 while Primal is either unauthenticated or NIP04.
(update: neh, probably not)
Its most likley an issue for nostrify because it already works everywhere else like https://bouquet.slidestr.net/ and snort.social
I suspect it could be missing base64 padding
Nostrify is adding a spurious
}
at the end of the auth string. I'll make a PR to remove that.I briefly worked around it by stripping the last character, though then something else goes wrong:
What does your
config.toml
look like, there should always be an error message too, check the response in nostrify.In nostrify I get this:
Config:
I'll try switching to the Ubuntu version of
ffmpeg
to see if that helps. I assume it's justlibavutil-dev
?By the way, I don't know that the
webhook_url
config is for so haven't touched the default.I dont think
$HOME/.void-cat
will work, its probably not expanding ENV varsYou can comment out
webhook_url
this is to allow authorization of file upload, via external API. (docs needed)You need
libavcodec-dev libavformat-dev libswscale-dev libavutil-dev
(im probably missing some)It needed a bit more:
So I'm not sure which of the above things fixed it, but it works!
Here's the workaround for Nostrify, pending https://gitlab.com/soapbox-pub/nostrify/-/merge_requests/91
Nice! Probably configs was the issue.
Here's an nginx example:
The three commented lines are needed for nip-96, but I haven't tested that.
Use certbot to add the necessary SSL certificate lines.
And here's a simple systemd config: