—region- your choice. But some rake tasks and legacy rails console code wanted to use the file instead of passing those env variables / arg
desc "Write a remote region id to this server's REGION file" task :join_region => :environment do configured_region = ApplicationRecord.region_number_from_sequence.to_i EvmApplication.set_region_file(Rails.root.join("REGION"), configured_region) end
will all of those users be logging into and using the UI? Will they be using the API instead?
Logging in and using the UI, not the API.
Definitely not. In fact, I think of the 1000 users granted access some will rarely use it. Maybe 20% will use it regularly. Management guessed 20-30% concurrent users. Maybe on day 1, but I think that's high.
Will they be running intensive tasks such as provisioning?
an you roll it out to users in stages so you can evaluate the load?
I could suggest that.
We have some information in the Deployment Planning Guide...
Thanks, that looks really helpful.