update,
This commit is contained in:
31
.gitattributes
vendored
Normal file
31
.gitattributes
vendored
Normal file
@@ -0,0 +1,31 @@
|
||||
*.mp4 filter=lfs diff=lfs merge=lfs
|
||||
*.zip filter=lfs diff=lfs merge=lfs
|
||||
*.7z filter=lfs diff=lfs merge=lfs
|
||||
*.tar.gz filter=lfs diff=lfs merge=lfs
|
||||
*.jpg filter=lfs diff=lfs merge=lfs
|
||||
*.png filter=lfs diff=lfs merge=lfs
|
||||
*.avif filter=lfs diff=lfs merge=lfs
|
||||
*.webm filter=lfs diff=lfs merge=lfs
|
||||
*.mkv filter=lfs diff=lfs merge=lfs
|
||||
|
||||
# Documents
|
||||
*.doc diff=astextplain
|
||||
*.DOC diff=astextplain
|
||||
*.docx diff=astextplain
|
||||
*.DOCX diff=astextplain
|
||||
*.dot diff=astextplain
|
||||
*.DOT diff=astextplain
|
||||
*.pdf diff=astextplain
|
||||
*.PDF diff=astextplain
|
||||
*.rtf diff=astextplain
|
||||
*.RTF diff=astextplain
|
||||
|
||||
*.gif filter=lfs diff=lfs merge=lfs
|
||||
*.GIF filter=lfs diff=lfs merge=lfs
|
||||
*.bmp filter=lfs diff=lfs merge=lfs
|
||||
*.BMP filter=lfs diff=lfs merge=lfs
|
||||
*.tiff filter=lfs diff=lfs merge=lfs
|
||||
*.TIFF filter=lfs diff=lfs merge=lfs
|
||||
*.wav filter=lfs diff=lfs merge=lfs
|
||||
*.WAV filter=lfs diff=lfs merge=lfs
|
||||
*.log filter=lfs diff=lfs merge=lfs
|
1
.gitignore
vendored
Normal file
1
.gitignore
vendored
Normal file
@@ -0,0 +1 @@
|
||||
**/~*.*
|
7
gitUpdate.bat
Normal file
7
gitUpdate.bat
Normal file
@@ -0,0 +1,7 @@
|
||||
git status .
|
||||
|
||||
@pause
|
||||
|
||||
git add .
|
||||
git commit -m"update eyt278181,"
|
||||
start git push
|
16
gitUpdate.sh
Executable file
16
gitUpdate.sh
Executable file
@@ -0,0 +1,16 @@
|
||||
#!/usr/bin/env bash
|
||||
|
||||
set -ex
|
||||
|
||||
git config --global http.version HTTP/1.1
|
||||
git config --global lfs.allowincompletepush true
|
||||
git config --global lfs.locksverify true
|
||||
git config --global http.postBuffer 5368709120
|
||||
|
||||
git add .
|
||||
|
||||
git commit -m 'update,'
|
||||
|
||||
git push
|
||||
|
||||
echo "done"
|
16
meta.md
Normal file
16
meta.md
Normal file
@@ -0,0 +1,16 @@
|
||||
monitor-24.com
|
||||
|
||||
明白嘅,
|
||||
咁我又假設有客人想做 integration ,
|
||||
咁我想再問下有冇機會有 API doc 呢類文件可以望一望?
|
||||
|
||||
唔好意思先,我可能未帶到客仔比你住,不過傾開我想了解多 D 先
|
||||
假設有客人買 1 lot (例如過千個 website monitor )咁先算啦
|
||||
咁一般而言都唔會叫個客人一個一個咁督入去架嘛
|
||||
咁所以好多時都有 D 叫 "API" 嘅野話比客仔可以點樣去 integrate 落去你地服務果度,咁果份 doc 就叫 "API doc".
|
||||
|
||||
Sorry in advance as i may not the right on to get customer to you but i would liek to know more by this chance.
|
||||
|
||||
so let say someone (possibly a corperate-customer) would like to subscribe one lot (let say 1000 website monitoring) service from you. how can you serve ? currently, AFAIK a popular model is leaving a API (endpoint) that can communiate with your system. when customer pass a HTTP request (with parameter/query) to this endpoint to your system. then your system parse those parameters, configure them accordingly (i.e. website monitoring --drive--> discord paging).
|
||||
|
||||
but most of the time this kind of process is expected full automatic. so is there any documentation to tell user/customer how to do that ?
|
Reference in New Issue
Block a user