How to Install and Uninstall rubygem-apipie-rails.noarch Package on Fedora 34

Last updated: November 26,2024

1. Install "rubygem-apipie-rails.noarch" package

Here is a brief guide to show you how to install rubygem-apipie-rails.noarch on Fedora 34


    
        
            $
        

        
            
                sudo dnf update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf install
            
                        
                rubygem-apipie-rails.noarch
            
                    
    
    Copied

2. Uninstall "rubygem-apipie-rails.noarch" package

This guide let you learn how to uninstall rubygem-apipie-rails.noarch on Fedora 34:


    
        
            $
        

        
            
                sudo dnf remove
            
                        
                rubygem-apipie-rails.noarch
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf autoremove
            
                    
    
    Copied

3. Information about the rubygem-apipie-rails.noarch package on Fedora 34

Last metadata expiration check: 1:50:35 ago on Tue Sep 6 08:10:37 2022.
Available Packages
Name : rubygem-apipie-rails
Version : 0.5.18
Release : 3.fc34
Architecture : noarch
Size : 129 k
Source : rubygem-apipie-rails-0.5.18-3.fc34.src.rpm
Repository : updates
Summary : Rails REST API documentation tool
URL : http://github.com/Apipie/apipie-rails
License : MIT and ASL 2.0
Description : Apipie-rails is a DSL and Rails engine for documenting your RESTful API.
: Instead of traditional use of #comments, Apipie lets you describe the code,
: through the code. This brings advantages like:
:
: * No need to learn yet another syntax, you already know Ruby, right?
: * Possibility of reusing the docs for other purposes (such as validation)
: * Easier to extend and maintain (no string parsing involved)
: * Possibility of reusing other sources for documentation purposes (such as
: routes etc.)
:
: The documentation is available from within your app (by default under the
: /apipie path.) In development mode, you can see the changes as you go. It's
: markup language agnostic, and even provides an API for reusing the
: documentation data in JSON.