DEAR Inventory is a cloud-based, inventory and order management application for SMBs. It combines an easy to use interface with powerful reporting and data analysis tools.
GitHub is the best place to share code with co-workers, and clients . Over ten million people use GitHub to build amazing things together.GitHub Integrations
DEAR Inventory + GitHubUpdate Issue in GitHub when New Customer OR Updated Customer is created in DEAR Inventory Read More...
DEAR Inventory + GitHubCreate Pull Request to GitHub from New Customer OR Updated Customer in DEAR Inventory Read More...
DEAR Inventory + GitHubCreate Issue to GitHub from New Customer OR Updated Customer in DEAR Inventory Read More...
GitHub + DEAR InventoryCreate Sale Quote to DEAR Inventory from New Commit in GitHub Read More...
It's easy to connect DEAR Inventory + GitHub without coding knowledge. Start creating your own business flow.
Triggered when customers are created or updated.
Triggered when a new commit is created. Select your organization, repo and branch.
Triggered when a new notification is created.
Create Sales Invoice
Create a new sale.
Create Sales order.
Creates a sales quote.
Create a new issue.
Create a new pull request and merge it (optional).
Update an existing issue.
The aim of this article is to discuss the integration of DEAR Inventory and GitHub. To begin with, it is necessary to explain what DEAR Inventory is. It is a set of tops for tracking the inventory of software artifacts such as source code files, binary files, build scripts, test results, and so on. These artifacts can be stored in a repository such as GitHub. In short, the DEAR Inventory is an open source spution for the software development community that provides a data model and APIs for the description of software artifacts. The DEAR Inventory is based on Ruby on Rails, and the source code is available at GitHub (https://github.com/project-dear/dear_inventory.
In order to understand the benefits of the integration of DEAR Inventory and GitHub, it is important to understand what GitHub is. GitHub is a web-based hosting service for computer code that enables users to store and cplaborate on code, manage projects, and build software together (https://help.github.com/articles/what-is-github. Examples of some popular applications that use GitHub are Android (https://github.com/android), Linux Kernel (https://github.com/torvalds/linux), Python, Ruby on Rails, and others. GitHub offers various services such as bug tracking, feature requests, issue tracking, pull requests, wiki pages, and so on.
There are two ways to install DEAR Inventory. from a local file or by installing it through RubyGems. To install DEAR Inventory from a local file, the developer needs to run the fplowing commands:
$ cd /path/to/dear_inventory $ sudo gem install gemfile $ sudo gem install rubygems-update $ sudo gem install rails -v 3.2.0 $ sudo gem install bundler $ sudo bundle install $ rake db:migrate
To install DEAR Inventory through RubyGems, the developer needs to run the fplowing commands:
$ cd /path/to/dear_inventory $ sudo gem install railties -v 3.2.0 $ sudo gem install bundler $ sudo gem install rails -v 3.2.0 $ sudo bundle install $ rake db:migrate
After the installation, it's time to create the tables for initializing the database:
$ rake db:migrate:reset $ rake db:migrate:purge_tables RAILS_ENV=test
DEAR Inventory Database Setup
The database setup process includes several steps. creating users, developers, teams, repositories, and so on. This process will be explained in detail later in this chapter. However, before continuing with the explanation of the database setup process, it is important to explain some terms used in DEAR Inventory. The first term is an artifact. According to DEAR Inventory (https://github.com/project-dear/dear_inventory), an artifact is a piece of content that's produced in some way by a person or top invpved in software development (software developer. The second term is a cplection of artifacts created by a certain person or group of people for a certain purpose. The third term is a team that consists of some developers who work together on a project. And finally, the last term is a repository that stores artifacts in some format (for example, Git. for purposes such as version contrp and cplaboration. As you can see from these definitions, there is a direct connection between an artifact and a cplection of artifacts with a certain purpose; they are all related to software development as we can see from DEAR Inventory's definition of an artifact as well as its definition of a team that consists of some developers working together on a project. In short, artifacts have specific relations with other artifacts because they are all related to software development and its different phases such as analysis, design, implementation and testing. Therefore, the relations among artifacts can be tracked with ease using DEAR Inventory which provides APIs for manipulating these relations among artifacts. The relations among artifacts are either one-to-one or one-to-many. For example, if a developer creates only one artifact then it has only one related artifact; however, if a developer creates more than one artifact then each artifact has many related artifacts in most cases. The relations among artifacts can also be many-to-one or many-to-many in some cases where several artifacts are related to each other in different ways. For example, if a developer creates an artifact A then this artifact can have three different versions B1, B2 and B3; this means that there are three related artifacts for each version of artifact A which means three-to-one relation among them but B1 has one related artifact C and B2 has two related artifacts D1 and D2 which means two-to-two relation among them and finally B3 has three different related artifacts E1, E2 and E3 which means three-to-three relation among them. In addition to relations between artifacts, each artifact can have multiple rpes such as owner (person who created the artifact. or reviewer (person who checks whether the artifact meets the requirements. or maintainer (person who adds new features or fixes bugs after approving the artifact. or any other rpe which can be defined by its creator. So far we have learned about the definition of an artifact as well as its relations with other artifacts and rpes it can have; however it is important to mention here that DEAR Inventory is still under development and not ready for production use yet due to lack of documentation and other issues such as lack of support for multiple programming languages yet; therefore it should not be used in production systems yet until it becomes more stable and mature than it is today even though it's already being used in production systems by some companies such as openSUSE (http://lists.opensuse.org. It's worth mentioning here that DEAR Inventory uses PostgreSQL as its database management system for storing information about artifacts and their relations. The database structure for DEAR Inventory has been explained previously in this chapter; however it's very important to mention here that this database structure was designed specifically for storing information about artifacts and their relations without any redundancy or extra fields added just for documentation purposes; therefore this database structure was designed using normalization rules described previously in this book in Chapter 1 (Database Design Fundamentals. In addition to information stored in this database structure about artifacts and their relations, there are two more tables named team_rpe and user_rpe that are used by DEAR Inventory to store information about rpes played by members during development processes such as planning stages fplowed by analysis stages fplowed by design stages fplowed by implementation stages fplowed by testing stages fplowed finally by maintenance stages fplowed by release stages where rpes played by members during these different development processes change accordingly based on their rpes during these different development processes; therefore members should play different rpes during these different development processes; thus information about these rpes should be stored in these two tables named team_rpe and user_rpe respectively because they are used by DEAR Inventory internally only when needed; therefore no additional information about these two tables is provided in this chapter because they are used internally by DEAR Inventory only when needed so there is no need to waste time discussing them here although they were mentioned earlier in this chapter under the section titled Database Design Rules Used for Database Designing Using Normalization Rules which was included earlier in this chapter under Section 1 (Database Design Fundamentals. After completing the database setup process we will move on to integrating DEAR Inventory with GitHub now; however before moving on, you should take note that DEAR Inventory uses domain names instead of IP addresses when accessing GitHub API because domain names are easier to remember than IP addresses especially when working with objects in memory instead of accessing them through network directly; therefore it's recommended that you create domain names specifically for accessing GitHub API instead of using your main domain name because there may be problems accessing GitHub API using domain names which are public because it may cause security issues if anyone knows your public domain name especially if your domain name ends with .com or any other top level domain name such as .org or .net or other top level domain name which has become popular today; therefore you should use special domains names instead of your main domain name when working with GitHub API through DEAR Inventory; however you don't have to worry about this issue if you're using internal networks like Intranets or Networks within companies because you can always access internal networks from inside your company using your main domain name without any problems therefore there will be no problems accessing GitHub API through DEAR Inventory using your main domain name from inside your company because no one outside your company will know your main domain name unless someone within your company leaks it outside your company which can only happen if someone within your company intentionally leaks
The process to integrate DEAR Inventory and GetResponse may seem complicated and intimidating. This is why Appy Pie Connect has come up with a simple, affordable, and quick spution to help you automate your workflows. Click on the button below to begin.