Skip to content

bug(installation): nano does not automatically get installed, results in not opening .env #1141

@AnonymousWP

Description

@AnonymousWP

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

When using a minimal Linux installation and running install.sh, you're being asked whether you made changes to the .env file or not. When selecting no and nano isn't installed, nothing will happen.

read -p "Are you sure, you made changes to .env file (y/n)? " answer
case ${answer:0:1} in
    y|Y|yes|YES|Yes )
      echo "Continiuing Installation!"
    ;;
    * )
      nano .env
    ;;
esac

Expected Behavior

Install nano in case it's not installed.

Steps To Reproduce

  1. Minimal installation Linux
  2. Run install.sh
  3. When being asked about whether you modified the .env file, answer n
  4. Notice how the file can't be opened because nano isn't installed on a clean installation

Environment

- reNgine: 2.0.2
- OS: Ubuntu 22.04.3
- Python: Not applicable
- Docker Engine: 24.0.7
- Docker Compose: 2.21.0
- Browser: Not applicable

Anything else?

image

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions