b310-digital / mindwendel Goto Github PK

adding ideas after the deadline expired should not be possible. There should be a timer counting down below the brainstorming name.

Clicking the share button will display the link. The share link should be hidden again with a click on copy. However, the link remains until a new idea is added.

Proposal: Change the default port 4000 inside the docker container to use port 80. I dont see any reason why we use 4000 inside the docker container. This should solve the issue.

This issue includes:

• Adjust naming to be consistent
• Changing to another trigger, see https://docs.github.com/en/actions/reference/events-that-trigger-workflows#release
• Add the latest tag to the release
• Have a look at the input for workflow dispatch

• Starting page, bottom uses the german UND
• Slogan makes no sense. Why post its?
• Logo in header is too big
• readme: seeds command is missing a bullet point
• Preloading likes / links twice in braistorming module (get_idea + broadcast)
• Readme: Explain url pre loading in readme as a feature
• screenshot is way too big in file size, loads slowly

It would be helpfull to have an option to hide the settings in a shared brainstorm so other users can't access them.

Add a job that deletes brainstormings after 30 days, to make sure the application is GDPR compliant. Running of the job is optional.

Currently the url preview shows the text and an image inside an idea - but the link of the url is not clickable

warning: unused alias Idea
  lib/mindwendel_web/live/idea_live/index_component.ex:5

