In part 4 of the tutorial, the field validation doesn't fire up when we hit send with empty username and password fields.

In the tutorial code, there is a typo in SignupActions.js on line 23.
It says
if (error.resposne) {

instead of
if (error.response) {

Because of this CREATE_USER_ERROR is never set and later on in the tutorial, when connecting to the api, sending the form with empty fields results in a 400 Bad Request response.

Nothing is broken at all, but i went ahead and setup a connection to a persistent postgresql database, and wanted to lay out here what i did in case it's of use to anyone.

It's possible that there are better ways to do the steps below, but it works :)

Plus, feel free to use any of this if there are any additional articles in this great series!

Updates to files

Dockerfile

1. install postgres client and server by adding before WORKDIR /app:

# Install postgres client so we can access the db directly from command line (see below)
RUN apk add --update --no-cache postgresql-client

and (note, i had to add gcc for compile reasons)

RUN apk update \
    && apk add postgresql-dev gcc python3-dev musl-dev libffi-dev openssl-dev

docker-compose.yml

1. add this to top of services section, above nginx:

    db:
        image: postgres
        restart: always
        volumes:
            - pgdata:/var/lib/postgresql/data
        environment:
            - POSTGRES_DB=postgres
            - POSTGRES_USER=postgres
            - POSTGRES_PASSWORD=postgres

2. update volumes section at the bottom:

volumes:
    static_volume: {}
    pgdata: {}

3. add this to end of service/backend section:

    depends_on:
        - db

settings.py

updates to django's backend/server/server/settings.py file. add this after the default sqlite3 db is set (change name of db/user/pwd as you wish; just make sure to change it to match in the docker-compose.yml file as noted above):

if not DEBUG:
    DATABASES = {
        'default': {
            'ENGINE': 'django.db.backends.postgresql',
            'NAME': 'postgres',
            'USER': 'postgres',
            'PASSWORD': 'postgres',
            'HOST': 'db',
            'PORT': 5432,
        }
    }

requirements.txt

addition to backend/requirements.txt:

psycopg2-binary>=2.8

Note, you'll likely need to comment this line out for locally. ideally we can add a server check so this doesn't get added locally when using sqlite3 default db.

That's it.

Doing those steps, it auto created the volume first time i launched, and the database connected successfully, and the db persists across sessions, even if i rebuild the docker images.

Working w/ the postgres db directly

This is only useful if you can login to your docker server via ssh and work through the command line.
Once logged into the server via ssh, you do:

1. docker ps to get container id
2. docker exec -it [container_id_here] sh to get into postgres container as an sh shell
3. su postgres to change to the user who owns the db situation
4. psql to take you into psql so you can work with db.

to get out, just type 'exit' a few times.

Conclusion.

I really appreciated this tutorial, one of the most useful and i wanted to help w/ folks interested in persistent db connection.

This repo was a huge help, thanks 🚀 💯

For anyone's reference , I ran into an issue similar to this where the rsa key size argument is too small when generating the dummy certificates to boot up nginx

error:

SSL routines:SSL_CTX_use_certificate:ee key too small

in this command

docker-compose run --rm --entrypoint "\
  openssl req -x509 -nodes -newkey rsa:1024 -days 1\
    -keyout '$path/privkey.pem' \
    -out '$path/fullchain.pem' \
    -subj '/CN=localhost'" certbot

I had to change rsa:1024 to rsa:4096 to get it to work.

Could potentially use the same rsa_key_size variable in the script as well

working with docker-compose-dev.yml but with another ec2 instance and docker-compose giving error

Certbot failed to authenticate some domains (authenticator: webroot). The Certificate Authority reported these problems:
Domain: mydomain.com
Type: unauthorized
Detail: Invalid response from http://mydomain.com/.well-known/acme-challenge/sklMcsF8-vKNJkzKqo95shFDXqdr7uiaOpWDiGspyrs [13.233.108.169]: "<!doctype html><html lang="en"><meta charset="utf-8"/><link rel="icon" href="/favicon.ico"/><meta name="viewport" content="

Domain: www.mydomain.com
Type: unauthorized
Detail: During secondary validation: Invalid response from http://www.mydomain.com/.well-known/acme-challenge/LH-LaBi42ZGOZAeTHycKAEKN670LF5m-ErwbXYzpeNs [13.233.108.169]: "<!doctype html><html lang="en"><meta charset="utf-8"/><link rel="icon" href="/favicon.ico"/><meta name="viewport" content="

Hint: The Certificate Authority failed to download the temporary challenge files created by Certbot. Ensure that the listed domains serve their content from the provided --webroot-path/-w and that files created there can be downloaded from the internet.

Some challenges have failed.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.

Reloading nginx ...

2021/08/04 06:39:21 [emerg] 31#31: cannot load certificate "/etc/letsencrypt/live/mydomain.com/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/mydomain.com/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)
nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/mydomain.com/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/mydomain.com/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)

After running my project the frontend part renders a white blank page with the following errors on the console tab

Dear Piotr Płoński

Thank you very much for your tutorials. Undoubtedly, using this structure can create valuable applications.

After cloning the code and using the docker-compose -f docker-compose-dev.yml build command, I got an error ERROR [build 5/7] RUN npm ci --silent . The problem was solved by changing the code RUN npm ci --silent on line 9 of the Nginx DockeFile to RUN npm install.

If possible, please complete this course and add the unfinished parts to the course, such as resetting the password in frontend and adding the subscription payment mechanism or production ready Email verification.

Finally, I sincerely thank you for sharing your knowledge and helping to develop new software.

Best regards
Hamed Asgari

What is needed to supply is:

• button to remove users' account available for user
• remember the last activity on the user account so that not used accounts will be removed
• automatically sending a message to the user that his account was deleted
• checked box about terms of service and privacy policy before registration account (not pre-checked according to privacy by default rule) and about marketing stuff and
• the automatically remembered date and the content of gave consent! (important)

After running my project the backend part renders a django admin page without the static files like this

OMG! "I have deployed my first app into production." Brother, I would like to thank you for your kindness and brilliant fully comprehensive tutorials. I am sure that it helped many others like me.

When I go back to the comment, the 'init-letsencrypt.sh' certification file should be executable before use. We can make it executable in linux using this command: "sudo chmod +x init-letsencrypt.sh"

Thanks again!

Hello

Maybe I am skipping something but when trying to run docker-compose -f docker-compose-dev.yml up, I get error in my terminal

django_redis_test_backend_1 exited with code 1
backend_1  | standard_init_linux.go:219: exec user process caused: no such file or directory

It also shows something about nginx config files but I am not sure about that.

| /docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration
nginx_1    | /docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d/
backend_1  | standard_init_linux.go:219: exec user process caused: no such file or directory
nginx_1    | /docker-entrypoint.sh: Launching /docker-entrypoint.d/10-listen-on-ipv6-by-default.sh
nginx_1    | 10-listen-on-ipv6-by-default.sh: Getting the checksum of /etc/nginx/conf.d/default.conf
nginx_1    | 10-listen-on-ipv6-by-default.sh: info: /etc/nginx/conf.d/default.conf differs from the packaged version
nginx_1    | /docker-entrypoint.sh: Launching /docker-entrypoint.d/20-envsubst-on-templates.sh
nginx_1    | /docker-entrypoint.sh: Configuration complete; ready for start up

I also cloned repo and tried again, but the error persists.
Could anyone help me figure out what could cause that or is it a general issue?

Thanks for tutorial anyway!

Hi, Just want to know about the deployment settings for the project and how we will deploy frontend and backend separately
like both would be entirely independent of each other and we will be calling apis from frontend.

Messed with this quite a time hence need some guidance.

Hello Team,
I have issue when opening domain in browser.

When entering the sample site https://boilerplate.saasitive.com/ , I select the Dashboard button and arrive at https://boilerplate.saasitive.com/login?next=/dashboard . But when trying to use the back button on both Firefox and Chrome, nothing happens, and a user can't navigate back to main page without modifying the URL.

In https://github.com/saasitive/django-react-boilerplate/blob/main/frontend/src/components/login/LoginActions.js. setAxiosAuthToken() is called 2 times, I believe you can drop one of them.

the login page should route to the dashboard or root if already authenticated.

I am following the tutorial https://saasitive.com/tutorial/docker-compose-django-react-nginx-let-s-encrypt/ step by step but I get this error saying no file found but the file mentioned is correctly in place

The command returned the following error:

django.core.exceptions.ImproperlyConfigured: Cannot import 'accounts'. Check that 'apps.accounts.apps.AccountsConfig.name' is correct.

It can be resolved by going to:
backend/server/server/apps/accounts/apps.py

and changing from

from django.apps import AppConfig

class AccountsConfig(AppConfig):
default_auto_field = 'django.db.models.BigAutoField'
name = 'accounts'

to:

from django.apps import AppConfig

class AccountsConfig(AppConfig):
default_auto_field = 'django.db.models.BigAutoField'
name = 'apps.accounts'

The media files in django (backend) part are not rendering correctly in the frontend, where are the media files stored by default ?
can you please put the modified version of the tutorial with django(backend) media files

After run docker-compose -f docker-compose-dev.yml up --build http://0.0.0.0/ is still not avaible
I don`t have any errors in docker containers

Hey Team :) First thanks a lot for the tutorial,
I am at 4th step and just wanted to tell yoiu that there is a typo error in the tuto https://saasitive.com/tutorial/react-token-based-authentication-django/

in // frontend/src/components/SignupReducer.js there is subimted instead of submitted, i have no idea if this is important but that's it!
Also I had to install history 4.10.1 instead of 5.0.0