flyve-mdm/demo-mode

Demo mode for Flyve MDM

demo-mode's Issues

Move Wiki articles to project site

Hi, @Naylin15

Could you move this article to the Wiki in the project site?

https://github.com/flyve-mdm/flyve-mdm-glpi-demo/wiki/Self_create_an_user_account

Thank you.

An in-range update of standard-version is breaking the build 🚨

Version 4.4.0 of standard-version was just published.

Branch	Build failing 🚨
Dependency	standard-version
Current Version	4.3.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

standard-version is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

---

Commits

The new version differs by 8 commits.

• e5c99f6 chore(release): 4.4.0
• 04c68a8 chore: npm audit (#244)
• ba4e7f6 feat: add prerelease lifecycle script hook (closes #217) (#234)
• b4ed4f9 fix: show full tag name in checkpoint (#241)
• fbfdf5e doc : added an example of a postcommit hook (#232)
• 371d992 feat: manifest.json support (#236)
• 6dac27b docs: add title to LICENSE.txt (#238)
• a56c7ac fix: use tagPrefix in CHANGELOG lifecycle step (#243)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Code of Conduct

Hi, @Naylin15

Could you split the code of conduct from the contributing guidelines?

Thank you.

Write a welcome article

Write a welcome article for the page, this first article should give a brief introduction to the product and serve as an entry point for for new users. The idea is to be able to use this for promotion.

Said article should be written in Markdown and be published in the branch of gh-pages within the folder "_post"

Steps to follow for publication:

1. Enter http://prose.io/
2. Select the Flyve MDM organization
3. Enter in repository where you want to publish the article
4. Change to the branch gh-pages
5. Click on the "NEW FILE" button
6. Write your article
7. Save your work

Coverage for project site

Observed Results:

The Coverage information is not displayed on the project site

Expected behavior:

To display this information on the development section on the project site

Code documentation for project site

Observed Results:

The code documentation is not displayed on the project site

Expected behavior:

To display this information

License Header

Hi, @btry

Please, use this header for the copyright information.

#
#  LICENSE
#
#  This file is part of Flyve MDM Demo Plugin for GLPI,
#  a subproject of Flyve MDM. 
#
#  Flyve MDM Demo Plugin for GLPI is free software: you can redistribute it and/or
#  modify it under the terms of the GNU General Public License
#  as published by the Free Software Foundation; either version 3
#  of the License, or (at your option) any later version.
#
#  Flyve MDM Demo Plugin for GLPI is distributed in the hope that it will be useful,
#  but WITHOUT ANY WARRANTY; without even the implied warranty of
#  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
#  GNU General Public License for more details.
#  --------------------------------------------------------------------
#  @author    Thierry Bugier - <[email protected]>
#  @copyright (C) 2017 Teclib' and contributors.
#  @license   AGPLv3 https://www.gnu.org/licenses/agpl-3.0.html
#  @link      https://github.com/flyve-mdm/flyve-mdm-glpi-demo
#  @link      https://www.flyve-mdm.com
#  --------------------------------------------------------------------

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

How-tos and development documentation

Hi, @Naylin15

Change the name "Wiki" to "How-tos" and add these articles; and add the sub menu items to the Development section. If these pages does not exist, please, create an issue and request it. 👍

How-tos

• How to install
• How to use
• Use Cases
• How it works
• How to contribute
• How to Translate

Development

• Code documentation
• Code coverage
• Test report

Test Report for project site

Observed Results:

The Test report information is not displayed on the project site

Expected behavior:

To display this information on the development section

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

Create project page

Create gh-pages as requested in this issue: flyve-mdm/flyve-mdm.github.io#13

Not validated account can login

Reported on Telegram, but raising this known problem :

If a user self creates his account, he can login without validating it, despite he does not has any access, even READ access to objects.

The user reported he needs to use an other browser to finish the validation procedure because he cannot close his session.

We may check if we can forcefully close a session when a user is not validated yet. Not perfect, but somewhat better than opening a session with a lot of access denied messages.

Requirements problem

I'm submitting a...

• Regression (a behavior that used to work and stopped working in a new release)
• Bug report
• Feature request
• Documentation issue or request
• Support request => Please do not submit support request here, instead see https://github.com/flyve-mdm/demo-mode/blob/develop/CONTRIBUTING.md#questions-or-doubts

Current behavior

After running composer install --no-dev it shows the problem "Your requirements could not be resolved to an installable set of packages."

Expected behavior

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

Environment

Demo Plugin version: 1.0.0-dev
GLPI version: 9.2.1
FusionInventory version: 9.2-1.0

Lost password feature return a bad request status

Hi, @btry
I got always an error when I try to recovery my password.

Reference:
flyve-mdm/web-mdm-dashboard#665

Create release

Hi, @btry

Could you create releases of the library

Thank you.

Compatibility matrix

Observed Results:

It is required to add the compatibility of the Web Dashboard with GLPI and Demo plugin

Expected behavior:

The compatibility between Dashboard, Demo and GLPI in the readme and web site documentation

Wrong error message for the captcha validation

Hi, @btry

I got this error:
["ERROR_GLPI_ADD","Turing test failed"]

Use tools package from glpi-project

see here
https://packagist.org/packages/glpi-project/tools