This repository contains a "starter" project for web application development in JavaScript. This includes the following components, from front-end to back-end:

• React 18.2.0
• React Router 6.20.0
• Bootstrap 5.3.2
• Node.js 20.11.0
• Express 4.18.2
• Sequelize 6.35.1
• Postgres 15.5

1. On Github, "Fork" this git repo to your own account so that you have your own copy.

   Read more about "forking" here:
   https://docs.github.com/en/free-pro-team@latest/github/getting-started-with-github/fork-a-repo

2. Clone YOUR copy of the git repo to a "local" directory (on your computer), then change into the directory.

   git clone https://github.com/YOUR_ACCOUNT_ID/full-stack-starter.git
   cd full-stack-starter
   

3. Install Docker Desktop: https://www.docker.com/products/docker-desktop

   1. Windows users see notes below...

4. Open a command-line shell, change into your repo directory, and execute these commands:

   docker compose pull
   docker compose up
   

   It will take a while the first time you run these commands to download the "images" to run the web application code in Docker "containers". When you see messages that look like this, the server is running:

   full-stack-starter-server-1       | 5:31:23 PM client.1 |    VITE v4.3.9  ready in 327 ms
   full-stack-starter-server-1       | 5:31:23 PM client.1 |    ➜  Local:   https://localhost:3000/
   

5. Now you should be able to open the web app in your browser at: https://localhost:3000/

6. Open a new tab or window of your shell, change into your repo directory as needed, and execute this command:

   docker compose exec server bash -l
   

   This will log you in to the running server container, as if you were connecting to a different machine over the Internet. Once you're logged in, you will be in a new shell for the container where you can run the following command:

   bin/create-admin.js Firstname Lastname email password
   

   Put in your name and email address and a password. This will create a first admin user in the database.

7. To stop the server, press CONTROL-C in the window with the running server. If it is successful, you will see something like this:

   Killing full-stack-starter_db_1           ... done
   Killing full-stack-starter_server_1       ... done
   Killing full-stack-starter_mailcatcher_1  ... done
   

   If it is not successful, you may see something like this:

   ERROR: Aborting.
   

   If you get an error, the server may still be running on your computer. To force it to stop, run the following command and wait for the output to report DONE:

   docker compose stop
   Stopping full-stack-starter_db_1          ... done
   Stopping full-stack-starter_server_1      ... done
   Stopping full-stack-starter_mailcatcher_1 ... done
   

8. That's it! After all this setup is complete, the only command you need to run to get started again is the docker compose up command.

1. Sign up for a Heroku account at: https://signup.heroku.com/

   You will need to add a credit card to your account and enable a billing subscription for Eco dynos.

