Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Color coding to distinguish between test, live and staging servers #3979

Closed
cyberduck opened this issue Dec 5, 2009 · 3 comments
Closed
Assignees

Comments

@cyberduck
Copy link
Collaborator

56f3c62 created the issue

I read with interest a description of a Drupal module that inserted a colour coded strip to remind the user whether he was on a live, staging or test install, and I wondered if perhaps the same could be done for bookmarked servers on Cyberduck (perhaps a horizontal strip would suit better here).

The screenshot of the Drupal module is here:
http://drupal.org/project/environment_indicator

More than once, i have inadvertently moved files to live instead of test, so this would be a real boon. You could configure this option through radio buttons in the 'New Bookmark/Edit bookmark' page.

@cyberduck
Copy link
Collaborator Author

56f3c62 commented

By 'configure ths option', i meant designate which filesystems are considered as 'live' 'test' and so forth. Apologies for the loose wording.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Jan 16, 2010

@dkocher commented

Close as duplicate in favor of #12233. Folders for bookmarks would let you organize these by deployment.

@cyberduck
Copy link
Collaborator Author

cyberduck commented May 4, 2021

42ce461 commented

Can you clarify in what way this report would duplicate #12233? #12233 makes no mention of colors at all.

This ticket is probably a duplicate of #3733.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants