well i thought i would split up all the settings in 3 categories depending on who they impact: Customers, Storage nodes and then the rest would logical concern the satellite itself
I “think” i have managed the customers ones and i’m now at the satellite ones, where i started out with a “branding section” that should allow doing things like logo’s and links and in the end also the few pages that i found out so far, like privacy policy and such
i use github copilot as a helper tool (the pro tier) since my skills at the go language is shit, someday i get a lot done and sometimes not so much, it all depends on how many of the prem. request that goes with the subscription it takes to get things done, when they are used up i have to wait intil the first day of the month before the counter is reset
but what i got so far:
at admin loging i manged to get TOTP installed so you need a one time code from an auth app, i use google auth. app. first time you set it up on the command line, and it gives you a QR code to scan. from there everything is done on a webinterface served at port 7777 locally
as part of this i also made a feature that requires a usb stick to be inserted to change settings, without it everything goes read-only. the stick also serves as a backup location for the config.yaml
landing page after this is customers accounts:
above that in side left hand sidebar/menu i also have a small services status thing that allow me to start and stop the different services the satellite runs
now all the settings i think and assume concerns the customer looks like this:
there are far to many to show at once, but the most important one is pricing packages
this allows to setup “packages” the customer can upgrade too
below it i have stripe that is used to collect money from the customer
now the most important one you think about is the thing that does check /24 requirement
i decided to use ip-api.com when a storage nodes contacts the satellite the satellite knows where its located, and the satellite can either do as storj does where the same data will not be sent to the same /24 segment or it will not be sent to the same address so the old option is still there
but as i and many have said, why should the guy next door be punished because i have a node or the other way round
i also made a payout section for the storage nodes:
yes paypal not tokens (“funny money”), why? while crypto is great and all you never know what you get, exchange rates go up and down so much. if i where to bring this to market i think nodes should be paid in something stable that they can go and buy bread with
fee’s yes they are true in both crypto and fiat world, paypal take a cut even when you use their mass payout feature, paying out small bits is not good as the fee’s will eat up the payout, i did a ballpark estimate and for things to be reasonble i think a minimum payout of 20$ is about right
hmm… i would have shown the entire menu as it is now, but how… maybe just a video where i click each setting at 5 sec interval maybe?
and the reason i have not made it further is simple: i do it with my own money and on disability pension that is not much, and i got an old house 4 years ago that needs renovation and that comes first
but at some point i will get to where i could launch a satellite and maybe compete against storj if i wanted to