Bug description
Don´t show table correctly

Expected behavior
A Table view normal

Steps to reproduce the issue:
Crreate a container with large ENV variable

Technical details:

• Portainer version: 1.21.0
• Docker version (managed by Portainer): 18.09.3
• Platform (windows/linux): linux
• Command used to start Portainer (docker run -p 9000:9000 portainer/portainer):

Prerequisites

• Are you running the latest version?
• Are you able to consistently reproduce the issue?
• Did you search the issue queue for existing issue?

Issue Description

The description field is missing in the input schema when you are creating a shop. It's defined in the graphql schema but not in the validation schema. So, if you create a shop with description,

Subject of the issue

If a u

It would be better to use bcrypt, beause its more secure as it's slower (uses more computing cycles).
Your code could also be better:

You wouldn't need salt field in User model, because it's saved into the same field as password does.

For authentication, something like:

var mongoose = require('mongoose'),
  bcrypt = require('bcryptjs');

var userSchema = mongoose.Schema({
  email: String,

We need to design a single Docker container that can run all of the Appwrite services and internal processes using Supervisord. This should be a feature with Appwrite minimum, must-have features (ClamAV disabled, no need for Traefik). This is something we need to allow developers to run Appwrite easily on low-end systems and 1-click deployment services (Raspberry PI, Free hosting tiers, Heroku, Ki

Dockly doesn't display well in a terminal using light colouring.

Let's write a guide on how to tail the pantheon/fpm logs.

I think it is as easy as:

lando logs -s appserver -f

That seems to spit out the PHP errors when I create a syntax error or undefined function in my Pantheon app.

Let's turn it into a guide: https://docs.lando.dev/contrib/guides-intro.html

Implement all functionality of reports module for mobile platforms

Include a script that can generate weekly status reports to dev's leadership. The report should have enough buzzwords to make leadership feel as if progress is being made without providing any specific detail that defines said progress.