Sylvia

6 days ago

Sylvia
6 days ago

Played a bit more with #fruitstand (github.com/BasementCat/fruitst…) from @Wren this evening, now my ePaper display (seeedstudio.com/XIAO-7-5-ePape…) came in.

I've never been so excited seeing an "Internal Server Error" displayed on the screen, because it comes from the server!

In just an evening I got my CI-built container properly tested, reported some bugs, fixed an issue and got the ESP32 properly linked to the Fruitstand webserver with #esphome.

Been a while since I enjoyed hacking on stuff this much :)

GitHub - BasementCat/fruitstand

Contribute to BasementCat/fruitstand development by creating an account on GitHub.

^GitHub

#esphome #fruitstand @Wren 🐁

in reply to Sylvia

Sylvia

in reply to Sylvia 6 days ago

Wouldn't surprise me if the Internal Server Error is me doing something wrong too, not trying to blame Fruitstand. Just, *sighs comfortably*, it's fun learning something new and progressing quickly :)

in reply to Sylvia

Wren 🐁

in reply to Sylvia 6 days ago

oh, there's likely bugs! I need to poke back at it a little more, I've been busy with too many projects lately!

in reply to Wren 🐁

Sylvia

in reply to Wren 🐁 6 days ago

Hope you're having fun with the projects :) I have all the patience in the world, don't worry, take your time! I'm already very glad for what Fruitstand already is starting to shape up to be, it's exactly what I was looking for :)

in reply to Sylvia

Wren 🐁

in reply to Sylvia 6 days ago

oh, re: this, you might just need to run database migrations (should be in the readme)

in reply to Wren 🐁

Sylvia

in reply to Wren 🐁 6 days ago

I'm not seeing the DB migration in the README but yeah that was one of the issues I ran into (I'm thinking the Docker container should probably just auto-migrate on launch), but sadly that's not this issue: github.com/BasementCat/fruitst…

I'm starting to feel it may be some config issue, like, maybe there is no default config for plugins until you explicitly save. And maybe they're not saving on my side for some reason. I'll debug more later, I'm already glad about the progress of yesterday :)

Add Docker build and publish workflow by TheLastProject · Pull Request #11 · BasementCat/fruitstand

Fixes #3 It was a bit longer ago then I remembered last touching Docker stuff on GitHub Actions (most of my more recent experience is on GitLab CI and Woodpecker CI, which I personally prefer). Giv...

^GitHub

in reply to Sylvia

Sylvia

in reply to Sylvia 1 day ago

You were right about the database migration being documented in the README, my bad!

I'm not sure which exact action got stuff working eventually, but well, Fruitstand is working for me now, which is lovely :)

I'd like to document how to make seeedstudio.com/XIAO-7-5-ePape… work with Fruitstand somewhere. Do you have any preference? A new page under github.com/BasementCat/fruitst…? Something else?

The XIAO 7.5" ePaper Panel displaying a quote on an image rendered by the Open Source Fruitstand project

BasementCat/fruitstand

Contribute to BasementCat/fruitstand development by creating an account on GitHub.

^GitHub

in reply to Sylvia

Sylvia

in reply to Sylvia 1 day ago

@aks Just noticed your progress on Queerminal (scalie.zone/@aks/1151257995352…), very cool! Given we both seem to really want a non-queerphobic TRMNL alternative, I just figured I'd ping you here to show you Fruitstand running on similar hardware in the hope it might interest you. If you'd rather I not bother you with this let me know! :)

Akseli :quake_verified: :kde: (@aks@scalie.zone)

Managed to make my TRMNL server "Queerminal" to support modules, so it now loops between an RSS feed and my calendar. Next up I need to make a weather view. Then clean up the code **a lot** and maybe it's ready for more public usage.

^{Scalie Zone}

@Akseli

in reply to Sylvia

Akseli

in reply to Sylvia 1 day ago

ooh thank you, im definitely interested.

I probably will keep going on with my project because I find it fun but I'll check out Fruitstand too!

in reply to Akseli

Sylvia

in reply to Akseli 1 day ago

@aks Fun is the best reason to work on a project :)

@Akseli

in reply to Sylvia

Wren 🐁

in reply to Sylvia 1 day ago

I'm not super familiar with how the GitHub wiki thing works - having it easy to access would be great, but it'd be nice if it wasn't tied to GitHub (though that all still lives in the repo, right?)

in reply to Wren 🐁

Sylvia

in reply to Wren 🐁 1 day ago

GitHub wikis do get their own semi-hidden repo (URL visible on the bottom, see github.com/TheLastProject/frui…) but the wiki format is kinda... GitHub-specific. If your goal is to have less vendor lock-in I would personally suggest GitHub Pages instead as you can mostly move that as-in to GitLab Pages or (sadly in maintenance mode) Codeberg Pages. Or build it with a third party tool like Netlify. Of course, you should put that behind an own domain to not be stuck with a github.io domain.

test

Contribute to TheLastProject/fruitstand development by creating an account on GitHub.

^GitHub

This entry was edited (1 day ago)

in reply to Sylvia

Sylvia

in reply to Sylvia 1 day ago

"Mostly" as in, whatever is in the "pages" branch gets published as HTML, so you will have to modify your build scripts for the CI system you switch to. But given the commands will stay the same that would be fairly minimal amounts of work.

Then we get to the level of multiple repositories though, so you may want to move Fruitstand to a GitHub organisation for clarity (though not required).

Could also just put markdown files in the current Fruitstand repo but that is more limiting.

in reply to Sylvia

Wren 🐁

in reply to Sylvia 16 hours ago

for now the wiki probably makes the most sense (path of least resistance and all that) - better to have documentation at all than to spend way too much time trying to find the "best" solution (I'm not likely to move this off of GitHub soon so I'm just not going to worry about it for the moment)

in reply to Wren 🐁

Sylvia

in reply to Wren 🐁 14 hours ago

Understandable! It seems I have permission to edit the Wiki (it might be set to public), so it accidentally published the moment I hit save. I hope that's okay anyway :)

I might tweak this if more stuff comes up, but for now, I'm considering github.com/BasementCat/fruitst… to be "correct documentation". Feel free to change/ask as you see fit :)

XIAO 7.5" ePaper Panel

Contribute to BasementCat/fruitstand development by creating an account on GitHub.

^GitHub

⇧

Sylvia 6 days ago • •

Sylvia
6 days ago