You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-[Using StackMuncher app on multiple machines](#using-stackmuncher-app-on-multiple-machines)
20
20
-[Limitations](#limitations)
21
21
-[Troubleshooting](#troubleshooting)
22
22
-[Bug reports and contributions](#bug-reports-and-contributions)
@@ -122,6 +122,14 @@ Git will invoke the app every time you make a commit to a repo with the post-com
122
122
123
123
You can skip adding the Git hook and run `stackmuncher` from the root of any of your projects. No additional params are required.
124
124
125
+
## Using StackMuncher app on multiple machines
126
+
127
+
1. Clone this repo onto a 2nd machine
128
+
2. Run `cargo run -- view_config` to bootstrap the app
129
+
3. Copy-paste the contents of `.stm_config/config.json` and `.stm_config/key.txt` from the 1st to the 2nd machine
130
+
131
+
The 2nd machine will be connected to the same Developer Profile as the first one for as long as they share the same _key.txt_ file. If you loose the key file the app will generate a new one and create a new Developer Profile. Contact us on [email protected] to merge the old profile into the new one.
132
+
125
133
## Detailed usage instructions
126
134
127
135
Running `stackmuncher` without any additional params generates a report forthe projectin the current working directory and updates your developer profile.
@@ -181,14 +189,6 @@ Example:
181
189
#### Additional commands
182
190
*`view_config`: displays the contents of the config file and its location. The config file can be edited manually or copied to another machine together with the key file to connect to the same Developer Profile.
183
191
184
-
## Using StackMuncher app on multiple machines
185
-
186
-
1. Clone this repo onto a 2nd machine
187
-
2. Run `cargo run -- view_config` to bootstrap the app
188
-
3. Copy-paste the contents of `.stm_config/config.json` and `.stm_config/key.txt` from the 1st to the 2nd machine
189
-
190
-
The 2nd machine will be connected to the same Developer Profile as the first one for as long as they share the same _key.txt_ file. If you loose the key file the app will generate a new one and create a new Developer Profile. Contact us on [email protected] to merge the old profile into the new one.
191
-
192
192
## Limitations
193
193
194
194
_The current version of the app is at alpha-stage and should be used for testing purposes only._
0 commit comments