Example
Thank you
Example
Thank you
1. Install package i18n
2. Add files languages
resources\lang\en.json
resources\lang\vi.json
3. Add plugin resources\js\plugins\langPlugin.ts
* need: legacy: false, see more >>
4. Update resources\js\app.ts
5. Using I18n
- In template
- in <script setup>
Thank you
1: enable false => true
2. set origin value
Thank you
=====================
- sudo nano /etc/postgresql/{version}/main/postgresql.conf
+ listen_addresses = '*'
// + port = 5433 (no needed)
- sudo nano /etc/postgresql/{version}/main/pg_hba.conf
+ host all all [Your_IP_Can_Access]/32 md5
- sudo service postgresql restart
- sudo ufw allow 5433/tcp=====================
- access as root $ sudo -u postgres psql - show all dbs $ \l Connect to the PostgreSQL Database \c taximailinhdb; Grant all privileges on the database: GRANT ALL PRIVILEGES ON DATABASE hangchatgiagocdb TO hangchatgiagocuser; Grant all privileges on all existing tables in the database: GRANT ALL PRIVILEGES ON ALL TABLES IN SCHEMA public TO hangchatgiagocuser; Grant all privileges on all sequences (if you are using sequences): GRANT ALL PRIVILEGES ON ALL SEQUENCES IN SCHEMA public TO hangchatgiagocuser; Optionally, grant privileges on all future tables and sequences: ALTER DEFAULT PRIVILEGES IN SCHEMA public GRANT ALL PRIVILEGES ON TABLES TO hangchatgiagocuser; ALTER DEFAULT PRIVILEGES IN SCHEMA public GRANT ALL PRIVILEGES ON SEQUENCES TO hangchatgiagocuser; Step 3: Verify Permissions (Optional) \dp
1. Install docker, docker compose
- add current $USER to docker group
sudo usermod -aG docker $USER
2. Download source code and build in local using docker-compose
https://github.com/thecaringdeveloper/laravel-cicd-tutorial (1)
3. Install, start Jenkins
- install java
- install jenkins
- start jenkins
- access jenkins localhost:8090
- add user jenkins to docker group: sudo usermod -aG docker jenkins
- add plugin for jenkins
4. Create github repository
- push code in (1) to repository
5. Setup pipeline in source local (a job)
- create Makefile
- create Jenkinsfile
- create a job:
Enter an item name/ Pipeline
/ General: Testing CICD
/ Pipe script from SCM
/ Repository URL: get from repository in github
/ Credentials select credential create below
/ Branch: select branch in git repository
/ Script path: Jenkinsfile
6. create Credential for jenkins connect to github
Manage Jenkins/ manage credentials/ global /add credentials
/ Kind: SSH username with private key
/ scope: Global (jenkins, nodes, items, all child items, ect)
/ id: github
/ username: your_github_username
/ create private, public key: private_key for jenkins, public_key for github
/ Create
* Create a job for CICD
/ name: laravel-test
/ Pipeline: Piple script from SCM
/ SCM: git
/ Repository Url: Your_repo_url
/ Credentials:credential already create above
/ Script path: jenkinsfile
7. Populate .env by using jenkin
+ copy .env file to jenkin:
/ create folder in workspace jenkins include .env file: var/lib/jenkins/workspace/envs/laravel-test
/ create .env file in var/lib/jenkins/workspace/envs/laravel-test
/ add script to copy this .env file when deploy
- Run pipeline
6. Setup EC2
- get key-ec2.pem to ssh to ec2
- chmode 400 key-ec2.pem
- create credential for ec2 in jenkins
7. Create Artifact
Create artifact.zip file
8. Copy Artifact artifact.zip file to ec2
update Jenkinsfile to copy Artifact artifact.zip file to ec2
9. Deploy on ec2, install server on ec2
- install server: sudo yum -y install httpd
- start server: sudo service httpd start
- edit inbound, outbound rules
- install php and extension: sudo yum install php-{...}
- set permission: sudo chown ec2-user:ec2-user /var/www/html
- sudo server httpd restart
Jenkinsfile
Makefile
Thank you
There are two branch
commit on branch A: 123|4.......5
commit on branch B: 123|...678 (checkout from branh A from commit 3, after add commit 678)
---------------------------------------------------
* Git merge: add commits from branch B to branch A follow time create commit
- git checkout A
- git merge B
- handle conflict commits: 3 5 8
- git add .
- git commit -m"M"
=> A: 123|4|678|5|M
--------------------------------------------------
* Git rebase: add all commits from branch B to branch A at left side of branch A from postion of commit of both branch
- git checkout A
- git rebase B
- handle conflict commit: 8 to 4 -> git add . -> git rebase --continue => A: 123|678|4
- handle conflict commit: 4 to 5 -> git add . -> git rebase --continue => A: 123|678|45
- alert result rebase, handle commits with p,s,.. can change name commit in nano, ex 4 => 4'
- ctrl+x -> y to save
=> A: 123|678|4'5
* git rebase itself: select commit want to keep
- git rebase -i idCommit
- git checkout A (A: 12345)
- git rebsae -i 2
- handle conflict commit: 2 to 3 -> git add . -> git rebase --continue => A: 12|3
- handle conflict commit: 3 to 4 -> git add . -> git rebase --continue => A: 12|34
- handle conflict commit: 4 to 5 -> git add . -> git rebase --continue => A: 12|345
- alert result rebase, handle commits with p,s,.. can change name commit in nano, ex 3 => 3', 4->4'
- ctrl+x -> y to save
=> A: 12|3'4'5
---------------------------------------------------
* Git reset: remove commit from a branch
+ git reset --soft idCommit # Removes from HEAD to idCommit, keeps changed staged
+ git reset --hard idCommit # Removes from HEAD to idCommit, DONT keeps changed staged
---------------------------------------------------
* Git commit --amend: to change a last commit message.
+ git commit --amend -m "........"
+ git push origin BranchName -f
* Note:
- Have branh A, PR A to DEV, PM agree merge
- if you commit --amend branch A, after PR A to DEV -> Conflict
---------------------------------------------------
* Git pick cherry: pick commit from a Branch to add for orther branch
- git checkout A
- git cherry-pick -e 7 (git cherry-pick -e idCommit)
-> A: 12345|7
or
- git checkout B
- git cherry-pick -e 5 (git cherry-pick -e idCommit)
-> B: 123678|5
---------------------------------------------------
* Git handle conflict when PR
- git checkout A
- git add .
- git commit -m"..."
- git push origin A
- PR: from A to DEV -> conflict
=> handle
- git checkout A
- git checkout -b A-fix-conflict // create this branch to fix-conflict // because dont want get code from DEV to merge to A
- git checkout DEV
- git pull origin DEV
- git checkout A-fix-conflict
- git merge DEV
- handle fix conflict in local
- git push origin A-fix-conflict
- PR from A-fix-conflict to DEV
- PM aggree merge
=> now A can PR to DEV
Thank you
Để publish pav-kit lên NPM, bạn hãy làm theo các bước dưới đây. Tôi đã tạo thêm file index.js để đảm bảo gói tin hợp lệ. Bước 1: Tạo ...