7
results
for projects
-
Another project So I decided to create another project, this was mainly to re-learn react, and to get back into the swing of things, so what is it Well if you can’t guess by the title, its a todo-list, specifically Todo-List.app Features Entirly private, encryption happens in browser Storage is only of the encrypted form Login is using Keycloak, so no “real” details are retained Export/Import todo.txt Unfinished features Project support (its a very simple todo, only items and sub-items atm) Github Link
-
Retro Board Update Well after a couple of months of coding ive got about 50% through doing reto-board, major progress has been made, it is now techniclly possible to sign up for it, you can’t yet make any boards, but there an example version of what a board will look like non of the functionality works in the example it took quite a while for me to get the login to work, and the main reason to that is undocumented bits that I had to get working myself, for example “can I do this / userAllowed” is not a standard feature it seems at least not in the golang libraries for keycloak, so I had to go down a very long and winding path
-
Retro Board Well I’ve started another project, retro-board.it this is just going to be a very simple app, that has a couple of options Initial Signin Ask the user what the Company name is, this is to create a subdomain with that company name (if it doesnt already exist) if the company name already exists then enter the password for the domain Ask the user for a Team name Ask if they would like to use single sign-on (Google | Github) or accounts Team Board Setup The team board starts with the following options
-
This is a bug tracking system, any time an error happens on your site it tells bugfixes in the agent for your language, then if the error occurs quickly or once in a while it informs the user some how nothing is public yet (the javascript version released needs fixing) Planned languages supported * Go * Javascript * Swift Planned notification systems * Auto-create tickets * Jira * YouTrack * Jetbrains Space * GitHub * Channel messages * Slack * Microsoft Teams * Jetbrains Space * Email GitHub Link
-
This project is so that I can deploy projects into my cluster using github pipelines now that sounds simle enough, except there aren’t any (from my limited research) deployment agents for kubernetes that work on arm So whats my plan, well this system works thus Method There is a github action that is triggered in your pipeline, this talks to an orchestrator on k8sdeploy the orchestrator then sends a message to a queue with a topic for an agent that has been registered by you for your cluster
-
Progress has been slow to start with, but that should now speed up I have finished the authorizer, and moved the storage system to Postgres from Dynamo, the main reason for that is that a lot of the data is relational so it makes sense to put it in a relational database Nest This is the service where all CRUD operations take place, it is also what triggers Hive Hive This is the service that works out what to do with a bug, is it a new one, has it happened before, is it happening frequently, it also triggers the notification system
-
I have decided to go back to BugFix.es and re-start development mainly this is due to me needing a common bug/issue tracking system (this is not a ticket system like jira) BugFix.es tracks bugs, so if a bug is sent to the system and it hasn’t been seen before or was seen a long time ago, or is happening a lot in a short period of time it creates a ticket / notification so development on it can be tracked/done