gitlab

基于gollum的wiki搭建

给你一囗甜甜゛ 提交于 2020-03-05 15:12:07
基于gollum的wiki搭建 gollum是个啥 gollum是一个基于git的,解析markdown文件的wiki系统;gollum项目托管在github上: gollum ( https://github.com/gollum/gollum),项目的wiki地址:https://github.com/gollum/gollum/wiki github的wiki据说也是基于gollum搭建的;没确认; 搭建 gollum是基于ruby编写的;所以在安装gollum之前,需要先安装ruby环境; 安装依赖包 gollum依赖的包还是蛮多的,包括了ruby ,ruby-devel ,git 等等;看自己服务器的情况增加依赖包; yum -y install ruby ruby-devel rubygems make gcc libxml2-devel libxslt-devel git libicu-devel ruby版本建议在2.0+; git最好用最新版吧; 2. 安装gollum gem install gollum 中文目录/文件名问题解决 注意:建议安装 Rugged;这个是gollum所需要的git adapter ;默认的git adapter 是grit;但实际在用这个适配器的时候,会发现这个适配器不支持中文文件名、目录的问题;使用 rugged是没有问题的;

Gitlab + GKE + AutoDevops set environment variables

北城以北 提交于 2020-03-05 05:03:44
问题 I have successfully deployed an app using gitlab auto devops on GKE. How can I set environment variables for my app containers? Variables like PORT, DB_URL, 3rd party services etc ... 回答1: I am deploying to GKE from GitLab but without AutoDevops, but in k8s the env vars are defined in the deployment yaml. If you want to set them from GitLab and you want them to be different between deployments (production / dev etc.) then I recommend using Helm and passing --set to the helm install/upgrade

Gitlab + GKE + AutoDevops set environment variables

末鹿安然 提交于 2020-03-05 05:03:20
问题 I have successfully deployed an app using gitlab auto devops on GKE. How can I set environment variables for my app containers? Variables like PORT, DB_URL, 3rd party services etc ... 回答1: I am deploying to GKE from GitLab but without AutoDevops, but in k8s the env vars are defined in the deployment yaml. If you want to set them from GitLab and you want them to be different between deployments (production / dev etc.) then I recommend using Helm and passing --set to the helm install/upgrade

Gitlab + GKE + AutoDevops set environment variables

ε祈祈猫儿з 提交于 2020-03-05 05:03:16
问题 I have successfully deployed an app using gitlab auto devops on GKE. How can I set environment variables for my app containers? Variables like PORT, DB_URL, 3rd party services etc ... 回答1: I am deploying to GKE from GitLab but without AutoDevops, but in k8s the env vars are defined in the deployment yaml. If you want to set them from GitLab and you want them to be different between deployments (production / dev etc.) then I recommend using Helm and passing --set to the helm install/upgrade

Why is Create React App build failing in Gitlab CI Runner?

不羁的心 提交于 2020-03-04 23:10:53
问题 The contents of my Dockerfile: FROM node:alpine as builder WORKDIR /usr/src/app COPY package.json . RUN npm install COPY . . RUN npm run build || cat /root/.npm/_logs/*.log FROM nginx COPY --from=builder /usr/src/app/build /usr/share/nginx/html I've configured this to run with my own gitlab runner. This was working fine until the last time I attempted a build. On my own machine it builds without issue. Only when the gitlab runner attempts to build it does it fail. Only changes I made were to

Why is Create React App build failing in Gitlab CI Runner?

旧巷老猫 提交于 2020-03-04 23:10:46
问题 The contents of my Dockerfile: FROM node:alpine as builder WORKDIR /usr/src/app COPY package.json . RUN npm install COPY . . RUN npm run build || cat /root/.npm/_logs/*.log FROM nginx COPY --from=builder /usr/src/app/build /usr/share/nginx/html I've configured this to run with my own gitlab runner. This was working fine until the last time I attempted a build. On my own machine it builds without issue. Only when the gitlab runner attempts to build it does it fail. Only changes I made were to

k8s+docker部署jenkins+gitlab实现CICD项目实战

試著忘記壹切 提交于 2020-03-04 17:01:18
CICD核心概念 CICD是持续集成(continuous integration,CI),持续交付(continuous delivery,CD),持续部署(continuous Deployment,CD)的简称。 指在开发过程中自动执行一系列脚本来减低开发引入bug的概率,在新代码从开发到部署的过程中,尽量减少人工的介入。 1,持续集成 持续集成指的是,频繁地(一天多次)将代码集成到主干。 它的好处有两个: 1)快速发现错误:每完成一点更新,就集成到主干,可以快速发现错误,定位错误也比较容易。 2)防止分支大幅偏离主干:如果不是经常集成,主干又在不断更新,会导致以后集成的难度变大,甚至难以集成。 持续集成的目的: 让产品可以快速迭代同时还能保持高质量,它的核心措施是:代码集成到主干之前,必须通过自动化测试,只要有一个测试用例失败,就不能集成。 Martin Fowler说过,"持续集成并不能消除Bug,而是让它们非常容易发现和改正。" 2, 持续交付 持续交付指的是频繁的将软件的新版本交付给质量团队或用户,以供评审,如果评审通过,代码就进入生产阶段。 持续交付可以看作是持续集成的下一步,强调的是,不管怎样更新,软件是随时随地可以交付的。 3,持续部署 持续部署是持续交付的下一步,指的是代码通过评审之后,自动部署到生产环境。 持续部署的目标是:代码在任何时候都是可以部署的

国内难下载gitlab RPM包和jenkins RPM包

雨燕双飞 提交于 2020-03-04 06:22:12
1.gitlab RPM包 http://itityunwei.cn/index.php?share/file & user = 1 & sid = k4Kzqa7G 下载完直接使用yum -y install +包名 即可安装 2.jenkins RPM包 http://itityunwei.cn/index.php?share/file & user = 1 & sid = NwUcTZJH 下载完直接使用yum -y install jenkins 即可安装 3.gitlab安装比较简单,jenkins我有发布安装教程,两者一般配合使用结合ansible构建自动化运维开发,有需要其它难下载的rpm包的评论附上下载链接我会回复下载链接 这世上没有什么比坚持对成功的意义更大! 来源: CSDN 作者: 旅途丶 链接: https://blog.csdn.net/weixin_43838503/article/details/104626264

Unable to push nuGet packages to GitLab with dotnet CLI due to Unauthorized error

蹲街弑〆低调 提交于 2020-03-03 10:01:49
问题 GitLab now supports nuget public and private feed repository. I've got a public project (e.g: https://gitlab.com/sunnyatticsoftware/sasw-test-support) I create an access token for my user with api and write_repository (e.g: AAABBBCCCDDD) I create a group variable in my CI/CD: SASW_API_ACCESS_TOKEN : AAABBBCCCDDD . All normal. Then I create the multi stage CI/CD script to build, pack and publish. When attempting to publish the nuGet package with the following: dotnet nuget push **/*.nupkg -

Unable to push nuGet packages to GitLab with dotnet CLI due to Unauthorized error

*爱你&永不变心* 提交于 2020-03-03 10:01:40
问题 GitLab now supports nuget public and private feed repository. I've got a public project (e.g: https://gitlab.com/sunnyatticsoftware/sasw-test-support) I create an access token for my user with api and write_repository (e.g: AAABBBCCCDDD) I create a group variable in my CI/CD: SASW_API_ACCESS_TOKEN : AAABBBCCCDDD . All normal. Then I create the multi stage CI/CD script to build, pack and publish. When attempting to publish the nuGet package with the following: dotnet nuget push **/*.nupkg -