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

Sync configuration between browsers #191

Open
GentlemanHal opened this issue Aug 27, 2017 · 1 comment
Open

Sync configuration between browsers #191

GentlemanHal opened this issue Aug 27, 2017 · 1 comment
Labels
complicated Changes that are difficult or time consuming to implement help wanted Changes the team requires more information or help to resolve new feature A new feature

Comments

@GentlemanHal
Copy link
Member

It would be good to be able to sync configuration between different browsers.

This would make it super simple to run Nevergreen on multiple browsers, such as different TVs around the office or on local developers machines.

Backup and restoring from a Gist (#119) allows users to do this, but copying the Gist ID is a little tedious as they can be up to 32 characters.

@GentlemanHal GentlemanHal added the new feature A new feature label Aug 27, 2017
@GentlemanHal GentlemanHal added the help wanted Changes the team requires more information or help to resolve label Jul 1, 2018
@GentlemanHal GentlemanHal added the complicated Changes that are difficult or time consuming to implement label Aug 29, 2018
@GentlemanHal GentlemanHal pinned this issue Feb 25, 2019
@GentlemanHal GentlemanHal added this to the v7.0.0 milestone Aug 18, 2019
@GentlemanHal
Copy link
Member Author

GentlemanHal commented Aug 18, 2019

Playing #271 would keep configuration up to date remotely, so it might be good enough for this feature to just periodically pull the configuration down from the remote location, e.g. nightly.

This would require the user to make one copy of Nevergreen the "primary" that all updates happened on to avoid trashing configuration, but that is probably acceptable 🤔

@GentlemanHal GentlemanHal added this to To do in v7.0.0 via automation Sep 29, 2020
@GentlemanHal GentlemanHal removed this from To do in v7.0.0 Nov 7, 2020
@GentlemanHal GentlemanHal removed this from the Backup improvements milestone Nov 22, 2022
@GentlemanHal GentlemanHal unpinned this issue Jan 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
complicated Changes that are difficult or time consuming to implement help wanted Changes the team requires more information or help to resolve new feature A new feature
Projects
None yet
Development

No branches or pull requests

1 participant