fixed naming issues

This commit is contained in:
Sebastian Wendel 2022-11-22 23:40:49 +01:00
parent d78475fa8d
commit 775bb1ec5e
No known key found for this signature in database
GPG key ID: 1422B7DF78144640
5 changed files with 13 additions and 7 deletions

View file

@ -8,6 +8,10 @@ indent_style = space
insert_final_newline = true insert_final_newline = true
max_line_length = 120 max_line_length = 120
[*.{nix}]
indent_size = 2
indent_style = space
[*.{yml,yaml}] [*.{yml,yaml}]
indent_size = 2 indent_size = 2
indent_style = space indent_style = space

View file

@ -17,13 +17,13 @@ First of all, thank you for contributing to FCOS! The goal of this document is t
## 🚧 How to Contribute ## 🚧 How to Contribute
1. Make sure that the contribution you want to make is explained or detailed in a Gitlab issue! Find an [existing issue](https://gitlab.fabcity.hamburg/software/fabcity-os-core-chart/-/issues) or [open a new one](https://gitlab.fabcity.hamburg/software/fabcity-os-core-chart/-/issues/new). 1. Make sure that the contribution you want to make is explained or detailed in a Gitlab issue! Find an [existing issue](https://gitlab.fabcity.hamburg/software/fcoscore-chart/-/issues) or [open a new one](https://gitlab.fabcity.hamburg/software/fcoscore-chart/-/issues/new).
2. Once done, [fork the FCOS Core Chart repository](https://docs.gitlab.com/ee/user/project/repository/forking_workflow.html) in your Gitlab account. Ask a maintainer if you want your issue to be checked before making a PR. 2. Once done, [fork the FCOS Core Chart repository](https://docs.gitlab.com/ee/user/project/repository/forking_workflow.html) in your Gitlab account. Ask a maintainer if you want your issue to be checked before making a PR.
3. [Create a new Git branch](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-new-branch). 3. [Create a new Git branch](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-new-branch).
4. Review the [Development Workflow](#development-workflow) section that describes the steps to maintain the repository. 4. Review the [Development Workflow](#development-workflow) section that describes the steps to maintain the repository.
5. Make the changes on your branch. 5. Make the changes on your branch.
6. [Submit the branch as a PR](https://docs.gitlab.com/ee/user/project/merge_requests/index.html) pointing to the `main` branch of the main fabcity-os-core-chart repository. A maintainer should comment and/or review your Pull Request within a few days. Although depending on the circumstances, it may take longer.<br> 6. [Submit the branch as a PR](https://docs.gitlab.com/ee/user/project/merge_requests/index.html) pointing to the `main` branch of the main fcoscore-chart repository. A maintainer should comment and/or review your Pull Request within a few days. Although depending on the circumstances, it may take longer.<br>
We do not enforce a naming convention for the PRs, but **please use something descriptive of your changes**, having in mind that the title of your PR will be automatically added to the next [release changelog](https://gitlab.fabcity.hamburg/software/fabcity-os-core-chart/releases/). We do not enforce a naming convention for the PRs, but **please use something descriptive of your changes**, having in mind that the title of your PR will be automatically added to the next [release changelog](https://gitlab.fabcity.hamburg/software/fcoscore-chart/releases/).
## 🎮 Setup a development environment ## 🎮 Setup a development environment
@ -41,7 +41,7 @@ In order to use the different tools on this repository, you will first need to:
## 👩‍💻 Development Workflow ## 👩‍💻 Development Workflow
1. 🔀 [Fork the Project](https://gitlab.fabcity.hamburg/software/fabcity-os-core-chart/-/forks/new) 1. 🔀 [Fork the Project](https://gitlab.fabcity.hamburg/software/fcoscore-chart/-/forks/new)
2. Check out `make help` 2. Check out `make help`
3. Create your feature branch `git checkout -b feature/branch` 3. Create your feature branch `git checkout -b feature/branch`
4. Start the development Cluster `make up` 4. Start the development Cluster `make up`

View file

@ -4,7 +4,7 @@ description: Fab City OS Core Kubernetes Helm Chart
version: 0.1.0 version: 0.1.0
type: application type: application
appVersion: latest appVersion: latest
home: https://gitlab.fabcity.hamburg/software/fabcity-os-core-chart home: https://gitlab.fabcity.hamburg/software/fcoscore-chart
icon: https://www.fabcity.hamburg/wp-content/uploads/2021/04/cropped-Fab_City_Hamburg@4x-192x192.png icon: https://www.fabcity.hamburg/wp-content/uploads/2021/04/cropped-Fab_City_Hamburg@4x-192x192.png
sources: sources:
- https://github.com/dyne/zenflows - https://github.com/dyne/zenflows

View file

@ -107,7 +107,7 @@ package: ## Package the helm chart.
@helm package . --destination charts @helm package . --destination charts
push: ## Publish the helm chart. push: ## Publish the helm chart.
@helm cm-push charts/fcoscore-*.tgz fabcity-os-core-chart @helm cm-push charts/fcoscore-*.tgz fcoscore-chart
%: %:
@true @true

View file

@ -11,7 +11,7 @@
</h4> </h4>
<p align="center"> <p align="center">
<a href="https://gitlab.fabcity.hamburg/software/fabcity-os-core-chart/LICENSE"><img src="https://img.shields.io/badge/license-AGPL-informational" alt="License"></a> <a href="https://gitlab.fabcity.hamburg/software/fcoscore-chart/LICENSE"><img src="https://img.shields.io/badge/license-AGPL-informational" alt="License"></a>
<a href="https://matrix.to/#/#fcos:fabcity.hamburg"><img src="https://img.shields.io/badge/Matrix-FCOS-blue.svg?logo=element" alt="Matrix"></a> <a href="https://matrix.to/#/#fcos:fabcity.hamburg"><img src="https://img.shields.io/badge/Matrix-FCOS-blue.svg?logo=element" alt="Matrix"></a>
</p> </p>
@ -53,6 +53,8 @@ Helm CLI is a Command Line Interface which will automate chart management and in
#### From the source files #### From the source files
```sh ```sh
git clone https://gitlab.fabcity.hamburg/software/fcoscore-chart.git
cd fcoscore-chart
helm install fcoscore . helm install fcoscore .
``` ```