2. Click on the Deploy button below:

   

   In the App Name field, enter a URL-friendly name that will become part of your final url. (i.e. https://your-app-name.herokuapp.com)

3. Install the Heroku CLI (Command Line Interface) tool: https://devcenter.heroku.com/articles/heroku-cli

   On macOS you must first install Homebrew, if you don't already have it: https://brew.sh/

   When successfully installed, you can execute the command:

   heroku
   

   And you will see output like this:

   CLI to interact with Heroku
   
   VERSION
   heroku/7.47.6 darwin-x64 node-v12.16.2
   
   USAGE
   $ heroku [COMMAND]
   

4. Link your repo directory to the Heroku deployed app:

   heroku git:remote -a [YOUR APP NAME FROM STEP 2HERE]
   

5. Once linked, you can execute Heroku CLI commands. For example, to run the user creation script on the server:

   heroku run "cd server && bin/create-admin.js Firstname Lastname email password"
   

1. Sign up for a Render account at: https://render.com/

   You will need to add a credit card number to your account, even if using free instances.

2. In the Dashboard, go to Blueprints, and click on New Blueprint Instance.

3. Connect your Github account and return to this page. Select your forked repository.

4. Enter a name for your deployment, and optionally the branch you wish to deploy (if not main).

5. Set values for VITE_FEATURE_REGISTRATION (true/false to enable/disable user registration), VITE_SITE_TITLE (the name you wish to appear in the browser title bar), and SMTP_ENABLED (true/false to enable/disable mail, recommend false to start until mail server is set up).

6. Click on Apply and wait, this can take quite a few minutes. You can click on the web service server link to follow the deployment event and watch the logs if you like.

7. Once completed, you can see the site at the provided generated URL.

8. Go to the web service server Settings, and edit the Build Command. Remove the command to run seeders and to create a first admin user so it doesn't re-run on subsequent builds (if [ -d seeders ]; then ../node_modules/.bin/sequelize db:seed:all; fi; bin/create-admin.js Site Admin [email protected] changeme123;). You can log in to the site with this email and temporary password (change it immediately after logging in!).

• Every directory and file on your computer has a path that describes its location in storage. Special path symbols include:

  • The current working directory you are in: .
  • The parent of the current working directory: ..
  • Your home directory: ~
  • The root directory: / (Mac, Linux) or \ (Windows)
    • The same symbol is used as a separator when specifying multiple directories in a path
    • If the path starts with the separator, it means the path starts at the root
      • For example: /Users/myusername/Documents
      • This is called an absolute path
    • If the path does not start with the separator, it means the path starts at the current working directory
      • For example, if the current working directory is: /Users
        then the same path as the previous example is: myusername/Documents
      • This is called a relative path
    • A path can also start with any of the above special path symbols
      • For example, on Mac the same path as the previous example is: ~/Documents

• To print the working directory (i.e. to see the full path of the directory you are currently in):

  pwd
  

• To list the files in the working directory:

  ls -l
  

• To change the working directory:

  cd path
  

• To make a new directory inside the working directory:

  mkdir newpath
  

• To create a new empty file inside the working directory:

  touch filename.ext
  

• To check the status of the files in your local repo (i.e. what's been added or changed):

  git status
  

• To add all the changed files to the next commit:

  git add .
  

  To add specific file(s) to the next commit:

  git add path/to/file1.ext path/to/file2.ext path/with/wildcard/*
  

• To commit the added files with a message:

  git commit -m "My description of what's changed"
  

• To push the commit to the remote repo:

  git push
  

• To pull any new commits from the remote repo:

  git pull
  

• To start all the containers:

  docker compose up
  

• To log in to the running server container:

  docker compose exec server bash -l
  

• To stop all the containers, in case things didn't shutdown properly with CTRL-C:

  docker compose stop
  

• To run the server container without starting everything using the up command:

  docker compose run --rm server bash -l
  

• To re-build the server container:

  docker compose build server
  

• On some PC laptops, a hardware CPU feature called virtualization is disabled by default, which is required. To enable it, reboot your computer into its BIOS interface (typically by pressing a key like DELETE, ESC, or F1 during the boot process), and look for an option to enable it. It may be called something like Intel Virtualization Technology, Intel VT, AMD-V, or some similar variation.

  https://support.microsoft.com/en-us/windows/enable-virtualization-on-windows-11-pcs-c5578302-6e43-4b4b-a449-8ced115f58e1

• Install the Windows Subsystem for Linux (WSL) and make sure to check "Use WSL 2 instead of Hyper-V" when installing Docker Desktop for Windows.

  https://learn.microsoft.com/en-us/windows/wsl/install
  https://docs.docker.com/desktop/install/windows-install/

• Use Microsoft Terminal to open a command-line shell running in your WSL distribution (typically Ubuntu), and use the git command line to clone this project into your Linux filesystem. If you attempt to run this project in Docker from the Windows file system, performance will be degraded and file change detection will not work. Editors like VSCode can edit files in the Linux filesystem of WSL.

Full-Stack Starter
Copyright (C) 2023 <Dev/Mission>

This program is free software: you can redistribute it and/or modify it under the terms of the GNU Affero General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Affero General Public License for more details.

You should have received a copy of the GNU Affero General Public License along with this program. If not, see https://www.gnu.org/licenses/.