You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A temporary alternative to chel serve would be implementing grunt serve - the idea of which would be to serve an optimized production build of the app.
I think whether we do chel serve or grunt serve first, we need a command to generate a build of the app that is production optimized. Currently we only generate a development build.
So a possible route forward would be to:
Implement a grunt deploy command that uses esbuild to create a production bundle of the app
Then implement grunt serve <folder> that just runs the server on port 8000 by default (and not browsersync). Make sure to take into account the contracts folder (perhaps grunt deploy would copy the contracts folder into a directory containing the groupincome bundle).
Note: chel serve is essentially the same thing, but more difficult to implement because the chel command doesn't have the Chelonia server in it (that's still here in Group Income under the backend/ folder)
EDIT: Another possibility is making it possible install a groupincome command via npm install -g and running that.
The point is our current approach of running grunt dev is not appropriate for deploying to a server, and we need something simpler and without the overhead of grunt dev.
The text was updated successfully, but these errors were encountered:
@Silver-IT keep in mind that there is now a releases branch that will contain each release of the website (including the contracts) and this will be what grunt serve will be serving...
Problem
We'll at some point need to be able to deploy GI to a running server.
Solution
Background:
grunt dev
as the only way of serving the app.chel serve
which is the ideal way that this issue would be closedchel serve
would be implementinggrunt serve
- the idea of which would be to serve an optimized production build of the app.I think whether we do
chel serve
orgrunt serve
first, we need a command to generate a build of the app that is production optimized. Currently we only generate a development build.So a possible route forward would be to:
grunt deploy
command that usesesbuild
to create a production bundle of the appgrunt serve <folder>
that just runs the server on port 8000 by default (and notbrowsersync
). Make sure to take into account thecontracts
folder (perhapsgrunt deploy
would copy thecontracts
folder into a directory containing the groupincome bundle).chel serve
is essentially the same thing, but more difficult to implement because thechel
command doesn't have the Chelonia server in it (that's still here in Group Income under thebackend/
folder)Old Commentary/notes
See:
EDIT: Another possibility is making it possible install a
groupincome
command vianpm install -g
and running that.The point is our current approach of running
grunt dev
is not appropriate for deploying to a server, and we need something simpler and without the overhead ofgrunt dev
.The text was updated successfully, but these errors were encountered: