#RUBY ZIP CPGZ HOW TO#
#RUBY ZIP CPGZ INSTALL#
#RUBY ZIP CPGZ FULL#

To check whether a gem with any given name exists, use the search box at the website. Make sure that the chosen name is not already in use (which means you should not call your gem lokalise_rails as this name is already taken by me). scription = 'This gem allows to exchange translation files between your Rails app and Lokalise TMS.' Spec.email = 'Lokalise integration for Ruby on Rails' Here’s an example: require File.expand_path('lib/lokalise_rails/version', _dir_) Now use the spec local variable to define the gem’s specifications. Start by requiring a file with the gem version (we are going to add it later) and by providing a specification block: require File.expand_path('lib/lokalise_rails/version', _dir_) In my case, the filename is: lokalise_rails/lokalise_rails.gemspec. Within your project directory create a new file named GEM_NAME.gemspec where GEM_NAME is the name of your brand-new library. provides a nice summary of all fields supported in gemspec. Typically, this file provides the following info: The most important file to create is the gemspec as it will contain specification for your library. Now let’s proceed to adding specific files to it. Start by creating a new project directory: I’ll call mine lokalise_rails. This will allow us to discuss every aspect of the Ruby gem creation in greater detail. While we could utilize a helper library like Juwelier to generate a boilerplate project structure, I’ll be adding every file manually from scratch.

Git version control system (not strictly required).

#RUBY ZIP CPGZ INSTALL#

Install by running gem update -system and gem install bundler. Windows users may take advantage of RubyInstaller. You will also need the following software: The code samples won’t be too complex, so being a Ruby expert is not required in any case. In this tutorial, I will assume that you have a basic knowledge of Ruby language and Rails framework. Third part of the series: /blog/how-to-create-a-ruby-gem-publishing. Second part of the series: /blog/how-to-create-a-ruby-gem-testing-suite. The final result can be found at /bodrovis/lokalise_rails. While this functionality is not overly complex, it will allow us to discuss many specifics regarding the gem creation process.

#RUBY ZIP CPGZ FULL#

These tasks will have additional configuration options so that the user can have full control over this process.

Running the corresponding task will either download translations from Lokalise to Rails, or upload translations from your app to Lokalise. Basically, it will provide two main rake tasks: import and export. This gem will allow the exchange of translation files between the Rails app and Lokalise TMS.

#RUBY ZIP CPGZ HOW TO#

I’ll show you how to create a new gem for the Rails app. We will tackle the above concepts using a “learn by example approach”. Setting up TravisCI and Codecov services.īy the end of the series, you’ll be able to create your own Ruby gem.Working and testing the third-party API.Creating and testing installation tasks.Generating a dummy Rails application for testing.

Setting up a testing suite using RSpec.

In this section we will make the initial preparations, create the project structure, define the gemspec, and proceed to writing the actual gem.Īll in all, this series will cover the following topics: In this series of articles, we will discuss all aspects of how to create a Ruby gem (gem is just a fancy word for “library” or “plugin”).