Deployment (front, back, DB)

KristerV / heliumpay-budgetweb-backend

2 stars 2 forks source link

Deployment (front, back, DB) #13

Closed KristerV closed 6 years ago

KristerV commented 7 years ago

[x] Dockerfile-daemon
[x] Dockerfile-app
[x] docker-compose.yml
[x] Get heliumd and helium-cli to talk to eachother.
[x] create CoreOS server
[x] Deploy to server
[x] Also deploy frontend
[x] Where's nginx in all of this?
[x] Connect actual database
[ ] Should probably test everything with dashd on a separate server just to be sure.
[x] Make the blockchain persistent

KristerV commented 7 years ago

Two questions need to be figured out:

What servers to deploy (dev/staging/prod)
How to deploy them.

What servers to deploy

I don't think there's a need for having dev/staging separately for this project. But dev and prod does make sense. Still how about we just start with production, get it figured out and continue from there, since looks like Helium is being released in 9 days.

How to deploy.

On DigitalOcean I basically wrote some systemctl scripts to keep it alive seen here. It worked great since it's immune to restarts, but I just had way too much deployment logic in there, which should be a separate bash script.

Anyway @jschr can you please specify how you would deploy the server, as you seem to have more experience with Amazons scaling services.

KristerV commented 7 years ago

jschr said he was going to use Amazon's Beanstalk, which doesn't support having heliumd anywhere, so we are without a solution.

Talked to chaositec about this and he offered to create a middle layer of PHP that would route requests between multiple wallets (heliumd).

Pros

Caching
Someone else handles it
Scaling (manual)

Cons

Need to rewrite some of the app
No autoscale
Giving away control, so debugging will be harder for example
Developing is harder, as new APIs will have to be added by chaositec.

He did offer to build the thing and have us deploy, but since we've already built the backend it doesn't seem reasonable. We can just implement caching and manual-scaling ourselves and keep the control of the system. While also being able to autoscale later by using DigitalOcean API.

KristerV commented 6 years ago

Clearly going the self-deploy with docker route at this point :)

KristerV commented 6 years ago

ok let's leave the server for now.