Make EXAMPLE presets be legitimate starting points

[apolopena]

Problem this feature will solve

Workspace EXAMPLES require hand configuration of .gp/bash/init-project.sh in order to work on subsequent initializations, once initial scaffolding files have been saved to the repository. EXAMPLES should be stand-alone starting points once initial scaffolding files have been saved to the repository, meaning they should not require alteration of gitpod-laravel-starter internal bash scripts to properly initialize.

In other words:
Workspace urls successfully initialized with an EXAMPLE env variable passed in will not configure properly once initial scaffolding files have been saved to version control and a new workspace is initialized from that repository.

Background

.gp/bash/project-init.sh handles project specific initialization routines.

Proposed Solution

Ensure that examples initialize themselves from .gp/bash/project-init.sh rather than from it's .gp/bash/examples<init example script>.sh file.
.gp/bash/examples<init example script>.sh should really only download and untar the archive for project specfic files of that particular example.

A legitimate starting point will properly initialize itself after initial project scaffolding files have been saved to the repository.

• Ensure that EXAMPLE 1 and EXAMPLE 2 follows the proposed solution
• QA EXAMPLE 1 and EXAMPLE 2 in their own repository to make sure that they are legitimate starting points.
• Ensure that EXAMPLE 3 and EXAMPLE 4 follow the proposed solution
• QA EXAMPLE 3 and EXAMPLE 4 in their own repository to make sure that they are legitimate starting points.
• Ensure that EXAMPLE 10 and EXAMPLE 11 follow the proposed solution
• QA EXAMPLE 10 and EXAMPLE 11 in their own repository to make sure that they are legitimate starting points.
• Update README.md with information and any caveats in regard to using an EXAMPLE as a starting point.

Constraints and Assumptions

• There should be a separate repository and tag for each set of files for any particular EXAMPLE.
• Each EXAMPLE repository should contain a project specific .gp/bash/init-project.sh file.
• Each gp/bash/examples.shmust untar it's archive using the--overwrite` option.
• Once initial scaffolding is saved to the repository, ANY installation set by starter.ini (such as phpmyadmin) except the front end scaffolding to use (React, Vue, Bootstrap) will be installed. Note that this may differ from the original EXAMPLE. It is up to the user to set their starter.ini how they want it. In other words, an EXAMPLE will not supercede starter.ini once initial scaffolding files have been saved to the repository.

Alternatives or Workarounds

Not recommended:
Configure a particular EXAMPLE to be persistant once initial scaffolding files are in VCS by hacking and slashing the internal bash scripts of gitpod-laravel-starter