No description
Find a file
Douze Baie c08c4f1f10
All checks were successful
deploy to prod / Build and deploy site (push) Successful in 49s
update readme
2024-09-26 22:46:27 +02:00
.forgejo/workflows fix deploy action 2024-09-26 10:27:25 +02:00
.github/workflows implement deploy in deploy action 2024-09-26 10:23:01 +02:00
.vitepress s/Nixos/NixOS/g 2024-09-25 17:33:00 +02:00
bin add safeguard against running from another branch than main in push-to-prod script 2024-09-26 22:26:07 +02:00
components feat(name): rename to NixiN 2024-09-25 18:13:09 +03:00
public update logo 2024-09-26 11:13:43 +02:00
.gitignore initial commit 2024-09-24 10:14:24 +03:00
about.md feat: ConfigForm component and empty doc files 2024-09-24 13:46:27 +03:00
configure.md feat: ConfigForm component and empty doc files 2024-09-24 13:46:27 +03:00
index.md s/Nixos/NixOS/g 2024-09-25 17:33:00 +02:00
LICENSE initial commit 2024-09-24 10:14:24 +03:00
package-lock.json update name 2024-09-25 17:27:16 +02:00
package.json initial commit 2024-09-24 10:14:24 +03:00
README.md update readme 2024-09-26 22:46:27 +02:00
roadmap.md feat: draft roadmap for v0.1 2024-09-26 11:35:37 +03:00
technical-principles.md start writing technical principles 2024-09-26 21:44:28 +02:00

NixiN Web

Building the web site

npm run docs:build

Testing localy

npm run docs:dev

Manually deploying to a server usign sftp

pushd .vitepress/dist/ ; echo "put -r *" | sftp -b - -N user@server.domain.tld:www ; popd

Automatically deploying to a server with forgejo action

Development is taking place in the main branch, or in feature branches that are then merged into main. To deploy the web site to production server the changes in main branch are merged to the prod branch, which is triggering the deploy action, defined in .forgejo/workflows/deploy.yaml This action builds the web site (npm run docs:build) and then deploys it to the production server using sftp with public/private key authentiction

You can use the script in bin/push-to-prod.sh to perform the merge of main branch into prod branch

if you forked this repository, you need to create the secrets needed by the deploy action (in repository settings->actions->secrets) :

  • DEPLOY_USER : OS user to connect to production server
  • DEPLOY_TARGET : sftp target where the web site has to be deployed, in the form of server.domain.tld:path
  • DEPLOY_SSH_PRIVATE_KEY : private ssh key used to authenticate with the server and configure the server witht the public key corresponding to DEPLOY_SSH_PRIVATE_KEY