🗂 Kanban-style project & personal management tool for Nextcloud, similar to Trello
Перейти к файлу
Nextcloud bot b1f7c623a1
Fix(l10n): Update translations from Transifex
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
2025-01-28 00:41:14 +00:00
.devcontainer devcontainer(image): Fix package path 2025-01-10 18:24:10 +01:00
.github feat(deps): Add Nextcloud 32 support on main 2025-01-23 10:57:25 +01:00
.tx [tx-robot] Update transifex configuration 2022-10-01 02:24:14 +00:00
LICENSES chore: Add missing MIT license 2024-05-09 09:35:28 +02:00
appinfo feat(deps): Add Nextcloud 32 support on main 2025-01-23 10:57:25 +01:00
css fix: design review issues 2024-07-17 18:51:46 +02:00
cypress ci: Test for separate extension 2025-01-23 09:28:09 +01:00
docs Merge pull request #3430 from bahuma20/2797-clone-cards 2025-01-02 17:08:14 +01:00
img fix(icon): add height/width for iOS 2024-05-07 15:51:49 +02:00
l10n Fix(l10n): Update translations from Transifex 2025-01-28 00:41:14 +00:00
lib fix: Skip individual board caches when listing all boards 2025-01-14 23:19:38 +01:00
src fix: Properly show attachment extension 2025-01-23 09:28:09 +01:00
templates style: Fix php-cs issues 2024-12-17 09:22:00 +01:00
tests fix: Skip individual board caches when listing all boards 2025-01-14 23:19:38 +01:00
.codecov.yml chore: Add SPDX header 2024-05-07 15:51:49 +02:00
.editorconfig
.eslintignore chore: Add SPDX header 2024-05-07 15:51:49 +02:00
.eslintrc.js Export Board 2022-12-30 12:56:06 +01:00
.gitignore add cypress auto generated videos to gitignore 2022-12-30 14:43:13 +01:00
.nextcloudignore fix: clean up release 2024-11-19 20:03:00 +01:00
.php-cs-fixer.dist.php
AUTHORS.md chore: Add SPDX header 2024-05-07 15:51:49 +02:00
CHANGELOG.md release 1.15.0-beta.1 2025-01-10 17:11:10 +01:00
LICENSE
Makefile chore: Add SPDX header 2024-05-07 15:51:49 +02:00
README.md Remove old project from README 2025-01-13 11:43:56 +00:00
REUSE.toml chore: Migrate REUSE to TOML format 2024-07-08 20:55:59 +02:00
SECURITY.md chore: Add SPDX header 2024-05-07 15:51:49 +02:00
babel.config.js
composer.json chore: Bump php version requirement for composer to 8.1 2024-12-17 08:42:05 +01:00
composer.lock chore(dev-deps): Bump nextcloud/ocp package 2025-01-12 03:03:26 +00:00
cypress.config.js test(cypress): Move to @nextcloud/cypress 2022-12-30 15:42:33 +01:00
krankerl.toml
mkdocs.yml chore: Add SPDX header 2024-05-07 15:51:49 +02:00
package-lock.json feat(deps): Add Nextcloud 32 support on main 2025-01-23 10:57:25 +01:00
package.json feat(deps): Add Nextcloud 32 support on main 2025-01-23 10:57:25 +01:00
psalm.xml chore(composer): Update and cleanup composer dependencies 2023-07-20 11:42:19 +02:00
relativeci.config.js
stylelint.config.js
webpack.js chore(webpack): Move to shared code for entrypoints and use webpack serve public path 2023-05-17 09:53:50 +02:00

README.md

Deck

Build Status CodeCov Codacy Badge Scrutinizer Code Quality #nextcloud-deck REUSE status

Deck is a kanban style organization tool aimed at personal planning and project organization for teams integrated with Nextcloud.

  • Add your tasks to cards and put them in order
  • Write down additional notes in markdown
  • Assign labels for even better organization
  • Share with your team, friends or family
  • Integrates with the Circles app!
  • Attach files and embed them in your markdown description
  • Discuss with your team using comments
  • Keep track of changes in the activity stream
  • Get your project organized

Deck - Manage cards on your board

