Python で jsonの変数を持たせたいことがあり、読み込む上でのメモ
import json
list = [{"name":"Worker","no":"123"}, {"name":"User","no":"456"}, {"name":"Organization","no":"789"}, {"name": "Position","no":"123"}, {"name": "PositionTranslation","no":"123"}]
for d in list:
print(d.get('name'))
print(d.get('no'))
print("-----")
list の中に json の配列を格納
loop の中で .get(key名)を行うことで value を取り出すことができる
結果
Worker
123
-----
User
456
-----
Organization
789
-----
Position
123
-----
PositionTranslation
123
-----
一時領域を作ることができないほどdiskが圧迫している。
空き容量を確保する
docker rm -f $(docker ps -a -q)
docker builder prune -a -f
上記両方を行うことで容量を確保できることが多い。
手元のテキストファイルを単純に zipファイル化するためのメモ
以下のディレクトリ構成とする
% tree a
a
└── 1.csv
a というディレクトリの配下に 1.csv というファイルが存在したとする
python3 でzip 化
import zipfile
with zipfile.ZipFile('1.csv.zip', "w", compression=zipfile.ZIP_DEFLATED) as zf:
zf.write('a/1.csv',arcname='1.csv')
a/1.csv を圧縮し、a/1.csv.zip というファイルを生成する。
a/1.csv.zip を解凍すると、1.csv という名前のファイルが直下に作成される。
python zip.py
直下に
1.csv.zip
が作られる。
解凍する
% unzip 1.csv.zip
Archive: 1.csv.zip
inflating: 1.csv
無事解凍できたことを確認
% cat 1.csv
NO,CODE
1,987
Most of the tasks in aws can be operated with aws commands. The only command I couldn’t find in the official documentation was “create folder,” which should be on the screen.
In fact, the concept of folders does not exist in S3. https://docs.aws.amazon.com/ja_jp/AmazonS3/latest/dev/UsingMetadata.html
The data model of Amazon S3 is a flat structure. Buckets are created and objects are stored in those buckets. There is no hierarchy of sub-buckets or sub-folders. However, a logical hierarchy can be implied by using key name prefixes and delimiters, such as those used in the Amazon S3 console.
So, for one bucket, there are no folders in it, and it is an image of a large number of files.
I don’t have a directory, but I’ll just dump it in directly!
aws s3 cp sample.txt s3://test/sample-folder/
This will create a sample-folder in the test bucket. Copy the sample.txt file into it. Reference: Breaking the illusion of “folder” in Amazon S3 and revealing its reality https://dev.classmethod.jp/cloud/aws/amazon-s3-folders/
If multiple environments are registered in the .aws directory, it is possible to specify the profile to be loaded with -profile role-a-profile.
If you want to copy the whole directory, use
--recursive
option to copy the entire directory recursively.
I ran out of storage on my docker build server. I need to delete unnecessary files, but there is a command to safely allocate space.
Identify what is putting pressure on the disk in docker.
Use docker system df command, you can identify the disk usage related to docker.
# docker system df TYPE TOTAL ACTIVE SIZE RECLAIMABLE Images 9 1 2.014GB 1.962GB (97%) Containers 2 0 0B 0B Local Volumes 4 2 824.6MB 781.2MB (94%) Build Cache 0 0 0B 0B
It will remove stopped containers, unused volumes, unused networks, and unused images.
docker system prune
However, the option to delete unused volumes and images is required.
# docker system prune --help
Usage: docker system prune [OPTIONS]
Remove unused data
Options:
-a, --all Remove all unused images not just dangling ones
--filter filter Provide filter values (e.g. 'label=<key>=<value>')
-f, --force Do not prompt for confirmation
--volumes Prune volumes
I was able to reduce the size of the file by 355.4MB.
553d15cd6b78ad0f21788a22e9ce16a7295c4bab97609973 deleted: sha256:7ae9338aed73a0f33568db53740431038d3a1f779c4dae40d27433984e1cd97c deleted: sha256:b1be54c8cadff1e50b87b93559320a1ae57b8d0dd326507148f7ca81d707beed deleted: sha256:86d78f10b9718618eaae056f5dfa1edae518949aee4578e4147268e9db2e75f0 Total reclaimed space: 355.4MB
However, this does not remove the storage.
use –volumes optiion. you can also delete storage.
docker system prune --volumes
WARNING! This will remove:
- all stopped containers
- all networks not used by at least one container
- all volumes not used by at least one container
- all dangling images
- all build cache
Are you sure you want to continue? [y/N] y
If you choose –all option. you can also delete images.
# docker system prune --all
WARNING! This will remove:
- all stopped containers
- all networks not used by at least one container
- all images without at least one container associated to them
- all build cache
Are you sure you want to continue? [y/N]
When you finish deleting unnecessary files, it will be zero.
# docker system df TYPE TOTAL ACTIVE SIZE RECLAIMABLE Images 0 0 0B 0B Containers 0 0 0B 0B Local Volumes 0 0 0B 0B Build Cache 0 0 0B 0B
vue.js の loop
HTML
<script src="https://unpkg.com/vue@3.1.5"></script>
<div id="app">
<p v-for="color in colors">{{ color }}</p>
</div>
JS
const app = Vue.createApp({
data: () => ({
colors: ['black', 'white', 'orange']
})
})
app.mount('#app')
結果は以下の通り、loop して値を取得できる
表示非表示を切り替える
HTML
<script src="https://unpkg.com/vue@3.1.5"></script>
<div id="app">
<p v-if="toggle">hello</p>
</div>
JS
const app = Vue.createApp({
data: () => ({
toggle: true
})
})
app.mount('#app')
HTML
<script src="https://unpkg.com/vue@3.1.5"></script>
<div id="app">
<input type="text" v-bind:value="message">
</div>
JS
const app = Vue.createApp({
data: () => ({
message: 'hello'
})
})
app.mount('#app')
vue.js のデータバインディングの仕組みを紹介。
HTML
<script src="https://unpkg.com/vue@3.1.5"></script>
<div id="app">
<p>
<input type="text" v-model="message">
</p>
<p>
{{ message }}
</p>
</div>
js
console.log(Vue.version)
const app = Vue.createApp({
data: () => ({
message: "hello"
})
})
app.mount('#app')
テキストボックスを変更すると、js の message が変更され、html に反映される
最新 version ではなく、指定の version を読み込む際の設定
https://v3.ja.vuejs.org/guide/installation.html#vue-devtools
では、
<script src="https://unpkg.com/vue@next"></script>
を使うように記載されているが、これだと常に最新になる。
@next の部分を version に変更することで指定した version を読み込ませる事ができる
<script src="https://unpkg.com/vue@3.1.5"></script>
codepen で確認すると、3.1.5 が読み込まれたことを確認。
