Lattice
- 3 Devlogs
- 4 Total hours
Lattice is a lightweight software designed to be the center of your server systems
now working on a dash!
- started work on the dashboard
- it has a header, which has a javascript that does a websocket connection to the backend to get real-time CPU usage. will expand to RAM, SSD, network, etc. later
- implemented authentication on the router level, so now you cant access the dashboard without logging in first.
challenges
- whilst implementing authentication for the router, i faced some issues with sqlite database locking. im more careful to close statements and queries now.
- the codebase is really starting to grow now so figuring out how things work is getting more and more complex
what’s next
- RAM, SSD, network usage via websocket implementation on the header
- proper home styling
- some cool charts or smth maybe
there’s a web interface now!
- added proper admin authentication handling (there’s functions to create and verify admins now)
- implemented html/template, all html files are embedded so everything can compile to a single binary
- created a basic login.html page that doesnt have any functionality (yet)
some obstacle
- i faced issues with go’s package handling as there’s import methods thats not allowed, but i fixed it thankfully hahahaaa
- getting the admin initial CLI to work as intended was a bit of a hurdle, it still doesnt run well when using tools like air.
what’s next
- authenticated web access (cookies, etc.)
- proper dashboard (lots of html tonight!)
starting with the basics!
i started by first creating functions for handling the database, configuration, and basic go echo setup.
here’s the flow of the initialisation process:
- lattice loads up the config from config.json
- lattice checks if there is an existing admin
- if none, the tool shown on the screenshot will appear! afterwards, it’ll proceed
- then go echo runs, followed by the whole Lattice system!
so i got basic database, read/write, and backend things working.
what’s next
- the authentication for frontend
- ill work on the backend for systemd management, mostly routes with some sqlite database.
- and a few more.
