I have 2 hp g800 sff i5 4th gen @3.4ghz a qnap nas for storage, 2 rpi 4 and an odroid m1 as a docker swarm for all my services a modem a router and my switch and I’m having around 100 watt usage for the whole cluster.
So i think an SFF pc will do the job fine and meet your power and computing requirements.
Usually on the remote i use lunarvim(neovim but with some default settings and plugins).
Other than that I usually have everything as a git repo, so i edit on my local/remote ide(pycharm, vscode or vscode server). I edit the files push them to the repo and then i just pull the files on my host.
I know this adds some steps to edit a simple file, but the version control etc can be a massive advantage depending on what you do.
You can host on almost any PC that supports the OS for your application. How much of it you can host really depends on the specs of the machine.
If you run docker i like homepage, since it has auto discovery based on service/container labels. So if I deploy a new service i just add some labels to the compose file and boom it’s on homepage.
Yes indeed, i think that’s the phrasing that does it best. For example if there are some cheaper psp’s around for 1 specific payment method but you’d like to offer more. You could proxy different psp’s for different payments all into 1 API and offer that as a service perhaps. I don’t have any concrete ideas for that but suggested it as a point to get you started somewhere and if you have a working business model you could use the profit to start building everything in-house to work towards becoming your own PSP.
Working for a bank i know there many aspects that come with being a PSP. Think about fraud detection, KYC, technical as well as well as financial audits. When you work with card processing you need to abide with Mastercard policies for example(which is a few hundred page rulebook). Same goes for various other payment methods with each their own rules, fraud rate tresholds. Then there are security aspects, risk apetite, chargeback policies as well as possible liquidity requirements.
My 2 cents is that this is a bit much for a side project. But I don’t know how much time and resources you have on your hands. As there is a reason people usually use larger payment providers and smaller payment providers usually attract a certain type of customers(p*rn, gambling, “research” drugs etc)
If you want to do this solely for your own company, perhaps the way to go is to tie a few existing psp API’s together. But in Europe since the wirecard scandal regulators have become more strict on PSP’s.
Hope this info helps you a bit and doesn’t encourage you, if you are really set on this you’ll find a way. But handling other people their money and payment infrastructure comes with great responsibility.
Same here, also have some autoscaling mechanisms set up in docker swarm to scale certain services in case the load is high
I use qbittorent in docker as backend and run flood for frontend as a separate container works a charm.
Looks great, unfortunately i’m running on docker swarm. Hope it’ll support that somewhere in the future so i can use it. As i’m a great fan of uptime kuma and use it for work and private.