bashtickets VS daedalOS

A nice terminal-based ticketing system. https://github.com/tpapastylianou/bashtickets

v2 on master is as simple as it gets, but still incredibly functional; my team is dogfooding the hell out of it at work.

v3 on the "commandbased" branch is a total rehaul on the works, hoping to make this a more traditional/complete package, with a command-based interface (i.e. similar to how git works)

I created something similar when I had to work in an extremely resource-constrained project (we could only work by ssh'ing to a server with no graphical utilities, and no internet access other than ssh). It has worked like a charm, and I would find it difficult to go back to anything else for ticket management now. I use this for 'in-project tickets/milestones' and leave stuff like github issues for 'external' issues by users.

Here it is on github for anyone who's interested: https://github.com/tpapastylianou/bashtickets

My tool is slightly less minimal than the one in the article, but essentially the same philosophy. Everything is a local file following a simple but fixed template, so that they can be grepped / manipulated if necessary. It plays very well with versioning, and supports milestones and 'advanced queries' as pre-made scripts. Obviously, since the tickets/milestones are simple text, it should be fairly straightforward to write your own queries if you know a bit of bash (or any other language you prefer, obviously).

In fact, this little system has worked so well, that I have recently been trying to convert it to a nice, portable, "command-based" tool, i.e. the way git works; bashtickets init (or just bt init) initialises a ticket repository, bt new ticket creates a new ticket, bt list lists open/closed tickets, or active/completed milestones etc. There's nothing wrong with the original, of course, except for the fact that it's a bit ugly to have a bag of scripts in each ticket repository you want to manage. A command-based interface simply makes it look a bit more 'modern', and clean, putting any pre-made scripts and 'template' files out of sight for peace of mind. This is still very much under development, but please see the "commandbased" branch if interested. I'd be very open to feedback :)

I've learned so much while making this project into my personal website (dustinbrett.com). It's made me a much better web developer as I have tried to emulate a desktop environment with pixel perfect accuracy using CSS, HTML & JavaScript.

I'm very happy to announce that my personal website has once again been nominated for a Webby Award!

This has also been ported to the web via Emscripten. I host it on my website if anyone wants to play. https://dustinbrett.com/?app=SpaceCadet

Demo: https://dustinbrett.com/

As someone who built a website around this idea, I agree! The desktop metaphor is powerful. If anyone wants to check it out it's at https://dustinbrett.com

Very cool! It's always refreshing to see the "OS in the browser" projects that try and actually make something functional. I've been working on one myself for nearly 3 years now, called daedalOS (https://github.com/DustinBrett/daedalOS).

The WASM kernel idea is very cool and I hope one day to be able to add something similar to my project. I think you are onto something and I am excited to see your progress as you implement the GUI.

If you want some Browserception, my desktop environment (https://dustinbrett.com/) can indeed do this. But after a few levels in Chromium you need to add a random query string (/?a=1) to the URL otherwise it stops working.