9 32 120 DEV 32-7ef023e4 39-41 Gem submission implementation. The implementation must receive the .gem file, unzip it, and update specs files. As a result, files become available for downloading. src/main/java/com/artipie/gem/SubmitGem.java @Sammers21 titantins@gmail.com 24 9 30 DEV 9-d34d2491 33-35 Random gem name generation. Currently, when gem is uploaded, it has a name 'upd.gem'. The approach does not allow us to upload concurrently. Names should chosen randomly. src/main/ruby/SubmitGem.rb @g4s8 g4s8.public@gmail.com 25 9 30 DEV 9-d0d317ad 38-40 Sync generated indexes with Storage. For now, generated indexes are stored locally in temp-gem-index directory. Those should also be syncronized with storage. src/main/ruby/SubmitGem.rb @g4s8 g4s8.public@gmail.com 30 25 30 DEV 25-b18eefce 99-102 Use underlying storage. Currency, local directory 'temp-gem-index' is used as a storage for serving metadata files. This approaches has a significant amount of drawbacks, that is why we should change it. src/main/java/com/artipie/gem/GemSlice.java @Sammers21 titantins@gmail.com 42 9 30 DEV 9-59a54dc4 22-24 Adapt AstoIndexer to generate files in storage. For now, generated indexes are stored locally in temp-gem-index directory. Files should be generated in storage instead. src/main/ruby/AstoIndexer.rb @Sammers21 titantins@gmail.com 11 32 120 DEV 32-d2ff0e89 40-42 Gem Information implementation. The implementation must be able to response with either json or yaml format. An example response can be obtained via {@code curl https://rubygems.org/api/v1/gems/rails.json} src/main/java/com/artipie/gem/GemInfo.java @Sammers21 titantins@gmail.com 15 13 30 DEV 13-4aa56782 46-49 Initialize on first request. Currently, Ruby runtime initialization and Slice evaluation is happening during the GemSlice construction. Instead, the Ruby runtime initialization and Slice evaluation should happen on first request. src/main/java/com/artipie/gem/GemSlice.java @Sammers21 titantins@gmail.com 101 85 30 DEV 85-3d638df9 35-37 Move this class to artipie/asto repo This class was created due to lack of unchecked supplier implementation in asto project. Let's move it to asto repo. src/main/java/com/artipie/gem/UncheckedSupplier.java @g4s8 g4s8.public@gmail.com 124 122 30 DEV 122-d55ec42f 34-36 Add tests for this class. Check if it can add plain string values to JSON, and check it can support nested tree structures formatting. src/main/java/com/artipie/gem/JsonMetaFormat.java @g4s8 g4s8.public@gmail.com 134 103 30 DEV 103-34f1c84f 18-23 Inspect rubygems API response to add more fields. Check responses for different Gem requests for origin rubygems.org or reverse-engineer Gem repository Ruby code to understand all fields that should be added to gems API response. Now all mandatory fields are present in this metadata genrator but different gem responses may have optional fields. E.g. https://rubygems.org/api/v1/gems/builder.json src/main/java/com/artipie/gem/ruby/RubyGemMeta.java @g4s8 g4s8.public@gmail.com 137 122 30 DEV 122-e8ad5314 20-25 Add tests for this class and ApiGetSlice. Check that this class produces valid YAMLs as for JsonMetaFormat. Also, check that ApiGetSlice returns valid response for `.yaml` suffix in response path. Test for `ApiGetSlice` could be quite primitive just to check that slice is working fine with yaml. On the other hand `YamlMetaFormatTest` must cover all methods of YamlMetaFormat (same as JsonMetaFormatTest). src/main/java/com/artipie/gem/YamlMetaFormat.java @g4s8 g4s8.public@gmail.com 140 137 30 DEV 137-c2b83a35 31-34 Add tests for ApiGetSlice. Check that ApiGetSlice returns valid response for `.yaml` suffix in response path. Test for `ApiGetSlice` could be quite primitive just to check that slice is working fine with yaml. src/main/java/com/artipie/gem/http/ApiGetSlice.java @LightPro-Inc baudolivier.oura@gmail.com