Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Significant Refactor #147

Draft
wants to merge 5 commits into
base: main
Choose a base branch
from
Draft

Significant Refactor #147

wants to merge 5 commits into from

Commits on Aug 1, 2022

  1. Significant Refactor.

    - added numerous environment variable changes such as implied defaults that can be overriden.
    - skipped out on using git modules and just pull repo into build/launch step.  Adherance to license requires no repackaging and this solves this.
    - cleaned up now unnecessary .env file.
    - recycled environment section using yaml features.
    - writing a few strings to config path to persist data between container starts that focus on cryptography and secrets.
    - writing installed commit to the config path in case the end user needs to change the upstream git commit ID to a newer version for detection and automagic upgrades.
    - added docker-compose.override.yml pattern to .gitignore to allow users to customize their local dev environment if they use docker-compose.yml
    - wrote a dockerfile/container image which allows for uploading the base container to a private or public docker container registry without breaking the license rules.
    - left .env ignore in case users wish to continue to use the old method.
    - updated README.md to include updated simplified instructions.
    - added start.sh script and wait-for-it.sh into the shell $PATH to allow for a potential future of allowing the main executable (node JS app) to run under a limited privilege user while still allowing the init scripts to be executed securely.
    - added some input sanitation for certain critical variables.
    - by default disabled/commented out the studio service as its not to typically be run to enforce better default deployment practices.  I would like to figure out what specific query to execute via the CLI instead of running a whole container to establish the first user in the end.
    - wrote relatively unopinionated docker-compose.yml file to avoid causing problems for people trying to deploy this behind a reverse proxy for potential features such as TLS/HTTPS termination.
    - upgraded compose version to latest '3.9' to be sure to enable most modern feature set.
    
    Fixes calcom#87 by providing a working baseline with sober defaults.
    Fixes calcom#88 by ensuring consistency across all containers Environment vars.
    Fixes calcom#93 by allowing users to mount the application files within their IDE workspace, however, this will never solve for any times you will need to run yarn build steps.
    Fixes calcom#99 by no longer using git submodules and just pulling a single commit depth copy of the ORIGIN repository on app bootstrap/first boot.
    Fixes calcom#113 by no longer requiring build locally if the community maintainer of the Cal docker repository on GitHub will push this image to the hub.
    Fixes calcom#121 by removing dependency on BuildKit this is done by simply deploying the app if its detected to be the first execution of this container be it due to no container persistence or a commit version upgrade from ORIGIN.
    Fixes calcom#128 by removing dep on BuildKit
    Fixes calcom#123 not replicatable and confirmed to be working in repository shipped state.
    Fixes calcom#136 by building app on first launch from user define-able envvars which can be defined in numerous ways.
    Colin committed Aug 1, 2022
    Configuration menu
    Copy the full SHA
    73b2e61 View commit details
    Browse the repository at this point in the history
  2. fixup

    Colin committed Aug 1, 2022
    Configuration menu
    Copy the full SHA
    7e4190e View commit details
    Browse the repository at this point in the history

Commits on Aug 2, 2022

  1. fixup

    please squash this commit before merge
    Leopere authored Aug 2, 2022
    Configuration menu
    Copy the full SHA
    5aeeac7 View commit details
    Browse the repository at this point in the history
  2. Added ifndef function for declaring container vars.

    To clean up visually environment variable definitions and defaults `ifndef` function has been added.
    It checks var for null, and if null, defines the default string based on defined defaults.
    Also, it prints variable strings to the console[stdout] for debugging.
    I also added more comments to start.sh's environment definitions for posterity.
    Leopere authored Aug 2, 2022
    Configuration menu
    Copy the full SHA
    40e93a3 View commit details
    Browse the repository at this point in the history

Commits on Aug 10, 2022

  1. Update README.md

    Co-authored-by: Avinal Kumar <avinal.xlvii@gmail.com>
    Leopere and avinal authored Aug 10, 2022
    Configuration menu
    Copy the full SHA
    0f4740e View commit details
    Browse the repository at this point in the history