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
Postgres: At standard listenport 5432 for your jdbc-connection-string
82
87
stream-passthrough to postgres-container.
83
88
```
@@ -99,6 +104,9 @@ See Readme in folder security-paranoia if you want to have some hints how to con
99
104
|Postgres|postgres|admin|
100
105
101
106
## The Tools
107
+
There are some configurations you have to do after setup.
108
+
*Remember:* At every time use your real hostname and NOT localhost (locahost inside a container is the container itself).
109
+
For example: If yuo configure a GitLab-Connection in Jenkins, you will reach Gitlab at http://<you host>/gitlab and not http://localhost/gitlab
102
110
### Jenkins
103
111
* MAVEN_HOME is /opt/maven
104
112
* JAVA_HOME is /usr/lib/jvm/java-8-openjdk-amd64
@@ -109,10 +117,10 @@ See Readme in folder security-paranoia if you want to have some hints how to con
109
117
* the docker-registry from GitLab is at port 5555 (and secured with an openssl certificate ..thats part of
110
118
setupEnvironment.sh), just create a project in gitlab and click at the registry tab to show
111
119
how to login to the project registry and how to tag your images and upload them.
112
-
* ssh cloning and pushing is at port 2222
120
+
* ssh cloning and pushing is at port 2222 (ssh://git@myHOST:2222/scott/foo.git remeber to upload your public key before, should be ~/.ssh/id_rsa.pub )
113
121
114
122
#### gitlab-runner
115
-
The runner is a gitlab-multirunner image with a docker-runner (concurrent=1) , based on [gitlab/gitlab-runner][2] at every startup any runner is removed and only ONE new runner ist registrated to avoid multiple runners (the pipeline-history maybe lost.) docker-in-docker works :-)
123
+
The runner is a gitlab-multirunner image with a docker-runner (concurrent=1) , based on [gitlab/gitlab-runner][2] at every startup any runner is removed and only ONE new runner is registrated to avoid multiple runners (the pipeline-history maybe lost.) docker-in-docker works :-)
116
124
117
125
It takes a long time until gitlab is ready to accept a runner registration, if it fails, increase the REGISTER_TRYS in docker-compse.yml
118
126
@@ -136,34 +144,35 @@ _tl;dr_
136
144
* create client "product-app" as openid-connect client with Valid Redirect URI's http://<your host>:8081/*
137
145
* create role "user"
138
146
* create user "testuser" and map the role "user" to testuser (tab Role Mappings)
139
-
140
-
### Nexus
141
-
Some ToDo for me described here
142
-
[Unsecure docker-registry in Nexus][1]
143
-
use GitLab as a secured registry
144
-
..
145
-
And _yes_ docker-plugin in jenkins works (docker in docker, usefull but not recommended)
147
+
148
+
146
149
### Postgres
147
-
You can use any tool to connect to the database at locahost:5432 this is a pass through to the container so any
150
+
You can use any tool to connect to the database at localhost:5432 this is a pass through to the container so any
148
151
JDBC-Connection should work
149
152
153
+
### The Docker-Registries
154
+
* NEXUS-Docker-Registry ist NOT configured .. needs a pass trough and some more configs, see [Unsecure docker-registry in Nexus][1] feel free to provide a push-request
155
+
* GitLab docker-registry is at port 5555 you have to use your GitLab Credentials from the corresponding git-respository
156
+
* standard Docker-Registry v2 ist at standard port 5000 with no credentials, so eays-to-use
157
+
158
+
150
159
## Troubleshooting
151
160
##### check Hostname and IP
152
161
In most cases a wrong HOSTNAME:HOSTIP causes trouble, to check this try the following.
0 commit comments