-
Notifications
You must be signed in to change notification settings - Fork 22
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
Create a minimal infrastructure template #162
Comments
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
Requirement is still active, adding comment to remove stale state |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
Requirement is still active, adding comment to remove stale state |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
Still valid and ongoing topic |
Hi @deyan-r , just to check, if I got it correctly you are currently investigating this? |
I started, but had to jump to another task, so now not working on it. |
Oks, for now we don't have anyone else assigned so in case you have any free availability and want to continue investigating, just know that it is still free |
The minimal infrastructure documentation now guides us through setting up all the application docker containers that host the infrastructure, the connectivity and application access, the dev environment, creating a project from archetypes, running and testing the project locally, setting up the GitLab CI/CD pipeline, and finally building, deploying and pushing artifacts. Shell file removed as it is no longer needed. docker-compose updated to work with nginx, nexus, gitlab, and a custom gitlab-runner. .m2/settings.xml added to the infrastructure folder. gitlab-runner Dockerfile added with openjdk, maven and nodejs on top. nginx configuration changed. Fixed #162 Signed-off-by: Ivan Zdravkov <[email protected]>
The minimal infrastructure documentation now guides us through setting up all the application docker containers that host the infrastructure, the connectivity and application access, the dev environment, creating a project from archetypes, running and testing the project locally, setting up the GitLab CI/CD pipeline, and finally building, deploying and pushing artifacts. Shell file removed as it is no longer needed. docker-compose updated to work with nginx, nexus, gitlab, and a custom gitlab-runner. .m2/settings.xml added to the infrastructure folder. gitlab-runner Dockerfile added with openjdk, maven and nodejs on top. nginx configuration changed. Fixed #162 Signed-off-by: Ivan Zdravkov <[email protected]>
The minimal infrastructure documentation now guides us through setting up all the application docker containers that host the infrastructure, the connectivity and application access, the dev environment, creating a project from archetypes, running and testing the project locally, setting up the GitLab CI/CD pipeline, and finally building, deploying and pushing artifacts. Shell file removed as it is no longer needed. docker-compose updated to work with nginx, nexus, gitlab, and a custom gitlab-runner. .m2/settings.xml added to the infrastructure folder. gitlab-runner Dockerfile added with openjdk, maven and nodejs on top. nginx configuration changed. Fixed #162 Signed-off-by: Ivan Zdravkov <[email protected]>
Description
infrastructure
folder that need to be updatedThe text was updated successfully, but these errors were encountered: