I got this structure:
├── root
│ ├── app A
│ ├── app B
│ ├── app C
The root folder is initialized as git folder so I can easily push the whole project. Now I am wondering where to place the kubernetes yaml files.
My idea would be something like this:
├── root
│ ├── app A
│ ├── app B
│ ├── app C
│ ├── kubernetes.conf.d
├── appA.yaml
Question: is there is a common location to place the config files for kubernetes?
This is completely subjective and you should do whatever works for you. My preference, however, is:
# Each application has
- opt
- kubernetes
- deployment.yaml
- helm
- values.yaml
I like using ./opt, as it is familiar to most with Unix experience.
Related
I am fairly competent in using GitHub actions to build a variety of languages, orchestrate deployments, and I've even done cross-repository actions using web-hooks, so I'd say that I'm pretty familiar with working with them.
I often find myself doing a lot of scratch projects to test out an API or making a demo, and these don't usually merit their own repositories, but I'd like to save them for posterity, rather than just making Gists out of them, Gists being largely impossible to search. I'd like to create a scratch repository, with folders per language, like:
.
└── scratch
├── go
│ ├── dancing
│ │ ├── LICENSE-APACHE
│ │ ├── LICENSE-MIT
│ │ ├── main.go
│ │ └── README.md
│ ├── gogettur
│ │ ├── LICENSE-APACHE
│ │ ├── LICENSE-MIT
│ │ ├── main.go
│ │ └── README.md
│ └── streeper
│ ├── LICENSE-APACHE
│ ├── LICENSE-MIT
│ ├── main.go
│ └── README.md
├── node
│ └── javawhat
│ ├── index.js
│ ├── LICENSE-APACHE
│ ├── LICENSE-MIT
│ └── README.md
└── rust
├── logvalanche
│ ├── Cargo.toml
│ ├── LICENSE-APACHE
│ ├── LICENSE-MIT
│ ├── README.md
│ └── src
├── streamini
│ ├── Cargo.toml
│ ├── LICENSE-APACHE
│ ├── LICENSE-MIT
│ ├── README.md
│ └── src
└── zcini
├── Cargo.toml
├── LICENSE-APACHE
├── LICENSE-MIT
├── README.md
└── src
I'd like to generalize GitHub actions per language, for Go, use go test ./... and go build, for Rust cargo test and cargo build, etc.
I know that what I could do is have a workflow for each created project, but this would be tedious, I'd end up copying and pasting most of the time, and every build would run on every change in the entire repository, and I don't want to be building node/javawhat if only rust/zcini has changed.
Therefore I have a few questions:
Is it possible to have a workflow only run when certain files have changed, rather than running everything every single time?
Is there a way to generalize my workflows so that every dir in rust/ uses the same generic workflow, or will I need one workflow per project in the repository?
Using kubectl apply -k, you can overlay Resource configs (that you have already defined). Can you create resources as well?
In my specific case I want to create a local Volume for the development environment. I do not have this Resource in the base folder though.
My folder structure is like this:
~/someApp
├── base
│ ├── deployment.yaml
│ ├── kustomization.yaml
│ └── service.yaml
└── overlays
├── development
│ ├── cpu_count.yaml
│ ├── kustomization.yaml
│ ├── replica_count.yaml
│ └── volume.yaml <--- *Is this possible*?
└── production
├── cpu_count.yaml
├── kustomization.yaml
└── replica_count.yaml
In your overlays/development/kustomization.yaml you can add:
resources:
- volume.yaml
I'm building a blog using jekyll and hosting it on github with gh-pages. The root of my project can be see seen below:
├── LICENSE
├── README.md
├── _config.yml
├── _img
│ ├── 2016-09-09\ 14.48.20.png
│ └── 2016-09-09\ 15.25.09.png
.
.
.
├── _posts
│ ├── 2016-09-08-seven-weeks-before-applying-to-devops-job.markdown
│ └── 2016-09-09-an-hour-with-ansible.md
.
.
.
├── _site
│ ├── 2016
│ │ └── 09
│ │ ├── 08
│ │ │ └── seven-weeks-before-applying-to-devops-job.html
│ │ └── 09
│ │ └── an-hour-with-ansible.html
│ ├── LICENSE
│ ├── README.md
│ ├── about
│ │ └── index.html
│ ├── css
│ │ └── main.css
│ ├── feed.xml
│ └── index.html
├── about.md
├── css
│ └── main.scss
├── feed.xml
└── index.html
The documentation gives the following example:
Because of Jekyll’s flexibility, there are many solutions to how to do this. One common solution is to create a folder in the root of the project directory called something like assets or downloads, into which any images, downloads or other resources are placed. Then, from within any post, they can be linked to using the site’s root as the path for the asset to include. Again, this will depend on the way your site’s (sub)domain and path are configured, but here are some examples (in Markdown) of how you could do this using the site.url variable in a post.
Including an image asset in a post:
... which is shown in the screenshot below:
I've tried several different ways but non are working once I push gh-pages up:
I've also tried "keeping" the _img directory by putting the following in my _config.yaml
# Build settings
markdown: kramdown
keep_files: ["_img"]
But this also is not working. So how do I include images in a jeykll project hosted on github?
Thanks for your help :)
Every folder beginning with an underscore won't be copied to the build destination. The most common way is to store images is to add them to a assets/img folder.
If you want to use _img you have to add to your _config.yml:
include:
- "_img"
Create a folder for your images, you can name it according to your wish (mine is "images")
Find the image address of that image that you want to include in your post
(You can do that by going to your folder image and right click on your image, then copy image address)
Now you use that address in your post without any problem.
I have downloaded a rpm in my ansible-playbook:
(djangoenv)~/P/c/apache-installer ❯❯❯ tree .
.
├── defaults
│ └── main.yml
├── files
│ ├── apache2latest.tar
│ ├── httpd_final.conf
│ ├── httpd_temp.conf
│ └── sshpass-1.05-9.1.i686.rpm
├── handlers
│ └── main.yml
├── hosts
├── meta
│ └── main.yml
├── README.md
├── tasks
│ └── main.yml
├── templates
├── tests
│ ├── inventory
│ └── test.yml
└── vars
└── main.yml
My question is why can't I just install it using:
- yum: name=files/sshpass-1.05-9.1.i686.rpm
? It complains that files/sshpass-1.05-9.1.i686.rpm is not found in the system. Now I am doing it in two steps:
- copy: src=files/sshpass-1.05-9.1.i686.rpm dest=/tmp/sshpass-1.05-9.1.i686.rpm force=no
- yum: name=/tmp/sshpass-1.05-9.1.i686.rpm state=present
No, there is no simple way around coping the package to the remote host before installing. Ansible yum module expects a local file when you define a file in the name parameter.
IMHO it is not a good idea to keep packages inside the Ansible code base. Because they are binary and not exactly part of the actual Ansible code. It would be cleaner to setup a private repository and store those files there. That is the only way around coping a package in this situation I'm aware of.
In order to reduce the superfluous codes，I want to share a base template among many
subapps,
Example dir tree
├── admin
│ ├── __init__.py
│ ├── templates
│ │ └── admin.html
│ └── view.py
├── base_templates
│ └── base.html
└── view.py
Now , I am using dir package styel as a sub app(I dunno whether it's a right way to do this). Above,
I am going to use base.html template in admin app, so
foo.py
render = web.template.render(...) # the render
class Foo:
def GET:
return render.admin()
any way to resolve my trouble ? thx
You can do this using a site layout template.