Basic Deployment #6

New issue

Open

opened 2022-07-19 22:51:25 +02:00 by orblivion · 0 comments

orblivion commented

2022-07-19 22:51:25 +02:00

(Migrated from github.com)

Right now it's running with supervisord and caddy.

We'd like to move to systemd, build binary with Github Actions, and deploy with ansible.

Github Actions

Note to self

Build app on git push
Darwin? (added challenge)
Windows? (added challenge)

Ansible

Wallet Sync Role: Pull built binary from Github
Wallet Sync Role: Configure systemd
Use caddy role
Finishing touches, actual deployment to test user server (The above works with some workarounds)

~Deployed as part of the hub? See below.~

No need for golang role if we use Github Actions for the binary.

Other

Update (or delete) the "hosting" directory of wallet-sync-server. Not sure if we want anything since our hosting details are hidden in the ansible repo. But maybe we can give a similar example systemd conf.

Question: Should this be deployed as part of the hub?

Positives:

Fewer types of things to deploy, for us and for self-hosters.
Fewer settings (custom servers to pick) for user.
Wallet sync may feel to user like a natural extension of the hub's responsibilities (even though to us, it's really not)

Negatives:

Switching sync servers might be glitchy, we haven't prioritized that
If users have trust issues that are different between hub and wallet sync
Users might just want their own wallet sync server but not their own hub?
Big one: If a user has two clients and wants different hubs but same accounts on them for whatever reason, they won't be able to sync.

[Right now](https://github.com/lbryio/wallet-sync-server/tree/master/hosting) it's running with supervisord and caddy. We'd like to move to systemd, build binary with Github Actions, and deploy with ansible. # Github Actions [Note to self](https://blog.kowalczyk.info/article/8dd9c2c0413047c589a321b1ccba7129/using-github-actions-with-go.html) - [x] Build app on git push - [ ] Darwin? (added challenge) - [ ] Windows? (added challenge) # Ansible - [x] Wallet Sync Role: Pull built binary from Github - [x] Wallet Sync Role: Configure systemd - [x] Use caddy role - [ ] Finishing touches, actual deployment to test user server (The above works with some workarounds) ~Deployed as part of the hub? See below.~ No need for golang role if we use Github Actions for the binary. # Other - [ ] Update (or delete) the "hosting" directory of wallet-sync-server. Not sure if we want anything since our hosting details are hidden in the ansible repo. But maybe we can give a similar example systemd conf. ## Question: Should this be deployed as part of the hub? Positives: * Fewer types of things to deploy, for us and for self-hosters. * Fewer settings (custom servers to pick) for user. * Wallet sync may feel to user like a natural extension of the hub's responsibilities (even though to us, it's really not) Negatives: * Switching sync servers might be glitchy, we haven't prioritized that * If users have trust issues that are different between hub and wallet sync * Users might just want their own wallet sync server but not their own hub? * Big one: If a user has two clients and wants different hubs but same accounts on them for whatever reason, they won't be able to sync.