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
I am using citizen in an ec2 with the servers being a localhost on port 3000. I successfully published a module using citizen and can see a module.tar.gz file that is created under the path modules/namespace/name/provider/version (note: I have actual values for the url, namespace, name, provider and version but I am referring to them as such for ease of reading). I then attempted to define an instance of the module following the example given and using the source url/namespace/name/provider as shown in the example. This returned a 404 error. All different versions of the source returned either 404 or "no source url returned" except for when the source was in the form: url/v1/modules/tarball/namespace/name/provider/module.tar.gz which works. I get all the same results when using localtunnel, which gives an https url instaed of the localhost http url. I am using the default settings for all environment variables except for the CITIZEN_STORAGE but the results are the same for if I use file or s3 here. Is there a path that does not involve including the tar file and tarball in the path that will not trigger a 404?
The text was updated successfully, but these errors were encountered:
I am using citizen in an ec2 with the servers being a localhost on port 3000. I successfully published a module using citizen and can see a module.tar.gz file that is created under the path modules/namespace/name/provider/version (note: I have actual values for the url, namespace, name, provider and version but I am referring to them as such for ease of reading). I then attempted to define an instance of the module following the example given and using the source url/namespace/name/provider as shown in the example. This returned a 404 error. All different versions of the source returned either 404 or "no source url returned" except for when the source was in the form: url/v1/modules/tarball/namespace/name/provider/module.tar.gz which works. I get all the same results when using localtunnel, which gives an https url instaed of the localhost http url. I am using the default settings for all environment variables except for the CITIZEN_STORAGE but the results are the same for if I use file or s3 here. Is there a path that does not involve including the tar file and tarball in the path that will not trigger a 404?
The text was updated successfully, but these errors were encountered: