I added an endpoint to the platform API (GET /api/services) that returns all of the clients services.
On start, the virtual server will request services to run, and start them one concurrently using golangs channel features (containers to run are added to a queue where up to five containers are handled at a time)
I implemented the backend for ordering a service.
Diagram explaining flow
Text scored with red has not been implemented yet
It works by
This setup is pretty complicated but it allows for virtual servers to run virtually anything and have configuration options for all of it.
I have yet to implement:
You can now add services through an API, using a generated client id and secret.
A server would call the API, passing a list of products to sync. You pass a name, description, unique code, a price and a pricing schedule (per hour, day, or month). You can also add addons with options, currently only text or numbers (e.g for additional RAM).
I also added a page to view all available services.
Next I’ll implement “getting” the service
Added an env variable (MAIL_ENABLE) that will disable any email sending and functions like verification. With this enabled, signing up will automatically mark the account as verified and sign them in, skipping the verify step.
Did this so I can develop entirely locally and without internet, I’m on holiday in the Outer Hebrides where internet isn’t great. Writing this on a 7 hour ferry
Also changed the flags field from bigint -> integer to save space, I won’t need 64 bits)
I added a page to view, manage and create API clients. This is what the past couple of devlogs have been leading up to, there was a lot of interactivity required for this.
These will be used to programmatically set up “virtual servers”, which will be able to register “products” to the platform, and receive services to deploy, and they manage where to deploy them, for example on the current server, or provision a VPS, or to GKE, or a docker swarm. I’m designing it to be as flexible as possible.
I also added a copy button component
Need to implement actions next, probably just delete
I added tables and modals to my UI library. I needed these for my next platform update.
Tables were more annoying to implement than you’d expect, the browser makes them pretty hard to style.
Modals on the other hand were pretty quick to implement, I just used my existing card component.
My UI library is coming together pretty quickly, I’ve now implemented most of the components you’d need for a interactive website!
I added a sign in page, implemented session tokens, and fixed a few bugs
I also made it so you are automatically signed in after verifying your account. This is secure because a verification session is only made after signing in or creating an account.
Honestly I thought this would take longer to implement, but I have done this a million times before.
Next I’ll implement the account page.
When you create an account, an email with the verification code gets sent.
You are redirected to a verification page, where you can enter the code, submit and your account gets marked as verified.
The page after verification is not implemented.
To do this, I:
Next, I’ll implement signing in (with sessions)
I built a verification page (server side stuff not implemented yet) and to do this I build a custom code input.
It automatically focusses the next input when typing, or the previous when backspacing.
I also added support for pasting codes. In the video demo, after pasting the focus doesn’t go to the last input but I have since fixed this.
Next up, I’ll set up SMTP with AWS SES and get verification working on the server side.
There a fair bit of set up involved with this.
I had to:
So now you can create an account. You can’t do anything yet, and I need to implement the next step of the flow, which is to verify your email.
