A helper tool for hack club’s Nest that makes doing actions easier with the help of a GUI and caching and a separation of input from connection to make tasks go by faster
manitej
Whoops! Looks like they don't have a project yet. Maybe ask them to start one?
vestiral
Check their projects out: Some Smaller-than-usual Mercenaries, Realistic 3D rendering through stereoscopy, using nothing but tkinter (for rendering) and math (for computing), 3D renderer using nothing but turtle (for rendering) and math (for computing)., 3D Voxel renderer using nothing but turtle (for rendering) and math (for computing).
Once you ship this you can't edit the description of the project, but you'll be able to add more devlogs and re-ship it as you add new features!
did a lot of bugfixes between the ship to get it to even compile for windows (unfortunately i don't have a very good windows test box only a windows vista crapbox) so i did fix the shipwright feedback !!!
Completely also added JavaScript tasks too! I also did a lot of other things, like removing all unnecessary logs and fixing the fact that flows and command history didn't save (due to a problem with saving arrays using tauri stores). The JavaScript tasks include a whole user manual to indicate all the special sauce that they include, such as log statements and fetch functions that can fetch even if CORS is an issue.
Now, users can make custom flows using SSH commands. While the ones I demoed in the video seem to be (and are reasonably) useless, this does mean you can automate more mundane tasks. For example, if you need to update your server from a git pull, instead of doing a systemctl --stop server && git pull && pnpm install && pnpm run build && systemctl --start server you can just make a flow and run it whenever needed. This usecase makes sense to me because it's the reason why I'm making NestHelper.
Finished writing commands, which was quick, since all the infrastructure already exists: it's just a matter of getting it all shown in a new interface on the app. Now, I'm probably going to work on the final feature before the first ship, which is the flows feature.
This is the next step: just running commands as needed. While I wanted to put a normal shell, realistically rewriting a program that already exists wouldn't really do much for the user experience.
Got the uploads working!!! Why did this take so long? A problem that I hadn't considered was that SSH will just not even try to take your request if you send like 40 or 80 kilobytes of data through arguments. This isn't a problem when you're editing text files, but when you start to upload binary data, this problem becomes apparent. To fix this, uploads now rely on DD (yes the Disk Destroyer) and write the byte content using STDIN. This wasn't compatible with the existing flow logic, and I was not going to rewrite the existing flow logic, so Uploads are now frontend tasks that just call a command designed to upload files like this. 👍
Basically finished up the filesystem portion of the app, added an image viewer and implemented downloading of files, and you can mark files for deletion. after updating the filesystem code with an upload function, this portion should pretty much be done.
sometimes the simplest things are the most annoying: so I spent the last about 3 hours trying to implement cancelling a flow or command while in progress. The solution I came up with was to just hook into a system api and perform an unsafe SIGKILL of the underlying SSH process. if there's any data in flow being overwritten, your data is probably gone, but I guess you wouldn't cancel unless you knew the process occuring is something that doesn't need to occur. And unlike SIGKILLing a normal process on the client side, SIGKILLing SSH doesn't do much and the server can still recover normally.
woah this is cool. Just got the ability to commit file changes working. You can now edit as many files as you need and flush them out all at once. You can create new files as well. This also has the support of making sure that if a file is deleted on the server it asks you before updating so you can save your data. SO that's cool.
I got the text editing working so now you can edit files !!! Also added syntax highlighting courtesy of Monaco. Monaco is a bit heavy but since NestHelper's a desktop app anyway it doesn't seem to matter anyway.
soo this is the Filesystem browser. it took a while but is basically functional in all that it is meant to do, which is browse the filesystem. I'm probably going to import the basic syntax highlighting javascript component from codium to get text editing working, and probably also add a hex editor. image viewing should be easier, just encode bytes as a base64 string.
Got the dashboard implemented, so now you can see some important information about your current nest configuration. the debug box will probably just be for seeing how many caddy domains you have set.
Refined the SSH flow to be more modular. This should now work better when users make their own flows. First though, I'll include a couple dashboards and editing areas.
i didn't expect to make a devlog about this but it did take me 3 hours: i added the ability for the client to do things with data as part of the flow (for example if you need to see existing data in your own flow). basically the ssh session pauses until the client's promise resolves.
Due to my significant inexperience with Rust, It's been a while. However, I did just get code execution and output streaming working!!!! This current flow as shown on screen is just a demo: real flows will most likely be less hardcoded so the user can do as pleased. But the flow works after hours of learning about stupid async and move.
Got the basic flow setup working, so you can get your username. Next, I'm going to include a startup command flow that says what to do on startup of the app (so ssh hackclub.app, nest caddy list, cat Caddyfile, etc.)
Started this new project, and I'm using Tauri for the first time. NestHelper is gonna connect via SSH to get tasks done in a way that you don't have to wait for each action to slowly complete.