Mobile apps

3rd-Party Integrations

  • trello-to-deck - Migrates cards from Trello
  • mail2deck - Provides an "email in" solution
  • A-deck - Chrome Extension that allows to create new card in selected stack based on current tab
  • QOwnNotes - Quickly creates cards and links to them in Markdown notes

Installation/Update

The app can be installed through the app store within Nextcloud. You can also download the latest release from the release page.

Performance limitations

Deck is not yet ready for intensive usage. A lot of database queries are generated when the number of boards, cards and attachments is high. For example, a user having access to 13 boards, with each board having on average 100 cards, and each card having on average 5 attachments, would generate 6500 database queries when doing the file related queries which would increase the page loading time significantly.

Improvements on Nextcloud server and Deck itself will improve the situation.

Developing

There are multiple ways to develop on Deck. As you will need a Nextcloud server running, the individual options are described below.

General build instructions

General build instructions for the app itself are the same for all options.

To build you will need to have Node.js and Composer installed.

  • Install PHP dependencies: composer install --no-dev
  • Install JS dependencies: npm ci
  • Build JavaScript for the frontend
    • Development build npm run dev
    • Watch for changes npm run watch
    • Production build npm run build

Faster frontend developing with HMR

You can enable HMR (Hot module replacement) to avoid page reloads when working on the frontend:

  1. ☑️ Install and enable hmr_enabler app
  2. 🏁 Run npm run serve
  3. 🌍 Open the normal Nextcloud server URL (not the URL given by above command)

GitHub Codespaces / VS Code devcontainer

  • Open code spaces or the repository in VS Code to start the dev container
  • The container will automatically install all dependencies and build the app
  • Nextcloud will be installed from the master development branch and be available on a port exposed by the container

Docker: Simple app development container

  • Fork the app
  • Clone the repository: git clone https://github.com/nextcloud/deck.git
  • Go into deck directory: cd deck
  • Build the app as described in the general build instructions
  • Run Nextcloud development container and mount the apps source code into it
docker run --rm \
    -p 8080:80 \
    -v $PWD:/var/www/html/apps-extra/deck \
    ghcr.io/juliushaertl/nextcloud-dev-php81:latest

Full Nextcloud development environment

You need to setup a development environment of the current Nextcloud version. You can also alternatively install & run the nextcloud docker container. After the finished installation, you can clone the deck project directly in the /[nextcloud-docker-dev-dir]/workspace/server/apps/ folder.

Running tests

You can use the provided Makefile to run all tests by using:

make test

Running behat integration tests

Within tests/integration/ run composer install and then choose one of the two options:

  • Run tests with a local php server: bash run.sh
  • Run against an existing Nextcloud installation: BEHAT_SERVER_URL=http://nextcloud.local ./vendor/bin/behat --colors features/decks.feature

Documentation

The documentation for our REST API can be found at https://deck.readthedocs.io/en/latest/API/

Contribution Guidelines

Please read the Code of Conduct. This document offers some guidance to ensure Nextcloud participants can cooperate effectively in a positive and inspiring atmosphere, and to explain how together we can strengthen and support each other.

For more information please review the guidelines for contributing to this repository.

Apply a license

All contributions to this repository are considered to be licensed under the GNU AGPLv3 or any later version.

Contributors to the Deck app retain their copyright. Therefore we recommend to add following line to the header of a file, if you changed it substantially:

@copyright Copyright (c) <year>, <your name> (<your email address>)

For further information on how to add or update the license header correctly please have a look at our licensing HowTo.

Sign your work

We use the Developer Certificate of Origin (DCO) as a additional safeguard for the Nextcloud project. This is a well established and widely used mechanism to assure contributors have confirmed their right to license their contribution under the project's license. Please read developer-certificate-of-origin. If you can certify it, then just add a line to every git commit message:

  Signed-off-by: Random J Developer <random@developer.example.org>

Use your real name (sorry, no pseudonyms or anonymous contributions). If you set your user.name and user.email git configs, you can sign your commit automatically with git commit -s. You can also use git aliases like git config --global alias.ci 'commit -s'. Now you can commit with git ci and the commit will be signed.