Refactor Repository (Massive update incl Documentation website)#1812
Refactor Repository (Massive update incl Documentation website)#1812gjrtimmer wants to merge 40 commits intosameersbn:masterfrom
Conversation
Fix shellcheck errors Update CI Converted documentation Update Global Config
Fixes #1637 Fixes #1636
Fixes #1768
Fixes #1794 Fixes #1793
Fixes #1791
Fixes #1792
Moved documentation generation to end of pipeline to ensure only building docs when image building succeeds.
[skip CI]
Fixes #690
Fixes #1569
Root CHANGELOG is automatically copied on documentation build
Fixes #738
Refactored branch uses a global config.yml for all configuration, including updating the version numbers in the newly generated documentation. This makes PR #1468 obsolete.
Update Backup restore documentation Fixes #1472
Add CRON=1 to command
Fixes #1695
Note: Documentation must be generated with the |
Fixes #699 Fixes #1746 Fixes #1814
Fixes #1477 Allow commandline override for GITLAB_EDITION to config.yml
Do not send documentation to docker daemon
b02c1fb to
cf312cc
Compare
I like it, and I think having an organised document site is a great idea. There is only one thing that I would change. When you click on a top level topic, I would expect it to bring up a page with all the content for the topic on it. Then in the navigation, clicking on a 2nd level topic would take you to anchors within the top level content. That way I can scan the whole top level topic without having to click very much; but if I know the subtopic I'm looking for, I can still quickly jump to it. maybe do this conditionally; because it doesn't make sense for certain large topics like Thank you. |
|
Yes, I have looked at the docs briefly and I like them too. But what delights me the most is that your PR includes some very old PRs that I've missed for a long time. (mainly LDAP) So I can only hope that this PR will pass through and serve as a "new basis" for the project. We have been using this container for quite some time and are very happy with it. |
|
@luv2code Would be a great addition, currently don't know if it is possible maybe just as simple as adding it to the _index.md files. To give you a quick summary how it works.
Check out the demo of the theme to see what an insane amount of features it has. |
Add Tagged build
|
@CrystalMethod I've updated the Circle-CI config of this new repository, and it is able to push the latest and tags to DockerHub. Also this PR now includes update of subcomponents and upgrade of Gitlab-CI to Have fun playing. P.S. *Note: This repository update also fixes the local testing. So if you clone my fork you only have to give Have fun playing @CrystalMethod I've you start playing with the new |
[skip CI]
* Upgrade Gitlab: 11.5.5 * Upgrade Components * Gitaly: 1.10.0
848aa30 to
fbe697b
Compare
* Gitaly: 1.12.0 * Update Circle-CI cache * Fixes #1816 * Fixes #1797 * Update .dockerignore
|
Hey @gjrtimmer, thank you for your Pull Request. I seems that there is a lot of work in it. But it has also a lot of breaking changes for this repository. Also there are some new features that at the moment out of scope. To clarify we should start a roadmap for the project and future changes. (This will come from my side) First of all I’ll say that I won’t replace the current master with your master branch, because of the breaking changes and that I can’t guarantee anyone from my side that this will work backwards and with no migration steps. (This is the current state of the Pull Request) . Now let’s dive inside your Components:
These versions are the latest from master and for the release. This could have breaking changes and breaks the whole releases or unintended side effects.
I’m not a really fan of an global configuration. This requires also a parser and structure for the configuration. I know you implemented it in bash but I won’t increase the readability. I think it increases only complexity, because not everyone has the use case to build different gitlab images. I think we should cover some features here in the upstream but for this I need sometime to think about it how we can handle this in a good manner with a stable process without breaking changes until Regarding the merged issues:
I hope you can understand my concerns regarding this pull request. |
* Gitlab: 11.6.2 * Golang: 1.11.4 * Update compile settings
|
I'll close this issue cause we can't integrate it directly and we have different directions. But I'm open for discussion so let's move this to an issue. |
@solidnerd @sameersbn Massive update of repository.
Cannot be auto merged, requires replacement of master branch.
Main features are:
Hugo.config.ymlwhich means that if you update the container to a new version of gitlab all the version numbers of the documentation will change with it too.config.templatefile more variables can be added to make the documentation even more automatic. When you runmake docsit will generate theconfig.ymlfor the documentation and generate it indocs/publicsee the .gitlab-ci.ymlpagesjob. We still need to add a job / script to circleci which will publish the documentation to the gh-pages branch. This is possible found some examples on github on how to do this.config.ymlto reflect the config of thesameersnm/docker-gitlabrepository.config.yml(Global) and Circle-CI config has to be changed. Also two variables has to be added to Circle-CI build environmentRepository Refactor
exec_as_gitfrom function to scriptexec_as_git=> /sbin because of symlinks / layer compressiondocker_layer_caching: trueinstead of manually saving layerstagDEBUGDEBUG=true make docker|| exit 1to non build commandsMakefiletargetlogs