@handle You might even be able to set it up so the "video resizing server" (laptop) outputs in HLS format (live video over HTTP) then you can just point VLC at a LAN IP based URL to the .m3u8 index file that ffmpeg outputs and it should stream
If quality is not an issue, GPU-accelerated video encoding might be a good bet. I don't know how old the GPU on the laptop is but there's a chance it supports GPU accelerated h264 encode. ffmpeg can do this, but sometimes it requires extra configuration to enable or properly link to the GPU device on linux
@gabek Come to Minneapolis, we have monitors in our new hackerspace here.
The rent we pay for the whole building is about the same as what you would pay for your single seat in SF, assuming you spent 40hr/week there.
We aren't making it open to the public, but we also aren't charging anyone any dues or fees. All economy mode
streaming working on capsul-flask https://stream.sequentialread.com/
Music right now: 🧔🏾👨🏾🦲👨🏿🎤 Das Racist 🎭👜🔥
@handle @linus well do you want a dedicated public IPv4 (you want to run an email server) or is a shared IP OK (Everything except email)?
Right now greenhouse does not support dedicated IPv4s yet, but its planned for the future. The nice thing about greenhouse, there's no minimum monthly payment. So once the paid service launches, you only pay for what you use. For small sites or text only type stuff, that would mean its practically free!!
Greenhouse Cloud alpha test program by the numbers!
3700 views on our self-hosted demo video
30 user accounts registered
19 successful installations:
9 linux -- command line only
3 linux with desktop application
4 macOS desktop application
3 windows desktop application
5 bugs identified and fixed
6 fully self-hosted web applications already live and in production via greenhouse!
1 month since the public alpha test was launched
@nolan Right now I think the fediverse (at least the corner of it that im exposed to) has that fresh "pre-eternal-september" feel :P
Only the people who have made a conscious decision to be here are here ... It makes for a much more pleasant experience in my opinion
@seedlingattempt@kolektiva.social
Thanks! The greenhouse daemon still has some issues to be worked out. The connection from the Threshold client to the Caddy Server was failing for the daemon instance that is embedded in the greenhouse web application aka greenhouse-alpha.server.garden. I rebooted it and now it appears to be working
@nolan thanks for the info I just wanted to make sure I wouldn't be duplicating work, for example if someone else already started it.
Hello, do you know of any work that has been done on profile edit in pinafore?
https://github.com/nolanlawson/pinafore/issues/741
Also, is there a pinafore development related real-time chat channel like matrix, slack, discord, irc ?
Thanks for the hard work on Pinafore, its really smooth to use 🤯
TEST
@seedlingattempt@kolektiva.social
Argh that sucks, did you already try hooking the monitor and keyboard up to the server?
If all else fails maybe you can take the disk out, attach it to another computer, and edit some files on there to disable some systemd services and try to boot with less things going on.
@f0x https://nixos.wiki/wiki/NixOS_on_ARM
There are already quite some community supported SBCs 👀
@f0x thats the really messed up thing about it 💀
@f0x all of this could have been avoided if docker / docker-compose had supported a standard, API-driven way to add a file into a container before running it
@f0x Yeah for mine I did a [stupid hack](https://git.sequentialread.com/forest/threshold/src/branch/multi-tenant/main_client.go#L242-L258)
JSON, YAML, TOML, all can have the same problem but its a lot more normative to warn or even error on unknown properties for those because they have a well defined namespace -- just 1 file.
@f0x I wish this kind of logging behavior would be more commonplace but everyone seems to think is weird or there's something wrong with it 🙁
@f0x In theory it could, but most software doesn't.
If we can coax the software to print its configuration file to the log on startup, at least it will indirectly let you know, because the configuration value in question will be missing. If it always prints the config on startup by default, this can even happen before we considered that the configuration part wasn't working.
In theory if the environment variable is prefixed, it might be possible to directly warn about unknown environment variables and/or low
levenshtein distance between the env var's name and a known configuration variable name.
I bet folks have been scared to implement this kind of logic for env-var-based config because of how the environment variables are often all thrown into the same global namespace, so there's a possibility of collisions with other programs running on the same machine.
The warning message for the unknown env var(s) would have to warn you that "this warning itself might be spurious" 🙃 that classic aged 30-40 years old technology flavor
I am a web technologist who is interested in supporting and building enjoyable ways for individuals, organizations, and communities to set up and maintain their own server infrastructure, including the hardware part.
I am currently working full time as an SRE 😫, but I am also heavily involved with Cyberia Computer Club and Layer Zero