[Feature] Main flux on home page

.codeclimate.yml

@@ -0,0 +1,18 @@
+engines:
+  duplication:
+    enabled: true
+    config:
+      languages:
+      - ruby
+  fixme:
+    enabled: true
+  rubocop:
+    enabled: true
+ratings:
+  paths:
+  - "SIGS/**.rb"
+  - "SIGS/"
+exclude_paths:
+- config/
+- spec/
+- apps/assets/

.github/CONTRIBUTING.md

@@ -0,0 +1,76 @@
+# Contributing to SIGS
+
+If you would like to contribute to the project, it may be a good idea to start with the [README](https://github.com/GCES-2018-2/SIGS-GCES/blob/master/README.md) to know more about us.
+Another important document that should be read is the [Code of Conduct]().
+
+Thanks for contributing! :tada::+1: Your help will be received with great gratitude!
+
+# How can I contribute?
+
+## Reporting a Bug
+
+* This project follows a [_Issue_](https://github.com/GCES-2018-2/SIGS-GCES/blob/master/.github/ISSUE_TEMPLATE.md) pattern. So if you find a bug, make sure it is not in one of our [_Issues_](https://github.com/GCES-2018-2/SIGS-GCES/issues). Bugs should be marked with _label (tag)_ __bug__.
+
+* If the bug found is not in the _Issues_, just open a [_New Issue_](https://github.com/GCES-2018-2/SIGS-GCES/issues/new).
+
+## Adding and/or modifying some functionality
+
+* First, check that there is no [_Issue_](https://github.com/GCES-2018-2/SIGS-GCES/issues) regarding this modification and/or addition.
+
+* If it does not exist, create a [_New Issue_](https://github.com/GCES-2018-2/SIGS-GCES/issues/new). Give a meaningful title to it, put a description and at least a _label_.
+
+* Changes must be submitted through [_Pull Requests_](https://github.com/GCES-2018-2/SIGS-GCES/compare). You can find more about this in the [_Pull Requests Template_](https://github.com/GCES-2018-2/SIGS-GCES/blob/master/.github/PULL_REQUEST_TEMPLATE.md).
+
+# Commits Pattern
+
+## For standardization we recommend the community to follow our _commit_ style:
+
+* _Commits_ must all be in __English__;
+
+* It should contain a short and objective title of what was done in that _commit_;
+
+* After this title, the commit should describe, with a little more detail, all the activities performed;
+
+* If you are working with an associate, sign on your _commits_ with your partners.
+
+__Example:__
+
+    Creating project community files (Shot and objective title)
+
+    Adds project license (Description of one of the activities)
+
+    Adds project code of conduct file
+
+    Adds project contributing file
+
+    Adds project issue template file
+
+    Adds projects pull request file
+
+    Co-authored-by: John Doe <johndoe@mail.com> (Partnership signarute)
+
+# Branch Policy
+
+With the goal of maintaining the completeness and reliability of the project code, the use of branch policy was proposed. This Branches Policy should guide developers in organizing their contributions to the repository.
+
+__Note__: The _branchs_ policy was designed to work in conjunction with the _git flow_ tool, its documentation and more information can be accessed [here](https://github.com/nvie/gitflow).
+
+* __`master`__ - Main branch of the repository where only consolidated and tested software integration will be allowed. This branch will be exclusively for the delivery of realeases, that is, a greater set of functionalities that integrate the software. Here will be the _**stable**_ version of the software.
+
+* __`develop`__ - Branch for the integration of new functionalities, where it will be allowed to deliver the features developed and that are in an advanced stage of completeness. It will be the base branch for the beginning of the development of the features and of the correction of bugs. The releases will also be merged here.
+
+* __`feature/<feature-name>`__ - Branch used for the development of new features. If the feature has been proposed by a _issue_ of the repository and accepted, the name should contain the _issue_ number.
+e.g.: `feature/1-<new-feature-name>` (whereas feature has been requested in _issue_ #1)
+
+* __`bugfix/<bug-name>`__ - Branch used to fix low/medium urgency bugs that are not present in the __master__ branch. If the bug has been reported by a _issue_ from the repository the name should contain the _issue_ number.
+e.g.: `bugfix/1-<bugfix-name>` (whereas feature has been requested in _issue_ #1)
+
+* __`hotfix/<bug-name>`__ - Branch used to fix high-urgency bugs that are present in the __master__ branch. If the bug has been reported by a _issue_ from the repository the name should contain the _issue_ number.
+e.g.: `hotfix/1-<hotfix-name>` (whereas feature has been requested in _issue_ #1)
+
+* __`release/<release-version>`__ - Branch where final adjustments/build will be made prior to delivery of a software product release. Branch name will be the version of the release to be delivered.
+
+* __`support/<theme-or-kind>`__ - Branch where support tasks related to the software will be performed, such as documentation development, configuration management corrections, and so on.
+
+* __`improvement/<improvement-name>`__ - Branch used for the improvement of functionalities or documentation project . If the improvement has been proposed by a _issue_ of the repository, the name should contain the _issue_ number.
+e.g.: `improvement/1-<improvement-name>` (whereas feature has been requested in _issue_ #1)

.github/ISSUE_TEMPLATE.md

@@ -1,16 +1,47 @@
-## Descrição do Problema
-
-
-## Comportamento Esperado
-
-
-## Comportamento Atual 
-
-
-## Passos Para Reproduzir o Problema
-
-  1.
-  2.
+## Problem description
+<!--- Provide a general summary of _issue_ in the above title -->
+<!--- Forneça um resumo geral da _issue_ no título acima -->
+
+## Expected Behavior
+<!--- If you are describing a _bug_, tell us what should happen. -->
+<!--- If you are suggesting a change/improvement, tell us how it should work or should be. -->
+<!--- Se você está descrevendo um _bug_, conte-nos o que deveria acontecer. -->
+<!--- Se você está sugerindo uma mudança/melhoria, conte-nos como deve funcionar ou como deve ser. -->
+
+## Possible Solution
+<!--- Not required, but suggest a possible fix/reason for the bug -->
+<!--- or ideas on how to implement the addition/change. -->
+<!--- Não é obrigatório, mas sugira uma possível correção/razão para o bug -->
+<!--- ou ideias de como implementar a adição/mudança. -->
+
+## Step to Reproduce (for _bugs_)
+<!--- Forneça um link para um exemplo, ou um conjunto de passos inequívocos -->
+<!--- para reproduzir esse _bug_. Inclua código para reproduzir, se relevante. -->
+<!--- Provide a link to an example, or a set of unambiguous steps -->
+<!--- to reproduce this _bug_. Include code to reproduce, if relevant. -->
+
+1.
+2.
+3.
+4.
 
 
 ## Screenshots
+<!--- If relevant, add some screenshots or print screens of the _bug_ -->
+<!--- or some prototype for the new addintion/change. -->
+<!--- Se relevante, adicione alguns _screenshots_ ou _print screens_ do _bug_ -->
+<!--- ou algum protótipo para a nova adição/mudança. -->
+
+## Context
+<!--- How does this problem affect you? What are you trying to accomplish? -->
+<!--- Providing context helps us find a solution that is most useful in the real world -->
+<!--- Como esse problema o afeta? O que você está tentando realizar? -->
+<!--- Fornecer o contexto nos ajuda a encontrar uma solução que seja mais útil no mundo real -->
+
+## Your Environment
+<!--- Include relevant details about the environment in which you witnessed/experienced the bug. -->
+<!--- Inclua detalhes relevantes sobre o ambiente em que você presenciou/experienciou o bug. -->
+* Software Version (_Release_):
+* Name and version of the browser:
+* Name and version of the Operating System (desktop or mobile):
+* Link to your project (in case of fork of this project):

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,30 +1,48 @@
-# Porposed Changes
-
-Make a brief outline of your changes. Make sure you have mentioned the related issue (use a hyperlink).
-
-# Type of Changes
-
-What type of change this Pull Request brings to SIGS? Put an **x** in the boxes that apply
+## Proposed Changes
+<!--- Make a brief outline of your changes. -->
+<!--- Faça um breve resumo de suas mudanças. -->
+
+## _Issue_ Related
+<!--- This project only accepts _pull requests_ related to opened _issues_. -->
+<!--- If you are suggesting a new _feature_ or change, please discuss in a _issue_ before. -->
+<!--- If you are correcting a _bug_, there should be a _issue_ describing it with steps to reproduce. -->
+<!--- Please add the link to _issue_ here: -->
+<!--- Este projeto apenas aceita _pull requests_ relacionadas à _issues_ abertas. -->
+<!--- Se está sugerindo uma nova _feature_ ou mudança, por favor discuta em uma _issue_ antes. -->
+<!--- Se está corrigindo um _bug_, deve haver uma _issue_ descrevendo-o com passos para reproduzir. -->
+<!--- Por favor, adicione o link para a _issue_ aqui: -->
+
+## Type of Changes
+<!--- What type of change this Pull Request brings to SIGS? Put an **x** in the boxes that apply. -->
+<!--- Que tipo de mudança o Pull Request traz para o SIGS? Coloque um **x** nas caixas que se aplicam. -->
 
 - [ ] New backend feature or update.
 - [ ] New frontend feature or update.
 - [ ] Bug fix.
 - [ ] Another change (what was the change?).
 
-# Checklist 
+## How Was This Tested?
+<!--- Please describe in detail how you tested your changes. -->
+<!--- Include details of your test setup and the tests you ran -->
+<!--- to see how your change affects other areas of the code, etc. -->
+<!--- Por favor, descreva detalhadamente como você testou suas mudanças. -->
+<!--- Inclua detalhes do seu ambiente de teste e os testes que você executou -->
+<!--- para ver como a sua alteração afeta outras áreas do código, etc. -->
+
+## Checklist
+<!--- Put an **x** in the boxes that apply. If you're confused about any of the following topics, ask us. We're here to help you! -->
+<!--- Coloque um **x** nas caixas que se aplicam. Se você está confuso sobre qualquer um dos tópicos a seguir, pergunte-nos. Estamos aqui para ajudar você! -->
 
-Put an **x** in the boxes that apply. If you're confused about any of the following topics, ask us. We're here to help you!
-
 - [ ] This Pull Request has a significant name.
 - [ ] The commits follow the [[commits policy]].
 - [ ] The build is okay (tests, code climate).
 - [ ] This Pull Request mentions a related issue.
 - [ ] The change was necessary to the progress of the project.
 
-# Screenshots
-
-If necessary, use screenshots to show us your changes on the frontend.
-
-# Further comments
+## Screenshots
+<!--- If necessary, use screenshots to show us your changes on the frontend. -->
+<!--- Se necessário, use capturas de tela para nos mostrar suas alterações no frontend. -->
 
-If you have something more to tell us (questions, explanations, etc) write them down here. We'll answer you as soon as possible.
+## Further comments
+<!--- If you have something more to tell us (questions, explanations, etc) write them down here. We'll answer you as soon as possible. -->
+<!--- Se você tem algo mais para nos dizer (perguntas, explicações, etc) escrava-os aqui. Nós lhe responderemos o mais breve possível. -->

.gitignore

@@ -15,17 +15,26 @@
 /log/*
 /tmp/*
 /SIGS/public/reports
+/SGIS/public/uploads
 !/log/.keep
 !/tmp/.keep
 !/SIGS/public/reports/.keep
 
 # Ignore Byebug command history file.
 .byebug_history
 
+# Ignore the coverage folder
+SIGS/coverage/*
+SIGS/coverage/
+
+# Other files
 .vagrant
 .gitignore
-SIGS/coverage
 SIGS/script/dbScript
+SIGS/.generators
+SIGS/.rakeTasks
+SIGS/db/schema.rb
 
-# Ignore script generated file
-/SIGS/start-dev.sh
+# Ignore IDE files
+.idea/
+.DS_Store

.travis.yml

@@ -1,32 +1,47 @@
+sudo: true
+env:
+  global:
+    - CC_TEST_REPORTER_ID=690d2b62e0c4304ed271341a2ed1786a41629b5a50c4c4fc4be8fd3ee6a99f33
 language: ruby
 rvm:
-- 2.3.1
+  - 2.5.1
 services:
-- mysql
+  - mysql
+  - docker
+addons:
+  ssh_known_hosts:
+    - 68.183.18.1
 before_script:
-- cp SIGS/config/database.yml.travis SIGS/config/database.yml
-- mysql -e 'create database myapp_test;' -uroot
-notifications:
-  slack: sigs-gces:IISF1PsHHYEWEMomYPJ7KWsi
+  - cp SIGS/config/database.yml.travis SIGS/config/database.yml
+  - mysql -e 'create database myapp_test;' -u root
+  - curl -L https://codeclimate.com/downloads/test-reporter/test-reporter-latest-linux-amd64 > ./cc-test-reporter
+  - chmod +x ./cc-test-reporter
+  - ./cc-test-reporter before-build
 branches:
   only:
   - "/.*/"
 script:
-- cd SIGS
-- bundle install
-- bundle exec rake db:load_config
-- bundle exec rake db:create
-- bundle exec rake db:migrate
-- rake cucumber
-- bundle exec rspec
-- rubocop
-after_sucess:
-- coveralls push
+  - echo $DOCKERHUB_PASS | docker login -u $DOCKERHUB_USER --password-stdin
+  - cd SIGS
+  - bundle install
+  - bundle exec rake db:load_config
+  - bundle exec rake db:create
+  - bundle exec rake db:migrate
+  - rake cucumber
+  - bundle exec rspec
+  - rubocop
+after_script:
+  - ../cc-test-reporter after-build --exit-code $TRAVIS_TEST_RESULT
 deploy:
-  provider: heroku
-  app: sigsunb
-  api_key:
-    secure: Yxxp3xzQ3Vcktw4OOS94+TQkOaSS5fK1nTrNBbInYcqkwZGMfM3kXo0JbrrcJtRolqvr9DETzbC8o8ZJjrdYR51J7mlgaoBEsHNCpuTdzSUXmSBGuHy/8OQgOwebxqJXjx75l3BOmvaMgt+PjNrVCRSDPr9L2qStqBTF94omBz8TXGgfAfcQgVlhp5Obb13pW60ND3dRSI9tWIfs4eBVa0InMjTEOirV2xZ894sh97pVdnxyk4hLItkcWZ/p8UH3mQU4PPhpn157m2eB7ApLW4vtUxmgv3PO742F8ow0U6ZhO0bkBDjdGV80GcP0CsAdx1C6V4P6X/TC862j0nyJPW6JVqiO8t5xBs74l9vn+7a8C2wB3mcWgAxVF6gqQOBPO0lV5Jk6PZSuQyFx3zrJtvVFA8ZV/oaJBNAJsyY6PMvAXcrSfC2O8xCBmKztCC63iGWxVQ2mMKFCy2leqGiB4ZdOjnwBt6WNcNe6PN701y3Xs+6kTIrxTCfKVN6nEemOg/xz5tvPDJyPl7eC5bjPfU7HASIWCNVn/3gzk23FTozqRunbXW6quqpYPNw9P6cSb6VK8h1IAjYFd/2F8TIkHlXwroXuPKT3tdxQZs6Z/70MMRBt28bZr/795uu7CSvrC0wL6yPpPh4V+FrMnvuFQ/pom4NZ7dZyRapjt/OLe2g=
-  on:
-    branch: master
-  run: "rails db:seed"
+  # Deploy develop on the staging environment
+  - provider: script
+    script: bash ../script/staging-deploy.sh
+    skip_cleanup: true
+    on:
+      branch: develop
+  # Deploy master on the production environment
+  - provider: script
+    script: bash ../script/production-deploy.sh
+    skip_cleanup: true
+    on:
+      branch: master