The Web IDE needs to move servers to be hosted on the ENF's architecture.
The backend has currently been running flawlessly on the following server for the past 2 months:
Hosting: Digital Ocean
CPU Type: Premium Intel
vCPUs: 4
Memory: 8gb
SSD: 160gb
Transfer: 5tb
The likeliest thing to run out of is SSD as it currently stores wasm/abi/project files to disk. Optimizations can occur later, but are not necessary right now.
Front-end is running on Netlify. This would be running under free-tier except for the fact that there is a custom domain (eos-web-ide.netlify.app)
AC:
Provision server capable of hosting the backend API. Preferably with more SSD capacity than 160gb
Set up nginx with default pointing towards /var/www/webide
Set up ide.eosnetwork.com domain to point to the server
Set up CDN in front of the server
Set up 2 github workflows (one on each repo, api/ui) that will trigger a placeholder bash script on the home directory of the user (update_api.sh/update_ui.sh) every time that something is pushed to main (no tag requirement) of the respective repo
Cache bust the cdn on UI pushes
Setup credentials for Nathan using an ssh key so that he can take care of the rest to get the real applications online
The Web IDE needs to move servers to be hosted on the ENF's architecture.
The backend has currently been running flawlessly on the following server for the past 2 months: Hosting: Digital Ocean CPU Type: Premium Intel vCPUs: 4 Memory: 8gb SSD: 160gb Transfer: 5tb
The likeliest thing to run out of is SSD as it currently stores wasm/abi/project files to disk. Optimizations can occur later, but are not necessary right now.
Front-end is running on Netlify. This would be running under free-tier except for the fact that there is a custom domain (eos-web-ide.netlify.app)
AC:
defaultpointing towards/var/www/webideide.eosnetwork.comdomain to point to the serverupdate_api.sh/update_ui.sh) every time that something is pushed tomain(no tag requirement) of the respective repoRepositories: