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
Copy file name to clipboardExpand all lines: Chapters/IcebergIntro/FirstConfiguration.pillar
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
!!! Configure your project nicely
2
2
@sec:Configure
3
3
Versioning code is just the first part of making sure that you and others can reload your code.
4
-
Here, we describe how to define a Baseline, a project map that you will use to define dependencies within your project and dependencies to other projects. We also show how to add a good ==.gitignore== file.
4
+
Here, we describe how to define a Baseline, a project map that you will use to define dependencies within your project and dependencies to other projects.
5
5
6
6
In the next chapter, we will show how to configure your project to get more out of the services offered within the Github ecosystem, such as Github Actions to automatically execute your tests.
Copy file name to clipboardExpand all lines: Chapters/IcebergIntro/StartedWithIceberg.pillar
+45-3Lines changed: 45 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -184,12 +184,54 @@ Now you can push your changes and versions to the remote repository using the ""
184
184
185
185
+Once you pushed you changes to the remote repository.>file://figures/S15-PushedFromReport.png|width=75|label=PushedFromReport+
186
186
187
-
!!!Configuring your project
187
+
!!!Configuring Pharo to commit in HTTPS/SSH
188
188
@sec:Configure
189
189
190
-
Versioning code is just the first part of making sure that you and other developers can reload your code. We will now describe how to define a ''Baseline'': a project map that you will use to define the dependencies within your project and its dependencies on other projects.
190
+
Versioning code is just the first part of making sure that you and other developers can reload your code. We will now describe how to configure Pharo to automatically connect to be able to publish to github. In the next section we will describe how to create a baseline (a kind of map) to reload your application.
191
+
192
+
193
+
With recent version of github, you should use a token to connect using HTTPS to be able to commit to your repository.
194
+
Now you can configure Pharo to store your token as well your github account authentification.
195
+
In addition you can configure Pharo to point to your private and public SSH key as follows:
publicKey: 'Path to your public rsa file (public key)';
215
+
privateKey: 'Path to your private rsa file (private key)'.
216
+
IceCredentialStore current
217
+
storeCredential: (IceTokenCredentials new
218
+
username: 'xxxxxJohnDoe';
219
+
token: 'magictoken here ';
220
+
yourself)
221
+
forHostname: 'github.com'.
222
+
].
223
+
}
224
+
]]]
225
+
226
+
227
+
You should place this file in the preference folder that depends on your OS.
228
+
You can find this place by using the ==Startup== menu. Note that you can configure this
229
+
for all or one specific version of Pharo.
230
+
231
+
232
+
!!! Defining a ==BaselineOf==
233
+
We describe now how to define a ''Baseline'': a project map that you will use to define the dependencies within your project and its dependencies on other projects.
191
234
192
-
!!!!Defining a ==BaselineOf==
193
235
194
236
A Baseline is a description of a project architecture. You express the dependencies between your packages and other projects so that all the dependent projects are loaded without the user having to understand them or the links between them.
0 commit comments