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:

1. lattice loads up the config from config.json
2. lattice checks if there is an existing admin
3. if none, the tool shown on the screenshot will appear! afterwards, it’ll proceed
4. 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.

web OS in progress!

i have started working on the web OS, and experimented with a way or two to make it communicate and work with apps (even external ones!)

for the ui, i’m referencing both mac OS and ubuntu. i also decided to mix in a bit of the zed browser experience.

in the background, i further refined the install script as well as started working on authentication.

what’s next

i’ll continue working on the web OS, and once the design is good enough, i’ll proceed with the IPC mechanics and maybe build up an app or two.

log 1

started with the project! first, i made go echo work, then started toying around with serving static files but realises thats not what the project should have hahahaaa.

afterwards, i added a configuration system so now it reads config from ./config.json. you can change the port and where the data file is located.

i also created a sqlite database to store things (just admin user/pass/salt for now). will be adding more data to that in the upcoming updates

finally, i created a bash installer script! so later users can install this to their server using a single command (which then opens an interactive installer as shown in attached picture, still work-in-progress)

whats next

i will either build a console mode so you can change the default admin credentials via CLI, or work on the web OS part of the project. stay tuned!

imported my old blog posts (now into journal entries), i think journal system development is done? its 1 am and ill go to bed now lol

journals are now in a separate repository (still compiled by the office), and the office is now up and running online!

added canvas for HTML games, projects and journals now have its content dynamic and requires no recompilation to show new content. very happy!

added a projects list, its dynamic. also added URL shorteners!

done with the landing page. whats left now is building a minigame next to the About section so visitors get to play and stay for a bit longer

the web server works, figured out a CRT-based design i liked, built a header and wrote some JS to make it cooler!