expyth0n

u/expyth0n@lemmy.world
5 posts · 54 comments

Recent posts

Recent comments

node-red is a flow engine, you wire up automations and walk away. ideon is a workspace you actually live in: git, notes, files, tasks, all on a spatial canvas your team navigates together :)

yjs too! the trick that worked for me was just not round-tripping yjs -> json -> db on every update, canvas state lives in leveldb as raw binary (y-leveldb), the relational db is only used to seed it when the doc is empty. after that leveldb takes over. y-indexeddb on the client for offline, works pretty well actually

on your second question yeah same struggle lol. connections are loose by default, to keep it manageable folders have a single-parent rule, no reverse refs, collapsing hides the whole subtree. frames are there too but purely visual. for kanban task relationships i just moved them out of the canvas entirely and stored them in the yjs content object, otherwise the graph gets unreadable fast

auto clustering and edge bundling are still missing tbh, when the graph grows it gets messy and right now the answer is just "use folders and frames", not super satisfying

the freeform vs structure thing is something i keep going back and forth on, leaning toward soft constraints that nudge rather than block. curious what you're doing on that front!

Fair point. Docker is the only install path right now. I'm a solo dev and I can't properly test across multiple platforms yet. A desktop app is on my list, it'll happen if the project grows enough to justify it. And if you ever recover that energy, PRs are open :D

thanks, if it helps, you can double click on the lines connecting blocks then you can enter sum text to append a tag on connections :

for Excalidraw, there's no specific reason, i just use excalidraw everyday lol so I choosed it, but I can look for a drawio integration ;)

There is already a non-piped docker-compose setup. The installer just downloads the compose file and env.example, and you can also get them manually from GitHub.

You don’t need to set APP_PORT. If it’s unset, the app falls back to the PORT var provided by Portainer. Just make sure APP_URL exactly matches the root path you’re using behind Nginx.

I know from a friend his deployment running fine on Portainer, so it should work with a standard setup.

on Ape Coding · c/hackernews · 2 pts · 183d

ohhh man I was looking for a mobile client for a very long time, THANK YOU!