Closed szeidler closed 5 years ago
That's great to hear! I'd say that sounds like the right plan. Fork with periodic merges. If you have custom modules that you think would be more generally useful, you could even send us a pull request.
On Fri, Aug 17, 2018, 7:12 AM Stephan Zeidler notifications@github.com wrote:
Hi,
we're using Lacuna for one of our projects and it's working quite well. We have been using the git clone setup and always fetched the new releases with git pull.
I'm wondering what is you suggested best practice to deal with custom modules in that setup and still keep it easy updateable? Maybe a fork with merging from upstream?
Thanks for any help.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/PoeticMediaLab/Lacuna/issues/233, or mute the thread https://github.com/notifications/unsubscribe-auth/ABWkocxjdbqoLKzueVG2m-Sk4Psy7Krgks5uRrM1gaJpZM4WBdew .
--
Typed with thumbs. @mwidner http://michaelwidner.com
Hi,
we're using Lacuna for one of our projects and it's working quite well. We have been using the
git clone
setup and always fetched the new releases withgit pull
.I'm wondering what is you suggested best practice to deal with custom modules in that setup and still keep it easy updateable? Maybe a fork with merging from upstream?
Thanks for any help.