You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running your own atomic-server is quite simple, but the real problem is making it accessible on the internet. I want consumers to be able to do this, without doing the hard work. What you currently need to do:
Get a domain name
Use DDNS (if you don't have a static IP, as most individuals)
Set up port-forwarding with your router
It's all just too much!
What could really work well, is use some tunnelling service like ngrok, tunnelto.dev (open source, rust) or cloudflare tunnels.
The text was updated successfully, but these errors were encountered:
Open a tunnel pktriot http 8080, note the tunnel domain
install / download atomic-server
Adjust the .env (or copy template.env): set HTTPS to false, HTTP_PORT to 8080, and the domain to the newly created tunnel domain
run atomic-server
Visit your domain
But there still is a problem: the returned @id does not match, since the server is thinking it's serving HTTP instead of HTTPS. Maybe add a RETURN_HTTPS flag?
Running your own
atomic-server
is quite simple, but the real problem is making it accessible on the internet. I want consumers to be able to do this, without doing the hard work. What you currently need to do:It's all just too much!
What could really work well, is use some tunnelling service like
ngrok
,tunnelto.dev
(open source, rust) or cloudflare tunnels.The text was updated successfully, but these errors were encountered: