* as we're using customised style.scss a manual merge is needed.
this could probably be better served by loading the changes from a
separate .scss file (TBD)
chore: add scaling param to the .drone.yml
fix: issue when dc build fails due to scale
Co-authored-by: surtur <a_mirre@utb.cz>
Reviewed-on: #20
Co-Authored-By: wanderer <wanderer@noreply.git.dotya.ml>
Co-Committed-By: wanderer <wanderer@noreply.git.dotya.ml>
commit 384b118
refactor: remove redundant ipv6 enablement in env
* it is already enabled by default, as witnessed by this error message:
10-listen-on-ipv6-by-default.sh: error: IPv6 listen already enabled
commit abfd7b2
add: loadbalance using traefik
fix: no need to stop the container before build 🚀
* this is handled for us by docker on container re-creation
Co-authored-by: surtur <a_mirre@utb.cz>
Reviewed-on: #19
Co-Authored-By: wanderer <wanderer@noreply.git.dotya.ml>
Co-Committed-By: wanderer <wanderer@noreply.git.dotya.ml>
refactor: .drone.yml + don't run on {push,PR}
add: docker-compose-build pipeline
* general refactoring of .drone.yml
fix: incorrect dependency
* add: don't run img pull on PR
refactor: update .drone.yml logic
chore: adding docker-compose.yml
* it's in fact going to be docker-compose deployment
add: Dockerfile + update baseUrl
* also enhance footer partial that cries when a ref goes missing (such
as when a branch is merged)
Co-authored-by: surtur <a_mirre@utb.cz>
Reviewed-on: #18
Co-Authored-By: wanderer <wanderer@noreply.git.dotya.ml>
Co-Committed-By: wanderer <wanderer@noreply.git.dotya.ml>
refactor: positive rather than negative selection
* i.e. includes as opposed to excludes
chore: separate build and deploy pipeline
* this allows for more granular run conditions and constraints
refactor: remove redundant status==success assertion
Co-authored-by: surtur <a_mirre@utb.cz>
Reviewed-on: #16
Reviewed-by: dalahast <dalahast@noreply.git.dotya.ml>
Co-Authored-By: wanderer <wanderer@noreply.git.dotya.ml>
Co-Committed-By: wanderer <wanderer@noreply.git.dotya.ml>
revert: use hard tabs for consistency
fix: status page link title 'source code' --> 'service status'
Co-authored-by: surtur <a_mirre@utb.cz>
Reviewed-on: #8
chore: notifications don't need to run on PR let's say
fix: fine-tuning the limits
chore: also run notification pipeline on any branch
fix: further limit pipeline execution
fix: limit deploy step execution for master
* run notifications on PR and any branch
chore: add utilization status badges + style
Co-authored-by: surtur <a_mirre@utb.cz>
Reviewed-on: #6
