https://lnvps.com/

Reply to this note

Please Login to reply.

Discussion

Very interesting! Thanks for sending this over!

I’m trying it now, but having some issues

Who built it so I can follow them?

How do you manage secrets?

I previously relied on environmental variables, but I'm learning there are limitations with that practice

a secrets.json/yaml/file format here

and listed in .gitignore

problem solved

anything else is unnecessarily complicated unless you have more than 2 servers and frequently changing secrets

i use an allow list pattern on my gitignores, this way only stuff i mean to be in there is caught, everything else gets ignored

https://github.com/mleku/realy/blob/dev/.gitignore

been using this since i had a colleague include a node_modules in our fiat mine project a year ago

this list will pretty much keep anything useful, just don't use .txt for secret files lol

Wouldn’t the owner of the hardware have root access to the secrets.json file?

I may be misunderstanding

How is that better than environmental variables?

More flexibility

Environment variables. Specify them in the systemd service file. What is the problem with them?

I don't have many secrets to be honest.

Wouldn’t the owner of the hardware have root access to them?

Definitely. If you want absolute secrecy you have to run your own (or trust Intel SGX but that's too complicated).

You can also precompile secrets inside the binary you deploy, the owner of the hardware still has access but it makes their lives harder. Or you can load the secrets from somewhere else on startup and keep them in memory, again they can still access but it's harder.

This is actually so epic, thanks again for sending this over!

nostr:nprofile1qqsx8lnrrrw9skpulctgzruxm5y7rzlaw64tcf9qpqww9pt0xvzsfmgrefsyl great job on this! I’m enjoying using it so far

Is it open source?

Also, would you consider doing payments per hour like traditional services instead of a single monthly payment?

Maybe there’s a better way, but in mind I see it as the user pays a deposit to a wallet for the service and can extend as needed (which you have currently), but the amount paid is deducted every hour so if the server is down or suspended then the payment is paused

I think I’d be more inclined to deposit more money upfront knowing it’s depleted based on usage (instead of monthly)

Does that make sense?

Another thought:

This would be crazy as a DVM

Minimal inputs: server OS, ssh key encrypted

DVM replies with lightning invoice

User pays invoice

DVM replies with encrypted IP, DNS, etc

Then AI agents can spin up servers without API keys 🤯

My impression is that the traditional way is charging per month, not per hour.

nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmwdaehgu3wdau8gu3wv3jhvtcqyr7dsxz9gqp2d3r6nqpe8uz5ntrwv2wj34tgsy2tkcxcxx6urqe2wkx04za by nostr:nprofile1qyf8wumn8ghj76r0d3jjua3sdshxjme0qy88wumn8ghj7mn0wvhxcmmv9uqzqcl7vvvdckzc8nlpdqg0smwsncvtl4m240py5qypec59dues2p8d28x895 is my new favorite hosting provider

- no KYC, login with nostr (NIP07)

- pay with satoshis I earned from nostr, no credit card required

- notifications over DM

- customize CPU, RAM and SSD independently

- saved $50 moving from Heroku and got an extra 40GB SSD with it

- dark mode

Imagine if this had a DVM for AI Agents to deploy servers 🤯

No KYC, No API Key, No Credit Card remote servers are here

If this gets combined with Zero Knowledge Proofs/Compute where the service provider is completely blind to what the server is running (learned about this from nostr:nprofile1qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcpzemhxue69uhks6tnwshxummnw3ezumrpdejz7qpq2rv5lskctqxxs2c8rf2zlzc7xx3qpvzs3w4etgemauy9thegr43sugh36r ) then we'll have something really interesting

nostr:nevent1qvzqqqqqqypzqwlsccluhy6xxsr6l9a9uhhxf75g85g8a709tprjcn4e42h053vaqqsqqqrarrrddh99k2y8n0trjljcrcrjre2jdulqqwsysah4qa05eug38n4hq