search

zhenlab-ltri / NemaNode

Interactive map of neural connections in the nematode C. elegans. Online at http://nemanode.org.
http://nemanode.org
GNU General Public License v3.0
8 stars 4 forks source link

Update "deploying nemanode" documentation #41

Closed dwitvliet closed 4 years ago

dwitvliet commented 4 years ago

@d2fong Is there any reason that we don't just have the repository loaded into public_html and then just do git pull, npm install (if changes to package.json), npm run populate-database (if changes to the database), and npm run build-prod? That seems simpler than running rsync.

d2fong commented 4 years ago

Ok I will add documentation.

RE: git repositories on the server - Yeah we should set it up like that. That was the setup for the nemanode_test folder, but I don't recall why the prod version didnt use the git repository. Also, I do recall npm run build-prod being really slow on the godady server, so that is why I used rsync on the dist folder after building it on my machine. It might be better after upgrading node.

dwitvliet commented 4 years ago

Thanks! And cool, we should set it up that way then. Is this something you could easily do? Then I would be more comfortable updating the server when small bug-fixes have to be implemented. If the server turns out to be extremely slow for building the app, we can always have GitHub actions build the dist folder automatically and then just pull it directly from git. I wouldn't worry about setting GitHub actions up now, but maybe sometime down the road.

dwitvliet commented 4 years ago

Related #42