Dashboard feature requests ux
Tonight having multiple deployments on vercel linking back to multiple projects on convex was a bit much to sort out.
1. Generated name of convex deployment selected up on top so you don't have to go into settings to figure it out.
2. When a preview deployment is deleted, it should not leave you at a 404 with no way to get back to the dashboard.
3. When you go to enter environment keys a preview deployment should warn you that you should set it in the production env as anything you set here will get overwritten on the next push to vercel.
4. Production env settings should also link back to the project env settings.
5. Project wide settings vs specific, i didn't realize that i was getting confused and consciously noticed the difference till today (or this is newer ux), i just click around till i find what i need. Settings for each dev/production/preview should use the color scheme to increase intuitiveness.
6. Project wide settings should give you a list of the convex generated names of the deployments. 7. It should be noted that each production?/preview deployment should get its own key and should never be used twice on vercel? 8. Searching for a deployment within my projects for fast-falcon-504 etc would speed up debugging greatly.
6. Project wide settings should give you a list of the convex generated names of the deployments. 7. It should be noted that each production?/preview deployment should get its own key and should never be used twice on vercel? 8. Searching for a deployment within my projects for fast-falcon-504 etc would speed up debugging greatly.
13 Replies
Thanks for posting in <#1088161997662724167>.
Reminder: If you have a Convex Pro account, use the Convex Dashboard to file support tickets.
- Provide context: What are you trying to achieve, what is the end-user interaction, what are you seeing? (full error message, command output, etc.)
- Use search.convex.dev to search Docs, Stack, and Discord all at once.
- Additionally, you can post your questions in the Convex Community's <#1228095053885476985> channel to receive a response from AI.
- Avoid tagging staff unless specifically instructed.
Thank you!
Thanks for the feedback! We’ll add these notes to our dashboard prioritization list. Good ideas 🙂
I was also curious about the point of having more than one preview key, since generally if you use that twice on vercel you will have a database overwriting battle?
Hey @ampp , apologies I was off on vacation. Can you tell me more about what you expect with preview deployment keys? They are keys that are allowed to manage any of your preview deployments. So you don't need more than 1 key
Yeah the only reason to have more than one preview key would be to use on a different vercel project which you should avoid. I happened to reuse the one and one project would delete the others preview environment causing issues on both.
I'd also suggest that the color for local dev should be different then cloud dev.
And is it possible to add microseconds to logs when click the detailed view:convex: ?
Both of those are great ideas! Added to our list / bumped up prioritization
We just shipped:
- milliseconds in logs view
- separate color for local dev deployments
- deployment names in the deployment selector (but not in the header itself)
Thanks for improvements 🙂
I'm having a few times where i'm on a local dev and errors sometime after i shut the server down, it would be nice if that error page had a link back to the normal dashboard as refresh and back don't help.
Can you show a screenshot of what state the dashboard is in? Normally you can click the convex logo on the top left to go back to your project list
it seems to happen on any local deploy that isn't running for a while and you go back to it
I have seen this error a few times before using the local deployments, so it would be nice to just have way to go back to the dashboard as nothing else is on the page.
I think you will also get the error if you try to go to a preview deploy that is deleted
Hm interesting, is it possible this happened after you restarted your local deployment? Or the local deployment was off in this case?
The error showing up in this way is unexpected, so we're looking into why that's happening. Adding a go back link on this page isn't a bad idea though!
yeah i just tested this, i restarted my local deployment and refreshed and it did reload so the path is still good.
If i close my local deploy i get the offline page, but that seems to eventually timeout to that error. I'm switching between local deployments often right now which might be what causes that error to trigger. i suppose if i update my ports i could have two running just fine?
If i close my local deploy i get the offline page, but that seems to eventually timeout to that error. I'm switching between local deployments often right now which might be what causes that error to trigger. i suppose if i update my ports i could have two running just fine?
Yeah for now using different ports for your different projects would be a good idea 🙂 we'll prioritize investigating where these crashes are coming from