Fix/fix block registration (#1059)

* fix disable button

* add backend env for restricting registration

* update state management

* add allow_signup to app info

* move allow_signup to backend only

* cleanup docker-compose

* potential darkmode fix

* fix missing variable

* add banner on login page

* use random bools for tests

* fix initial state bug

* fix state reset

docs/docs/documentation/getting-started/installation/backend-config.md

@@ -15,6 +15,7 @@
 | API_PORT      |         9000          | The port exposed by backend API. **Do not change this if you're running in Docker** |
 | API_DOCS      |         True          | Turns on/off access to the API documentation locally.                               |
 | TZ            |          UTC          | Must be set to get correct date/time on the server                                  |
+| ALLOW_SIGNUP  |         true          | Allow user sign-up without token (should match frontend env)                        |
 
 
 
@@ -60,4 +61,4 @@ Changing the webworker settings may cause unforeseen memory leak issues with Mea
 | LDAP_AUTH_ENABLED  |  False  | Authenticate via an external LDAP server in addidion to built-in Mealie auth                                       |
 | LDAP_SERVER_URL    |  None   | LDAP server URL (e.g. ldap://ldap.example.com)                                                                     |
 | LDAP_BIND_TEMPLATE |  None   | Templated DN for users, `{}` will be replaced with the username (e.g. `cn={},dc=example,dc=com`)                   |
-| LDAP_ADMIN_FILTER  |  None   | Optional LDAP filter, which tells Mealie the LDAP user is an admin (e.g. `(memberOf=cn=admins,dc=example,dc=com)`) |
+| LDAP_ADMIN_FILTER  |  None   | Optional LDAP filter, which tells Mealie the LDAP user is an admin (e.g. `(memberOf=cn=admins,dc=example,dc=com)`) |

docs/docs/documentation/getting-started/installation/frontend-config.md

@@ -4,12 +4,11 @@
 
 ### General
 
-| Variables    |        Default         | Description                         |
-| ------------ | :--------------------: | ----------------------------------- |
-| ALLOW_SIGNUP |          true          | Allows anyone to sign-up for Mealie |
-| API_URL      | http://mealie-api:9000 | URL to proxy API requests           |
+| Variables |        Default         | Description               |
+| --------- | :--------------------: | ------------------------- |
+| API_URL   | http://mealie-api:9000 | URL to proxy API requests |
 
-### Themeing 
+### Themeing
 Setting the following environmental variables will change the theme of the frontend. Note that the themes are the same for all users. This is a break-change when migration from v0.x.x -> 1.x.x.
 
 | Variables             | Default | Description                 |

docs/docs/documentation/getting-started/installation/postgres.md

@@ -18,13 +18,12 @@ services:
       - mealie-api
     environment:
     # Set Frontend ENV Variables Here
-      - ALLOW_SIGNUP=true
       - API_URL=http://mealie-api:9000 # (1)
     restart: always
     ports:
       - "9925:3000" # (2)
     volumes:
-      - mealie-data:/app/data/ # (3) 
+      - mealie-data:/app/data/ # (3)
   mealie-api:
     image: hkotel/mealie:api-nightly
     container_name: mealie-api
@@ -34,6 +33,7 @@ services:
       - mealie-data:/app/data/
     environment:
     # Set Backend ENV Variables Here
+      - ALLOW_SIGNUP=true
       - PUID=1000
       - PGID=1000
       - TZ=America/Anchorage
@@ -64,7 +64,7 @@ volumes:
 
 <!-- Updating This? Be Sure to also update the SQLite Annotations -->
 
-1. Whoa whoa whoa, what is this nonsense? The API_URL is the URL the frontend container uses to proxy api requests to the backend server. In this example, the name `mealie-api` resolves to the `mealie-api` container which runs the API server on port 9000. This allows you to access the API without exposing an additional port on the host. 
+1. Whoa whoa whoa, what is this nonsense? The API_URL is the URL the frontend container uses to proxy api requests to the backend server. In this example, the name `mealie-api` resolves to the `mealie-api` container which runs the API server on port 9000. This allows you to access the API without exposing an additional port on the host.
     <br/> <br/> **Note** that both containers must be on the same docker-network for this to work.
 2.  To access the mealie interface you only need to expose port 3000 on the mealie-frontend container. Here we expose port 9925 on the host, feel free to change this to any port you like.
-3.  Mounting the data directory to the frontend is now required to access the images/assets directory. This can be mounted read-only. Internally the frontend containers runs a Caddy proxy server that serves the assets requested to reduce load on the backend API. 
+3.  Mounting the data directory to the frontend is now required to access the images/assets directory. This can be mounted read-only. Internally the frontend containers runs a Caddy proxy server that serves the assets requested to reduce load on the backend API.

docs/docs/documentation/getting-started/installation/sqlite.md

@@ -1,6 +1,6 @@
 # Installing with SQLite
 
-SQLite is a popular, open source, self-contained, zero-configuration database that is the ideal choice for Mealie when you have 1-20 Users. Below is a ready to use docker-compose.yaml file for deploying Mealie on your server. 
+SQLite is a popular, open source, self-contained, zero-configuration database that is the ideal choice for Mealie when you have 1-20 Users. Below is a ready to use docker-compose.yaml file for deploying Mealie on your server.
 
 **For Environmental Variable Configuration See:**
 
@@ -16,7 +16,6 @@ services:
     container_name: mealie-frontend
     environment:
     # Set Frontend ENV Variables Here
-      - ALLOW_SIGNUP=true
       - API_URL=http://mealie-api:9000 # (1)
     restart: always
     ports:
@@ -30,6 +29,7 @@ services:
       - mealie-data:/app/data/
     environment:
     # Set Backend ENV Variables Here
+      - ALLOW_SIGNUP=true
       - PUID=1000
       - PGID=1000
       - TZ=America/Anchorage
@@ -45,7 +45,7 @@ volumes:
 
 <!-- Updating This? Be Sure to also update the Postgres Annotations -->
 
-1. Whoa whoa whoa, what is this nonsense? The API_URL is the URL the frontend container uses to proxy api requests to the backend server. In this example, the name `mealie-api` resolves to the `mealie-api` container which runs the API server on port 9000. This allows you to access the API without exposing an additional port on the host. 
+1. Whoa whoa whoa, what is this nonsense? The API_URL is the URL the frontend container uses to proxy api requests to the backend server. In this example, the name `mealie-api` resolves to the `mealie-api` container which runs the API server on port 9000. This allows you to access the API without exposing an additional port on the host.
     <br/> <br/> **Note** that both containers must be on the same docker-network for this to work.
 2.  To access the mealie interface you only need to expose port 3000 on the mealie-frontend container. Here we expose port 9925 on the host, feel free to change this to any port you like.
-3.  Mounting the data directory to the frontend is now required to access the images/assets directory. This can be mounted read-only. Internally the frontend containers runs a Caddy proxy server that serves the assets requested to reduce load on the backend API. 
+3.  Mounting the data directory to the frontend is now required to access the images/assets directory. This can be mounted read-only. Internally the frontend containers runs a Caddy proxy server that serves the assets requested to reduce load on the backend API.