M-Labs/it-infra
M-Labs
/
it-infra
8
0
Fork 4
Code Issues 12 Pull Requests 2 Releases Wiki Activity

Deploy web2019 to the intl domain #40

Open
esavkin wants to merge 2 commits from 134-deploy into master
pull from: 134-deploy
merge into: M-Labs:master
Conversation 1 Commits 2 Files Changed 1 +11
esavkin commented 2024-06-20 17:44:10 +08:00
Owner
Copy Link
No description provided.
esavkin added 1 commit 2024-06-20 17:44:10 +08:00
be2aa53220 Deploy web2019 to the intl domain 
Signed-off-by: Egor Savkin <es@m-labs.hk>
sb10q reviewed 2024-06-20 17:46:08 +08:00
nixbld-etc-nixos/configuration.nix Outdated
@ -654,0 +659,4 @@
cp /opt/hydra_id_ed25519.pub $HOME/.ssh/id_ed25519.pub && \
echo "5.78.86.156 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIEMbV69aqkHdQ1T5lMuALyHjNowU1rottZtEV4OhKQ6Y" > $HOME/.ssh/known_hosts && \
chmod 600 $HOME/.ssh/id_ed25519 && \
rsync -r -c $(jq -r '.outputs[0].path' < $HYDRA_JSON) zolaupd@5.78.86.156:/var/www/m-labs-intl.com/html/
sb10q commented 2024-06-20 17:46:08 +08:00
Owner
Copy Link

Is this tested? I doubt rsync is in scope.
You may also want to use writeShellScript.

Is this tested? I doubt rsync is in scope. You may also want to use writeShellScript.
esavkin force-pushed 134-deploy from be2aa53220 to 7455367033 2024-06-21 10:53:24 +08:00 Compare
sb10q commented 2024-06-24 10:21:08 +08:00
Owner
Copy Link

Temporary files created inside Nix derivations are automatically cleaned up after build, but is it the case here?

Temporary files created inside Nix derivations are automatically cleaned up after build, but is it the case here?
esavkin added 1 commit 2024-06-24 10:58:12 +08:00
1b3efaa5dd Remove temporary files after uploading website 
Signed-off-by: Egor Savkin <es@m-labs.hk>
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
You can also view command line instructions.

Step 1:

From your project repository, check out a new branch and test the changes.
git checkout -b 134-deploy master
git pull origin 134-deploy

Step 2:

Merge the changes and update on Gitea.
git checkout master
git merge --no-ff 134-deploy
git push origin master
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: M-Labs/it-infra#40
No description provided.
Delete Branch "134-deploy"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?