132 solve environment inconsistency between remote and local

.dvc/.gitignore

@@ -0,0 +1,3 @@
+/config.local
+/tmp
+/cache

.dvc/config

@@ -0,0 +1,4 @@
+[core]
+    remote = remote
+['remote "remote"']
+    url = /home/ilona/dvc_remote

.dvcignore

@@ -0,0 +1,3 @@
+# .dvcignore files (optional) contain a list of paths for DVC to ignore,
+# which can dramatically increase its operational performance.
+# see: https://dvc.org/doc/user-guide/project-structure/dvcignore-files

.github/workflows/python-app.yml

@@ -0,0 +1,65 @@
+# This workflow will install Python dependencies, run tests and lint with a single version of Python
+# For more information see: https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-python
+
+name: Python application
+
+on:
+  push:
+    branches: [ "master" ]
+  pull_request:
+    branches: [ "master" ]
+
+permissions:
+  contents: read
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest # Which OS this runs on
+    strategy:
+      matrix:
+        python-version: ["3.11.13"] # You can build against multiple Python versions
+
+    steps:
+    - uses: actions/checkout@v4
+    - name: Set up Python ${{ matrix.python-version }} # Name of an action that sets up Python
+      uses: actions/setup-python@v5                    # https://github.com/actions/setup-python
+      with:
+        python-version: ${{ matrix.python-version }}
+
+    - name: Install and upgrade core tools
+      run: |
+        python -m pip install --upgrade pip
+        python -m pip install pip-tools
+
+    - name: Verify lockfile consistency (diagnostic mode)
+      run: |
+        echo "Generating requirements.txt from source to check for differences..."
+        pip-compile --quiet requirements.in -o requirements.txt
+        echo "Comparing the generated file with the one in the repository:"
+        # 'git diff' will show any diff's. '|| true' ensures the step doesn't fail.
+        git diff requirements.txt || true
+
+    - name: Install Python dependencies from lockfile
+      run: |
+        echo "Installing dependencies from requirements.txt..."
+        if [ -f requirements.txt ]; then python -m pip install -r requirements.txt; fi
+
+    - name: Lint with flake8
+      run: |
+        # stop the build if there are Python syntax errors or undefined names
+        flake8 . --count --select=E9,F63,F7,F82 --show-source --statistics
+        # exit-zero treats all errors as warnings. The GitHub editor is 127 chars wide
+        flake8 . --count --exit-zero --max-complexity=10 --max-line-length=127 --statistics
+   # DVC iterative setup installation path is not working (Nov 2024), now happens via requirement.txt
+   # - name: DVC install      # see: https://github.com/iterative/setup-dvc
+   #   uses: iterative/setup-dvc@v1
+   # - name: DVC
+   #   run:  |
+   #     # see: https://dvc.org/doc/user-guide/troubleshooting#missing-files,
+   #     # no remote cloud service available yet
+   #     dvc pull
+    - name: Test with pytest 
+      run: |
+        # Final action: runs pytest for all tests in the ./tests dir
+        pytest ./tests/*.py -vv

.github/workflows/stale.yml

@@ -0,0 +1,27 @@
+# This workflow warns and then closes issues and PRs that have had no activity for a specified amount of time.
+#
+# You can adjust the behavior by modifying this file.
+# For more information, see:
+# https://github.com/actions/stale
+name: Mark stale issues and pull requests
+
+on:
+  schedule:
+  - cron: '30 1 * * *'
+
+jobs:
+  stale:
+
+    runs-on: ubuntu-latest
+    permissions:
+      issues: write
+      pull-requests: write
+
+    steps:
+    - uses: actions/stale@v5
+      with:
+        repo-token: ${{ secrets.GITHUB_TOKEN }}
+        stale-issue-message: 'Stale issue message'
+        stale-pr-message: 'Stale pull request message'
+        stale-issue-label: 'no-issue-activity'
+        stale-pr-label: 'no-pr-activity'

.gitignore

@@ -0,0 +1,167 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm.fming.dev/#use-with-ide
+.pdm.toml
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/
+
+# MLOPs proj3 US census app files
+./mlops_proj3_tree.txt
+./mlops_proj3_tree_dirs.txt
+./logs/*.*
+census_app.log
+

LICENSE.txt

@@ -1,46 +1,21 @@
-Copyright © 2012 - 2020, Udacity, Inc.
+MIT License
 
-Udacity hereby grants you a license in and to the Educational Content, including
-but not limited to homework assignments, programming assignments, code samples,
-and other educational materials and tools (as further described in the Udacity
-Terms of Use), subject to, as modified herein, the terms and conditions of the
-Creative Commons Attribution-NonCommercial- NoDerivs 3.0 License located at
-http://creativecommons.org/licenses/by-nc-nd/4.0 and successor locations for
-such license (the "CC License") provided that, in each case, the Educational
-Content is specifically marked as being subject to the CC License.
+Copyright (c) 2023 Ilona Brinkmeier
 
-Udacity expressly defines the following as falling outside the definition of
-"non-commercial":
-(a) the sale or rental of (i) any part of the Educational Content, (ii) any
-    derivative works based at least in part on the Educational Content, or (iii)
-    any collective work that includes any part of the Educational Content;
-(b) the sale of access or a link to any part of the Educational Content without
-    first obtaining informed consent from the buyer (that the buyer is aware
-    that the Educational Content, or such part thereof, is available at the
-    Website free of charge);
-(c) providing training, support, or editorial services that use or reference the
-    Educational Content in exchange for a fee;
-(d) the sale of advertisements, sponsorships, or promotions placed on the
-    Educational Content, or any part thereof, or the sale of advertisements,
-    sponsorships, or promotions on any website or blog containing any part of
-    the Educational Material, including without limitation any "pop-up
-    advertisements";
-(e) the use of Educational Content by a college, university, school, or other
-    educational institution for instruction where tuition is charged; and
-(f) the use of Educational Content by a for-profit corporation or non-profit
-    entity for internal professional development or training.
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
 
-THE SERVICES AND ONLINE COURSES (INCLUDING ANY CONTENT) ARE PROVIDED "AS IS" AND
-"AS AVAILABLE" WITH NO REPRESENTATIONS OR WARRANTIES OF ANY KIND, EITHER
-EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
-MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. YOU
-ASSUME TOTAL RESPONSIBILITY AND THE ENTIRE RISK FOR YOUR USE OF THE SERVICES,
-ONLINE COURSES, AND CONTENT. WITHOUT LIMITING THE FOREGOING, WE DO NOT WARRANT
-THAT (A) THE SERVICES, WEBSITES, CONTENT, OR THE ONLINE COURSES WILL MEET YOUR
-REQUIREMENTS OR EXPECTATIONS OR ACHIEVE THE INTENDED PURPOSES, (B) THE WEBSITES
-OR THE ONLINE COURSES WILL NOT EXPERIENCE OUTAGES OR OTHERWISE BE UNINTERRUPTED,
-TIMELY, SECURE OR ERROR-FREE, (C) THE INFORMATION OR CONTENT OBTAINED THROUGH
-THE SERVICES, SUCH AS CHAT ROOM SERVICES, WILL BE ACCURATE, COMPLETE, CURRENT,
-ERROR- FREE, COMPLETELY SECURE OR RELIABLE, OR (D) THAT DEFECTS IN OR ON THE
-SERVICES OR CONTENT WILL BE CORRECTED. YOU ASSUME ALL RISK OF PERSONAL INJURY,
-INCLUDING DEATH AND DAMAGE TO PERSONAL PROPERTY, SUSTAINED FROM USE OF SERVICES.
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.