| **Describe the bug** | |
| A clear and concise description of what the bug is. | |
| **To Reproduce** | |
| Steps to reproduce the behavior: | |
| 1. Go to '...' | |
| 2. Click on '....' | |
| 3. Scroll down to '....' | |
| 4. See error |
As prerequisites, you'll need:
We strongly recommend that you have a database and static files backup as this is a huge release. It's the biggest release from the beginning, as we're updating to Rails 6, migrating to Webpacker and ActiveStorage.
To update, follow these steps:
This is a quick hack for having videoconferences support on Decidim. Supported services:
How it works:
config.enable_html_header_snippets on config/initializers/decidim.rb) or as a javascript file on your application (app/assets/javascripts/videoconference.js for instance).
| #!/usr/bin/env bash | |
| # | |
| # Decidim installation script on Ubuntu 18.04 LTS | |
| # It should also work on other Operating Systems that supports docker / docker-compose | |
| # | |
| # This is a BETA and as such you should be aware that this could break your environment (if you have any) | |
| # This will use the docker image from Docker Hub and set-up a docker-compose environment for you to try Decidim | |
| # It'll take 15 minutes depending on your network connection | |
| # | |
| # This is also proposal to merge to upstream, to fix the docker-compose/Dockerfile/README |
As an user, there are moments where I need support for an administrator of the platform. Most of the deployments resolve this by two ways:
The problem is that all this requests for information will be outside the platform, and there are some questions that could be answer by the community itself or that they were already asked (and answered).
The solution proposed would have a dynamic similar to questions-and-answers (Q&A) websites, like StackOverflow, but for the moment we don't want to have votes. The module name could be "decidim-support".
These are multiple feature proposals to have a better compliance with GDPR (General Data Protection Regulation).
With our current architecture we're facing a crossroad, where we need to talk about how could be the best approach to handling all the git repositories and all the problems that we're having right now and the problems to come.
On one hand, this is the picture right now:
Official modules on decidim/decidim
| #!/usr/bin/env bash | |
| # | |
| # Decidim installation script on Ubuntu 16.04 LTS and macos sierra 10.2 | |
| # | |
| # This is a BETA and as such you should be aware that this could break your environment (if you have any) | |
| # This will install rbenv, postgresql, nodejs and install decidim on this directory | |
| # It'll take 15 minutes depending on your network connection | |
| # | |
| set -e |
| $ gem install decidim | |
| Fetching: decidim-api-0.6.5.gem (100%) | |
| Successfully installed decidim-api-0.6.5 | |
| Fetching: decidim-core-0.6.5.gem (100%) | |
| Successfully installed decidim-core-0.6.5 | |
| Fetching: decidim-participatory_processes-0.6.5.gem (100%) | |
| Successfully installed decidim-participatory_processes-0.6.5 | |
| Fetching: decidim-system-0.6.5.gem (100%) | |
| Successfully installed decidim-system-0.6.5 | |
| Fetching: decidim-admin-0.6.5.gem (100%) |
| """ | |
| This fabric file makes setting up and deploying a django application much | |
| easier, but it does make a few assumptions. Namely that you're using Git, | |
| Apache and mod_wsgi and your using Debian or Ubuntu. Also you should have | |
| Django installed on your local machine and SSH installed on both the local | |
| machine and any servers you want to deploy to. | |
| _note that I've used the name project_name throughout this example. Replace | |
| this with whatever your project is called._ |