I got my new Greenhouse desktop application working this week; it can publish a local listening port or a folder full of files to the internet via the greenhouse cloud service. Check out the screencasts I posted on my blog!
https://sequentialread.com/greenhouse-development-update-may/
@forestjohnson This seems like a cool project and I'd like to follow along, but I found it hard
as a newcomer to grasp what was happening in those videos. The text describes the "how" but doesn't explain much of the "what," so it wasn't clear to me what the user was trying to accomplish in the videos.
Separately, on Chrome+Win10, the videos aren't seekable, so it may be helpful to speed up the parts where there's no user interaction.
@michael Thanks for the feedback, it really helps me to know when I miss.
yikes, non-seekable video, definitely switching back to H264 as the default.
At very least for now I can add a summary at the top describing what greenhouse does and why I'm building it, plus link to another post expanding on that.
In the future I plan on doing much more professional presentation for this stuff, for now I'm focused on getting the software put together and ready to go out the door with an "alpha" sticker on it.
@michael Ok, I got it fixed.
It looks like the windows html5 video player implementation disables seeking if the http server serving the video does not support http byte range requests. So I added that to my crappy file upload app and now it works on windows.
@forestjohnson I like the summary! Very helpful in framing the post. One piece I think would be helpful to link back to the main project page at the top and bottom.
The piece that's still missing for me is that I'm interested in self-hosting services, but I'm afraid of allowing it to be an attack vector into my home network. It seems like Greenhouse hints that it will help protect me, but I'd love for the project page to give more of an explanation of why I can trust it.
@forestjohnson Hmm, I'm still not able to seek. I see my browser downloading the mp4 instead of the webm, but I still can't seek in Chrome or Edge. Firefox works, though (all Win10).
One other possible clue: when I try to open the mp4 URLs directly, they download instead of playing in the browser. Usually when I do that, they play directly in the browser, but that might just be a HTTP header issue on those files.