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
We host some of our ruby gems on a private cloudsmith repository. Steep does not seem to be able to pull signature files from gems on cloudsmith. Can you confirm that?
To work around this issue i tried to temporarily avoid using cloudsmith. My application and the source for this gem are in the same repository so i updated my project to refer to the gem via file path rather than via cloudsmith. Then after adding the signatures i needed, my plan was to symlink those signature files back to a folder in my application that uses the gem so that I would not have to duplicate them. This did not seem to work. When i duplicate the files it did work but not when i tried to symlink them. Is this something that can be fixed?
The text was updated successfully, but these errors were encountered:
Is cloudsmith is a private gem repository? I think there is no difference if the gem is pulled from rubygems.org or other repository. Can you confirm if your gem package contains the RBS files as you expect?
We host some of our ruby gems on a private cloudsmith repository. Steep does not seem to be able to pull signature files from gems on cloudsmith. Can you confirm that?
To work around this issue i tried to temporarily avoid using cloudsmith. My application and the source for this gem are in the same repository so i updated my project to refer to the gem via file path rather than via cloudsmith. Then after adding the signatures i needed, my plan was to symlink those signature files back to a folder in my application that uses the gem so that I would not have to duplicate them. This did not seem to work. When i duplicate the files it did work but not when i tried to symlink them. Is this something that can be fixed?
The text was updated successfully, but these errors were encountered: