Mirror/robosats
1
0
Fork 0
mirror of https://github.com/RoboSats/robosats.git synced 2024-12-13 02:46:28 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Fix github action workflow symlinks ignored

Browse Source
This commit is contained in:
Reckless_Satoshi 2022-08-22 10:35:54 -07:00
parent d769129142
commit 6013757e24
No known key found for this signature in database
GPG Key ID: 9C4585B561315571
2 changed files with 22 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
.github/workflows/node-client-image.yml vendored
View File

@ -1,4 +1,4 @@
name: RoboSats Client Node App Image CI/CD
name: Client App Image CI/CD
on:
workflow_dispatch:
@ -20,13 +20,18 @@ jobs:
steps:
- uses: actions/checkout@v3
- name: 'Copy Static' # Only needed because Github actions does not support symlinks
run: |
rm nodeapp/static
cp -r frontend/static nodeapp/static
- name: 'Download main.js Artifact'
uses: dawidd6/action-download-artifact@v2
with:
workflow: frontend-build.yml
workflow_conclusion: success
name: main-js
path: frontend/static/frontend/
path: nodeapp/static/frontend/
- name: 'Log in to Docker Hub'
uses: docker/login-action@v2
@ -52,10 +57,6 @@ jobs:
id: commit
uses: pr-mpt/actions-commit-hash@v1
- name: 'Save Commit Long Hash to TXT File'
run: |
echo ${{ steps.commit.outputs.long }}>"commit_sha.txt"
- name: 'Set up QEMU'
uses: docker/setup-qemu-action@v2

16
nodeapp/README.md
View File

@ -4,4 +4,18 @@ RoboSats app for soverign nodes ( Umbrel, Citadel, Start9 ...). This app serves
At the moment it has no special integration with your local lightning wallet (e.g. LND). This can be achieved easily by installing a WebLN compatible extension in your browser (e.g. getAlby).
The container launches two processes: 1) A `socat` that will expose RoboSats coordinator API over HTTP using the docker orchestration Tor socks proxy and 2) a `http-server` that will serve all static files (including the Javascript client app) directly from your own node (should reduce loading times by a lot). Every request that cannot be served by your node http-server will be forwarded to the RoboSats coordinator (that is: API calls and Robot avatar images).
# How it works
The container launches two processes: 1) A `socat` that will expose RoboSats coordinator API over HTTP on localhost:81 using the docker orchestration TOR socks proxy and 2) a `http-server` that serves all static files (including the Javascript client app) directly from your own node (should reduce loading times by a lot). Every request that cannot be served by your node http-server will be forwarded to the RoboSats coordinator (that is: API calls and Robot avatar images).
# Why host your own RoboSats client
Advantages over a full over-the-internet RoboSats experience:
1. Dramatically faster load times.
2. Safer: you control what RoboSats client app you run.
3. Access RoboSats safely from any browser / device. No need to use TOR if you are on your local network or using VPN: your node backend handles the torification needed for anonymization.
4. Allows control over what P2P market coordinator you connect to (defaults to robosats6tkf3eva7x2voqso3a5wcorsnw34jveyxfqi2fu7oyheasid.onion)
# Future upgrades
1. Increase availability by procesing API requests via I2P when TOR is not available.