Split ShareX endpoint out and have settings stored server-side
Closed this issue · 1 comments
A lot of people I have given micro access have been confused by the options on the dashboard where you select a domain, they think it persists automatically its just to customise the configuration. There are two ways forward, either split the configuration generator into a separate page that is clearly marked, or the harder but a lot nicer route of storing those domains server-side so you download the config once and customise it through the dashboard.
I'm not sure how this should work. Maybe we could rewrite authentication so each config sends a X-Micro-Config header with a unique key that is saved in our database, and that key corresponds to things like the domain(s) to use for uploads unless X-Micro-Host is present. Either way, I think we should continue to support X-Micro-Host as a header on all endpoints.
I think an easier better option is to just improve the UI so its not as confusing. Server-side configs would be nice but would be a lot of work for such a minor feature, and overwriting ShareX configs to update them is pretty simple.