warning: clauses with the same name and arity (number of arguments) should be grouped together, "def handle_event/3" was previously defined (lib/mindwendel_web/live/brainstormin

warning: invalid association `ideas` in schema Mindwendel.Brainstormings.Brainstorming: associated schema Mindwendel.Brainstormings.Idea does not exist
  lib/mindwendel/brainstormings/brainstorming.ex:1: Mindwendel.Brainstormings.Brainstorming (module)

warning: clauses with the same name and arity (number of arguments) should be grouped together, "def handle_event/3" was previously defined (lib/mindwendel_web/live/brainstorming_live/show.ex:38)
  lib/mindwendel_web/live/brainstorming_live/show.ex:85

warning: invalid association `users` in schema Mindwendel.Brainstormings.Brainstorming: :join_through schema Mindwendel.Accounts.BrainstormingUser does not exist
  lib/mindwendel/brainstormings/brainstorming.ex:1: Mindwendel.Brainstormings.Brainstorming (module)

warning: invalid association `idea` in schema Mindwendel.Attachments.Link: associated schema Mindwendel.Brainstormings.Idea does not exist
  lib/mindwendel/attachments/link.ex:1: Mindwendel.Attachments.Link (module)

warning: invalid association `likes` in schema Mindwendel.Brainstormings.Idea: associated schema Mindwendel.Brainstormings.Like does not exist
  lib/mindwendel/brainstormings/idea.ex:1: Mindwendel.Brainstormings.Idea (module)

warning: invalid association `brainstormings` in schema Mindwendel.Accounts.User: associated schema Mindwendel.Brainstormings.Brainstorming does not exist
  lib/mindwendel/accounts/user.ex:1: Mindwendel.Accounts.User (module)

• Use [head|tail] instead if ++ to add elements
• Different behaviour: Adding an idea puts it to the tail. But the broadcast adds it to the top.
• Logo should link to starting page
• admin area uses wrong layout, missing some links

For the compose install guide, add a short explanation how to create the db:

docker exec -it mindwendel_db_1 sh
su -- postgres
psql
postgres=# CREATE USER mindwendel WITH PASSWORD 'mindwendel';
postgres=# CREATE DATABASE mindwendel;
postgres=# GRANT ALL PRIVILEGES ON DATABASE mindwendel TO mindwendel;
\q
exit

Add the new env variables:

• DATABASE_SSL: "false"
• MW_DEFAULT_LOCALE: en

The github workflow named on_workflow_dispatch__build_publish_release is broken. The input fo the checkout step is defined in a wrong way.

It was not possible to test this github workflow before as workflow dispatches are not working on non-master branches.

This issue includes:

• Fix github workflow for on_workflow_dispatch__build_publish_release
• Optional: Add labels to improve the Dockerfile

Why? This gives us the possibilit to build a production release anytime we want regardless if the code is released or not.

This issue includes:

• Dockerfile combining development and production using https://docs.docker.com/develop/develop-images/multistage-build
• Refine Dockerfile
• Adjust docker-compose.yml to build only target development, see https://docs.docker.com/develop/develop-images/multistage-build/#stop-at-a-specific-build-stage
• Github Action to build docker image and publish docker image
• Discuss the release flow; when should the docker release be triggered
• Connect docker image to repository
• Adjust README
• Abandon mindwendel-docker project

This issue includes:

• Currently, config/prod.exs is disabled; we need to enable this in order to allow deployment on gigalixir and heroku
• Additionally, the Dockerfile builds the application in MIX_ENV=prod and therefore we need to allow building the application without the required ENV vars.

Silent brainstorming mode means that no new ideas popup in the overview. Everyone is just generating input. Silent brainstorming should be limited to e.g. 3-5 minutes.

The idea overview should just list your own ideas withing the silent brainstorming time window.

This issue includes:

• Ensure that screenshots are taken from an English mindwendel instance

Currently, there is no favicon icon displayed.

Add a random teaser above the idea section: "what would superman do?" etc.

to organize the ideas inside a brainstorming, there should be labels that can be assigned to them.

Easier alternative: Each idea can be assigned to a certain color. I think this could also help with clustering. We would then need a sorting functionality which also sorts each cluster.

When building and starting the mindwendel docker container, the following error is raised while executing the migration.

mindwendel    | ** (Code.LoadError) could not load /app/priv/repo/data_migrations/migrate_idea_labels.exs
mindwendel    |     (elixir 1.11.3) lib/code.ex:1460: Code.find_file/2
mindwendel    |     (elixir 1.11.3) lib/code.ex:924: Code.require_file/2
mindwendel    |     lib/mindwendel-0.1.0/priv/repo/migrations/20210314114416_execute_migrate_idea_labels.exs:2: (module)
mindwendel    |     (stdlib 3.14) erl_eval.erl:680: :erl_eval.do_apply/6

This issue includes:

• Fix the reference to the migration file

Add an export/html page with all ideas via admin area.

HTML might be easier to use instead of csv files on mobile devices

Tapping the hamburger icon on mobile devices opens a transparent menu. It's really hard to read the latest brainstormings.

• maybe release it on dockerhub

Steps to reproduce:

1. New Idea > type something inside the input body and remove it
2. close the modal
3. Background will stay greyisch

1. New Idea > type something inside the input body and remove it
2. save idea
3. results in a broken state, the modal cant be opened anymore

Currently, it is only possible to like an idea - but not to unlike it. This should be possible especially for later features like limited upvotes.

• Add a new env variable DEACTIVATE_TEASERS which defaults to false
• Hide teasers if set to true

This issue includes:

• Follow the guide https://devcenter.heroku.com/articles/heroku-button
• Add an app.json file

When an url is not found, then an error is thrown. This should be caught by dedicated not-found page.

This issue includes:

• Add a 404 error page
• Add a general something went wrong error page

• Add a new css class for the logo, remove inline style width

This issue includes:

• Labels (names / values) are set for each brainstorming individual
• Label names should be editable on the brainstorming show page
• Ensure that sorting by label is still possible
• Migrate current labels to new format

This issue includes:

• Set locale
• Add German language

Currently, basically every idea can be liked. This should be adjustable inside the brainstorming settings, e.g. to 3 likes.

Maybe this css addition would do the trick:

.bi-share-fill:before {
    content: "\f505";
    position: relative;
    bottom: 0.1em;

.bi-gear-fill:before {
    content: "\f3c2";
    position: relative;
    bottom: 0.1em;

This issue includes:

• Set the max_age for Plug.Session

I noticed that our .dockerignore file can be enhanced to ensure that files from the host machine do not interfere with the docker build, e.g. executing mix release on host machine create a _build folder. This folder should be ignored when setting up the build context as this folder is also used in some build stages.

See https://elixirforum.com/t/trivial-elixir-app-release-build-runs-but-docker-runtime-error-from-erlexec/30859/3

This issue includes:

• Enhancing the .dockerignore file