juntagrico / juntagrico-paas

juntagrico

the easy solution for cooperative vegetable growers

juntagrico is a management platform for community gardens and vegetable cooperatives.

It provides the basic functionality like

• subscription management
• extra subscription management
• management of shares
• delivery management
• management of members

Detailed documentation how to install and configure juntagrico can be found here https://juntagrico.readthedocs.io

Demo can be found here https://demo.juntagrico.science/ The username is "admin" and the password is "admin" too. Please do not change the password!

juntagrico-paas's Issues

Limit the number of lines shown from the docker log

Use e.g. container.logs(tail=1000) to limit the number of lines printed from the logs and avoid a timeout.

juntagrico-paas/adminconsole/views.py

Line 177 in 5f3442c

result_text = container.logs()

Check for expired githubkey

The github key may have expired, which will lead to "BadCredentialsException at /ca/repo" when creating a new application.

The validity not just the existence of the key should be checked here.
https://github.com/juntagrico/juntagrico-paas/blob/5f3442c7893a36b9e641fa811bbe063ea59137c6/adminconsole/views_ca.py#L29C14-L29C14

Option for user to backup and restore their database

Minimal:

• A button that creates db dump (keep the last 5)
• up to 5 button to restore from the last 5 dumps that are stored
• up to 5 Buttons to download the last 5 dumps

Nice to have

• A button to upload a dumpfile

Reset import to false

When clicking import app, then returning and instead clicking on create new app, the import flag will still be set to TRUE in the session, leading to an incomplete setup.

Add this at the beginning of create_app:

request.session['import'] = False

juntagrico-paas/adminconsole/views_ca.py

Line 25 in 5f3442c

def create_app(request):

Workaround: Logout and in again before creating the app.

Log may not be available after redeploy

This happens, when waiting for a while (around 15 minutes) after the redeploy and then clicking next

Traceback (most recent call last):
  File "/var/django/adminconsole/venv/lib/python3.8/site-packages/django/core/handlers/exception.py", line 34, in inner
    response = get_response(request)
  File "/var/django/adminconsole/venv/lib/python3.8/site-packages/django/core/handlers/base.py", line 115, in _get_response
    response = self.process_exception_by_middleware(e, request)
  File "/var/django/adminconsole/venv/lib/python3.8/site-packages/django/core/handlers/base.py", line 113, in _get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File "/var/django/adminconsole/adminconsole/decorators.py", line 16, in wrapper
    return view(request, *args, **kwargs)
  File "/var/django/adminconsole/adminconsole/views.py", line 62, in show_log
    texts = [str(eval(b_text), 'utf-8') if b_text.startswith('b') else b_text for b_text in b_texts]
  File "/var/django/adminconsole/adminconsole/views.py", line 62, in <listcomp>
    texts = [str(eval(b_text), 'utf-8') if b_text.startswith('b') else b_text for b_text in b_texts]

Exception Type: SyntaxError at /showlog/33/
Exception Value: invalid syntax (<string>, line 1)

Issue and workaround when using ManifestStaticFileStorage

When using

STATICFILES_STORAGE = 'django.contrib.staticfiles.storage.ManifestStaticFilesStorage'

After redeploying the project with changed static files, the page does not load (500).
This can be fixed by saving the settings (unchanged) after such a redeploy. I assume the settings saving does something, that should be done after each redeploy.

Select branch or commit to deploy

This would be helpful to easily move back to a previous version, when one has problems with an update and can't fix it quickly.

Probably somewhere here this would go.

juntagrico-paas/adminconsole/management/commands/rebuild_docker.py

Line 26 in da88b87

proc = subprocess.run(['git', 'pull'], stdout = subprocess.PIPE, cwd=cdir)