Build with Drone
This commit is contained in:
parent
e4ea529fbe
commit
deff3a6344
25
.drone.yml
Normal file
25
.drone.yml
Normal file
@ -0,0 +1,25 @@
|
|||||||
|
kind: pipeline
|
||||||
|
name: build-and-deploy
|
||||||
|
type: docker
|
||||||
|
|
||||||
|
platform:
|
||||||
|
os: linux
|
||||||
|
arch: arm64
|
||||||
|
|
||||||
|
|
||||||
|
steps:
|
||||||
|
- name: docker-build-and-push
|
||||||
|
image: thegeeklab/drone-docker-buildx # Absurd that this isn't offered as first-party!
|
||||||
|
privileged: true
|
||||||
|
settings:
|
||||||
|
registry: gitea.scubbo.org
|
||||||
|
username: scubbo
|
||||||
|
password:
|
||||||
|
from_secret: gitea_password
|
||||||
|
repo: gitea.scubbo.org/${DRONE_REPO}
|
||||||
|
tags:
|
||||||
|
- ${DRONE_COMMIT_SHA:0:10}
|
||||||
|
platforms:
|
||||||
|
- linux/arm64
|
||||||
|
- linux/amd64
|
||||||
|
# TODO - use kustomize to update the deployed image.
|
@ -21,16 +21,16 @@
|
|||||||
|
|
||||||
<p>
|
<p>
|
||||||
(This is only listing user-facing functionality - there are also plenty of technical or QA considerations that I'd
|
(This is only listing user-facing functionality - there are also plenty of technical or QA considerations that I'd
|
||||||
like to add! See the <a href="https://github.com/scubbo/edh-elo/blob/placeholder/NOTES.md">GitHub Repo</a> for more
|
like to add! See the <a href="https://gitea.scubbo.org/scubbo/edh-elo/src/branch/main/NOTES.md">GitHub Repo</a> for more
|
||||||
details)
|
details)
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
As you can probably tell, this app is currently in a "pre-alpha" state, with minimal functionality and cosmetic
|
As you can probably tell, this app is currently in a "pre-alpha" state, with minimal functionality and cosmetic
|
||||||
considerations so as to just get something in front of users.
|
considerations so as to just get something in front of users.
|
||||||
</p>
|
</p>
|
||||||
<p>
|
<p>
|
||||||
HUGE thanks to my friend Patrick for getting a jump-start on data-tracking, so that 1. I had some data to work with,
|
HUGE thanks to my friend Patrick for getting a jump-start on data-tracking, so that 1. I had some data to work with,
|
||||||
and 2. I had inspiration to keep working on this project.
|
and 2. I had inspiration to keep working on this project.
|
||||||
</p>
|
</p>
|
||||||
{% endblock %}
|
{% endblock %}
|
||||||
|
@ -8,6 +8,11 @@
|
|||||||
{% endblock %}
|
{% endblock %}
|
||||||
|
|
||||||
{% block content %}
|
{% block content %}
|
||||||
|
<p>
|
||||||
|
<b>PLEASE NOTE</b> that this application is currently in a "pre-alpha" state. You should <i>not</i> depend on it for
|
||||||
|
durable data persistence. Please use this application only on an experimental basis, and make a backup of your play
|
||||||
|
data elsewhere separately (for now!).
|
||||||
|
</p>
|
||||||
<input type="hidden" id="player_deck_data" value="{{ player_decks }}"/>
|
<input type="hidden" id="player_deck_data" value="{{ player_decks }}"/>
|
||||||
<label for="date">Date:</label>
|
<label for="date">Date:</label>
|
||||||
<input type="date" id="date" name="date">
|
<input type="date" id="date" name="date">
|
||||||
|
Loading…
x
Reference in New Issue
Block a user