GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.
@@ -42,13 +42,14 @@ This will generate the files in a directory called `public`. These files can now
### Workflow for camp.fsci.in
- Make necessary changes and commit the changes to git.
- Run the `generate-site` script (present in the Scripts folder in the root folder) from the website folder.
- Switch to the `production` branch.
- Run the `update` script, commit the changes in git and push the changes to production branch.
- Run the `generate-site` script (present in the Scripts folder in the root folder) from the website folder
(`cd website && ../scripts/generate-site`).
- Switch to the `production` branch (`git checkout production`).
- Run the `update` script, commit the changes in git and push the changes to production branch (cd .. && ./update).
### How to update website in production
- First you need ssh access to the server ([contact](https://camp.fsci.in/#contact) the camp team for the same).
- Add the server as a remote: `git remote add camp ssh://USERNAME@monitor.fsci.in:camp/camp.git` (Replace USERNAME with the original username).
- Add the server as a remote: `git remote add camp ssh://USERNAME@monitor.fsci.in:/home/USERNAME/camp/camp.git` (Replace USERNAME with the original username).
- Switch to the production branch: `git checkout production`.
- Push the changes to the newly added remote: `git push camp production`.
- That's it. A [post-receive hook](https://git-scm.com/docs/githooks) on the remote will update the website automagically.