You can either select to overwrite your local settings with the setting from the JetBrains account or vice versa.
#Community syn how to
When you enable it on another machine, you'll be prompted how to manage settings conflict. If you click it, you'll be able to enable the settings synchronization: Then click Activate.īefore you link your IDE to JetBrains account, your status bar in the lower-right part of the window should look something like this:Īfter your JetBrains account is linked, you should see a new Gears icon which is used to manage Settings synchronization:
#Community syn license
Then you just need to select Activate new License with JetBrains Account and enter your credentials. Once you have your JetBrains account, you'll need to Log in to IDEA using it. If you don't have one, you can create it here. The first thing you need to do is to make sure you have a JetBrains account. On top of that, unlike Settings Repositories, it allows you to also synchronize your installed plugins. It is much more convenient because you don't have to create a Git Repo to store the settings and provide its address to your IDE. Under the hood, it actually uses a variation of Settings Repository mechanism, but you are shielded from it. It utilizes your JetBrains account to synchronize the data. The second way of settings synchronization was available for some time as a standalone optional IDE plugin (which required an invitation to use), but now is integrated and enabled by default since 2017.3. Note that you can also disable automatic synchronization and use just sync on demand by VCS → Sync Settings. Underneath you can configure additional secondary repositories: Here you can see your primary repository, which you set up earlier. You can only fetch settings from them but they are not affected by your local settings changes. The rest of the repositories are secondary and are read-only. The synchronization works both ways - from the server to the client and the opposite way. In such case, IDEA will consider one of the repositories primary. After all, every user has different preferences. But then, of course, you want some of your setting to be personal and just for you. What is it good for? Well, maybe there are some settings you want to share with your teammates to ensure consistency on your project. However, IDEA offers a neat feature - you can actually define multiple Settings Repositories. When you are configuring Settings Repository this way, you can always check whether your local settings should overwrite those on the server, vice versa or if they should be merged.Īnd that's it, you're done. If you are just starting an empty repo will do. So you can track and rollback the changes if necessary or even allow other people to create Pull Requests with some tweaks to your settings.Īnd enter the URL of your git repo. That means your settings are backed up and under version control. What's nice is that it is a plain old Git repo. In case one instance makes changes in the settings it can be propagated back to the repository. Each IDEA instance then connects to this repository to fetch the settings. The way it works is that it uses an external Git repository to share the settings. The first way to synchronize settings is using Settings Repositories. Not to mention that it makes onboarding a new developer and making them stick to conventions much easier. And having same key settings of your IDE will help a lot. It is important to stick to some guidelines and standards for your project. Setting up a new IDE is much easier this way and everything is also backed up online in the process.Īnd of course, you usually do not work alone but in a team. Rather than doing manually, it is much better to use automated synchronization. It can be quite a hassle to keep settings the same on all of them. The importance of synchronizationĪs a developer, you usually use multiple computers each with its own instance of your favorite IDE. Did you know IDEA offers two ways of synchronization of you settings among multiple instances of your IDE? You can use it when working on multiple computers or to share unified settings in your team.
0 kommentar(er)
