Closed waltersf closed 7 months ago
I will add that to the documentation but AFAIK the install guide doesn't make you use a dedicated IP by default. How did you deploy?
I will add that to the documentation but AFAIK the install guide doesn't make you use a dedicated IP by default. How did you deploy?
You are correct. New deployments are using shared IPv4. But old ones, migrated from Heroku, are using dedicated ones. Both cases I checked were migrated from Heroku.
Thanks!
Great. Now the issue is they removed the web terminal so the documentation is broken.
Adding draft for reference https://github.com/nightscout/nightscout.github.io/commit/1cc8ee56f145d86ea2fb5dd7ffe0d865064f6a03. Fly.io needs rework for the missing web terminal though. That's to be done with https://github.com/nightscout/nightscout.github.io/issues/201
@waltersf the "good" news is they removed the migration wizard, so this should only be for currently migrated users. https://fly.io/docs/rails/getting-started/migrate-from-heroku/
According to https://community.fly.io/t/we-are-going-to-start-charging-for-dedicated-ipv4-in-january-1st/15970, Fly will charge for dedicated IPv4.
Messages were sent in October, but I realize that many people (including me) were using a dedicated IPv4. They will charge $1.90 per month, but you can change to a shared IPv4.
Could you please add a warning about this charging? Also, if people do not want to pay for it, they can use the
flyctl
command to release the dedicated address and ask for a shared one. I changed my app using the following commands:Notice that you must change the ip
137.66.11.78
and the name example-ns accordingly.Best