cordelya/axemoor-bootstrap

axemoor-bootstrap's Issues

Pause at end of script (ubuntu and raspbian -init.sh scripts)

Needs this:
$ read -rsp $'Press any key to continue...\n' -n1 key

Raspbian

needs a separate init file due to major differences in install procedure

see here: https://www.tomshardware.com/news/raspberry-pi-web-server,40174.html

Enhancement: new script to init new webdev

A script that prompts for the name of a new project and creates a new www folder, virtual host .conf file, and inits a new git repo in the new folder.
Creates a new readme document.
Instructs user to create a new repo on gh with n filename and waits for user input to continue (ie go make an empty repo named foo on github. When you are done, return to the terminal and press the enter key.)
Sets correct github remote connection for SSH, asks which key to associate with it if you have more than one, tests the SSH connection to github.
Adds the readme file, silently makes first commit, and pushes the first commit up to gh.

Raspbian init script

Selected error messages and notes:

E: Unable to locate package apache2 git systemctl atom
(this is because Raspbian in default state doesn't know where to find atom, and it keeps all the rest of the apps from being installed. Maybe let's drop it for now.)

Synchronizing state of ssh.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable ssh

Done installing Apache2

Apache config starting now
touch: cannot touch '/etc/apache2/sites-available/axemoor.net.conf': No such file or directory
...
unable to write to axemoor.net.conf due to non-existent file

sudo: a2ensite: command not found
sudo: a2dissite: command not found
Attempting to restart Apache. Hang on.
Failed to restart apache2.service: Unit apache2.service not found.
Done configuring Apache. Now installing additional software.

MariaDB setup OK
Make the MariaDB setup advice red for viz.
php-mysql setup OK
Failed to restart apache2.service: Unit apache2.service not found.
...
fatal: destination path '.' already exists and is not an empty directory.
mkdir: cannot create directory ‘/home/pi/help’: File exists
fatal: destination path '/home/pi/help' already exists and is not an empty directory.
chmod: cannot access 'axemoor.sh': No such file or directory

TODO list for the help system

• a more verbose explanation of the setup process to facilitate troubleshooting in case a step in the init process didn't take. Have them work backwards
• git workflow for Axemoor
• a brief introduction to man pages (because we're anticipating users who have never used the Linux CLI before)

init.sh reboot and resume

Future enhancement: fancy footwork inspired by this guide:

https://medium.com/@adikari/resume-bash-script-after-reboot-6fc0371491c8