Merge branch 'main' of gitlab.com:domaindrivenarchitecture/c4k-gitea into main
commit
a25b031789
@ -0,0 +1,22 @@
|
||||
#!/usr/bin/env bash
|
||||
|
||||
# set things
|
||||
set -o nounset
|
||||
set -o xtrace
|
||||
set -o errexit
|
||||
set -eo pipefail
|
||||
|
||||
# dirs
|
||||
srcDir="/home/$USER/"
|
||||
srcName="main.js"
|
||||
targetDir="/home/$USER/"
|
||||
targetName="c4k-gitea.js"
|
||||
|
||||
echo "build"
|
||||
shadow-cljs compile frontend
|
||||
|
||||
echo "move and rename file"
|
||||
cp $srcDir$srcName $targetDir$targetName
|
||||
|
||||
echo "build"
|
||||
(cd $targetDir; lein ring server)
|
@ -1,14 +1,43 @@
|
||||
# stable release (should be done from master)
|
||||
# Release process
|
||||
|
||||
## ... for testing (snapshots)
|
||||
|
||||
Make sure your clojars.org credentials are correctly set in your ~/.lein/profiles.clj file.
|
||||
|
||||
``` bash
|
||||
git add .
|
||||
git commit
|
||||
```
|
||||
|
||||
``` bash
|
||||
lein deploy # or lein deploy clojars
|
||||
```
|
||||
#adjust [version]
|
||||
vi package.json
|
||||
|
||||
## ... for stable release
|
||||
|
||||
Make sure tags are protected in gitlab:
|
||||
Repository Settings -> Protected Tags -> set \*.\*.\* as tag and save.
|
||||
|
||||
``` bash
|
||||
git checkout main # for old projects replace main with master
|
||||
git add .
|
||||
git commit
|
||||
```
|
||||
|
||||
Open package.json, find ":version" keyword and remove "-SNAPSHOT" from version number.
|
||||
|
||||
``` bash
|
||||
git add .
|
||||
git commit -m "Release [version]"
|
||||
lein release
|
||||
git push --follow-tags
|
||||
```
|
||||
|
||||
# bump version - increase version and add -SNAPSHOT
|
||||
vi package.json
|
||||
Open package.json again, increase version increment by one and add "-SNAPSHOT".
|
||||
|
||||
``` bash
|
||||
git commit -am "version bump"
|
||||
git push
|
||||
```
|
||||
```
|
||||
|
||||
Done.
|
||||
|
@ -0,0 +1,21 @@
|
||||
# Upgrading process
|
||||
|
||||
## adhoc (on kubernetes cluster)
|
||||
|
||||
Ssh into your kubernetes cluster running the gitea instance.
|
||||
|
||||
``` bash
|
||||
kubectl edit configmap gitea-env
|
||||
# make sure INSTALL_LOCK under security is set to true to disable the installation screen
|
||||
# save and exit
|
||||
kubectl edit deployments gitea
|
||||
# search for your current gitea version, e.g. 1.17.0
|
||||
# replace with new version
|
||||
# save and exit
|
||||
kubectl scale deployment gitea --replicas=0
|
||||
kubectl scale deployment gitea --replicas=1
|
||||
```
|
||||
|
||||
Logging into the admin account should now show the new version.
|
||||
|
||||
You may want to update your c4k-gitea resources to reflect the changes made on the cluster.
|
Loading…
Reference in New Issue