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
{{ message }}
This repository has been archived by the owner on Aug 28, 2021. It is now read-only.
I am wondering what would be a recommended best practice for keeping up to date with the latest changes to the Speckle code-base in a production installation (not using Docker). I am thinking the following might work:
fork SpeckleServer
fork SpeckleAdmin
npm run build and commit the dist folder to my fork of SpeckleAdmin
in my SpeckleServer fork add another plugins folder called my-plugins
in my SpeckleServer fork checkout SpeckleAdmin as a submodule into my-plugins/SpeckleAdmin
in my SpeckleServer fork add any files needed for my deploy
in my SpeckleServer fork make sure my deploy does a checkout of all submodules
Anytime SpeckleServer has new updates merge the changes into my fork. Do the same with SpeckleAdmin.
Any thoughts? Thanks, Andrew
The text was updated successfully, but these errors were encountered:
Hi Andrew, I personally clone the repos I need, create a branch for my development work, npm run build , node server.js for testing, merge changes from master into my branch everytime I am behind it, potentially merge my branch into master once I am not with dev work. Quite straightforward and no idea if this is a "best practice"...
So, currently I am doing an automatic deployment on commits to my master branch of SpeckleServer. I have committed SpeckleAdmin into the plugins folder so that SpeckleServer can find it and use it. The main problem with this setup is SpeckleAdmin isn't actually connected to the SpeckleAdmin repo anymore (i just copied the files), so I can't really make changes to SpeckleAdmin and submit pull requests. Also, if I try to merge SpeckleServer or do pull requests for SpeckleServer updates I am going to have issues with my plugins folder.
How do you manage your plugins folder? Do you use plugins? Do you just copy plugins manually into the plugins folder on your server? Are you managing your own server/web folders, IE SSH into it and do git pulls to get a new version? If this is the case how do you test things locally? IE how do you test updates to SpeckleAdmin code?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I am wondering what would be a recommended best practice for keeping up to date with the latest changes to the Speckle code-base in a production installation (not using Docker). I am thinking the following might work:
npm run build
and commit thedist
folder to my fork of SpeckleAdminAnytime SpeckleServer has new updates merge the changes into my fork. Do the same with SpeckleAdmin.
Any thoughts? Thanks, Andrew
The text was updated successfully, but these errors were encountered: