Serving only the build directory - github, and make it easier for clients to deploy the app.
Unanswered
Cane Corso posted this in #help-forum
Cane CorsoOP
Hey, i have a big project that users can download and use.
Currently its quite hard to install and run this app, and i want to make it better for them for running it.
(I do suggest them to use Vercel, but sadly they need to create a repository of their own and pull the changes every time i push anything, which will make it not-updatable)
I thought about including the build folder inside the repository, and hide all other other files except the package.json, public folder and etc.
But here is my first issue, the
The second new feature i thought about is adding a button that sends an api request, and there it will run a command like "npm run pull" (which will run git pull and restart), and its actually worked very well, and they dont have to re build the website on every new update.
but is it a good idea? i think its kinda weird to push a full build directory and let the users pull it on every time, will it cause any issues?
And the third problem i had is, the app is starting on
I thought about teaching them how to create an nginx reverse proxy or make it automatically by a shell script, but will it be a good idea? maybe there is simpler solutions?
Thanks!!
Currently its quite hard to install and run this app, and i want to make it better for them for running it.
(I do suggest them to use Vercel, but sadly they need to create a repository of their own and pull the changes every time i push anything, which will make it not-updatable)
I thought about including the build folder inside the repository, and hide all other other files except the package.json, public folder and etc.
But here is my first issue, the
build\cache\webpack\server-production\0.pack file generated is too large, 106k kbs, and github allows max of 100k kbs per file.The second new feature i thought about is adding a button that sends an api request, and there it will run a command like "npm run pull" (which will run git pull and restart), and its actually worked very well, and they dont have to re build the website on every new update.
but is it a good idea? i think its kinda weird to push a full build directory and let the users pull it on every time, will it cause any issues?
And the third problem i had is, the app is starting on
localhost:3000, but what if i want them to connect to a domain, and ssl? and how can i change the localhost:3000 into their domain name instead?I thought about teaching them how to create an nginx reverse proxy or make it automatically by a shell script, but will it be a good idea? maybe there is simpler solutions?
Thanks!!