Updated the build-dev CI workflow to run the static site generation with a development flag. This ensures the build script runs in the appropriate context for development environments. No issues referenced.
Added copying of .gitignore to the temporary static site location in both development and production build scripts. This prevents unnecessary files from being included in the new orphan branches, ensuring a cleaner and more efficient build process.
Changed the force push target from 'pages' to 'pages-dev' to ensure the dev build process does not interfere with the production pages. This helps maintain a clear separation between development and production environments, reducing the risk of unintentional overwrites.
Renamed 'build.yml' to 'build-dev.yml' to clarify its purpose for development builds. Updated branch triggers and orphan branch naming to 'dev' and 'pages-dev' respectively to distinguish development deployment processes from production. This enhances workflow clarity and separation of concerns in CI/CD practices.
- Added a new GitHub Actions workflow for the development branch to build and deploy the static site.
- Modified the existing workflow to trigger on the main branch instead of the static branch.
- Refactored the main.py script for consistency in string quotation.
The new workflow simplifies deployment processes during development, ensuring seamless and automated integration and testing.
Condensed the installation commands to streamline the setup process. Removed redundant pip upgrade step to avoid potential conflicts and expedite build workflow. No change to the overall functionality or dependency management.
Updated the build script to use `python3` and `pip3` commands, ensuring compatibility with environments where Python 2 might be the default. Also added `--break-system-packages` flag to `pip3` install to handle specific package installations without breaking the environment.
Replaces `runs-on` with `container` to utilize a Docker container
for node:20-bookworm. This enhances consistency and reproducibility
by standardizing the build environment across different runs.
Set up a GitHub Actions workflow to build and deploy the static site from the 'static' branch to the 'pages' branch. This workflow includes steps to install dependencies, generate the static site using Python, and handle deployment through Git configuration and git commands.
Refactored the Flask application to generate a static site instead of running as a dynamic web app. Added a CI workflow to build and deploy the static site on pushes to the 'static' branch.
- Replaced Flask route handling with a function that generates HTML files using Jinja2 templates.
- Modified the argparse logic to trigger the static site generation.
- Updated the .gitignore file to exclude the build directory.
- Created a Forgejo Actions workflow to automate the build and deploy process.
This change improves performance and reduces server overhead by serving pre-rendered static content.
Changed the metrics route from "/_metrics/" to "/metrics/" for consistency and better readability. This should enhance usability and clarity for users accessing the metrics endpoint.
Extended `get_transparency_data` function to allow current balances by adding an `allow_current` parameter. This change facilitates the inclusion of up-to-date balance information in the metrics output, enhancing the accuracy of financial reporting.
Introduced a new debug configuration for production mode in VSCode, facilitating easier debugging in different environments. Additionally, updated the `get_transparency_data` function to handle year and month as strings, ensuring compatibility with subsequent operations. Added a necessary parameter to a function call in `main.py` to align with the updated function signature.
Enhanced `get_transparency_data` to support an `allow_current` flag, preventing the inclusion of data from the current month. This ensures historical data analysis remains consistent when current month data might be incomplete. Updated calls to the function to pass appropriate parameters.
Added entry for membership fees in July to track additional revenue correctly. This update ensures financial data completeness and accuracy. No functional changes to the application's logic.
Added a new /_metrics/ endpoint to expose financial data in Prometheus format, facilitating better monitoring and analytics.
Enhanced the get_latest_month function to optionally exclude the current month, preventing potential issues in incomplete data scenarios, with this behavior being toggled by the application's development mode status.
Introduced a Tor-based alternative URL for Invidious to the services list.
This enhances accessibility for users preferring or requiring access
via the Tor network, improving privacy and circumventing network restrictions.
Replaced "Pride" references with "Privacy" to revert pride month styling. Updated header background to primary gradient and replaced SVG with an image for improved maintainability. The changes aim to enhance visual appeal and clarity of the site's purpose.
Included bank fees under financial expenses in the JSON data. This ensures a more accurate and comprehensive representation of all outgoing costs, improving financial tracking and reporting.
Adjusted the membership fees value to 382.42 EUR to reflect the latest financial data. Ensures accurate financial reporting and accounting. No other changes to costs or revenue items.
Updated membership information with pricing details and added
a call-to-action button linking to the join page. This aims to
increase engagement and improve user experience by providing
clear steps for potential new members.
Increased membership fees to 375 EUR and adjusted server costs to -317.62 EUR. These changes reflect the latest budget review and ensure accurate financial reporting.
The padding on .btn-primary .main-link was redundant and inconsistent with the overall button styling. Removing it ensures better alignment and consistency in button appearance across the application.
Combined Piped and Invidious into a single service entry in the JSON file to avoid redundancy and simplify maintenance. Adjusted the descriptions and links accordingly to reflect the merged entry.
Enhanced the UI by adding dropdown menus to service links. This includes new styles for dropdowns in CSS and corresponding changes in the HTML templates. Also, extended `services.json` to support alternative links with Tor options for better accessibility.
Adjusted the maximum width for service cards to improve layout on larger screens.
Replaced the outdated room link to '#private-coffee:private.coffee' with the correct '#coffeespace:private.coffee' to ensure users are directed to the updated Private.coffee space.
Added a new upload icon to the assets directory to enhance usability and UI consistency. Incorporated Transfer.coffee service for secure file transfers and moved GotHub entry for better data organization. This improves service discoverability and aligns with the project’s goal of providing diverse, privacy-respecting tools.
Changed the text on the membership button from "JOIN & REBEL" to "JOIN & SUPPORT" in the base template. This adjustment better reflects the community spirit and aims to be more inclusive, encouraging broader participation. The update is part of ongoing efforts to make our digital spaces more welcoming and representative of our values.
Adjusted the EUR server costs entry in finances.json to reflect the recent increase in expenditures. This ensures financial data accuracy and up-to-date budgeting.
Updated membership information with pricing details and added
a call-to-action button linking to the join page. This aims to
increase engagement and improve user experience by providing
clear steps for potential new members.
Introduces a new VSCode debug configuration to streamline debugging for Python scripts. This configuration includes settings to launch the main.py program using the integrated terminal within the current workspace and sets an environment variable for development purposes.
Adjusted the server costs in the finances dataset to reflect the latest expense of -85.62 EUR. This ensures the financial records are accurate and up-to-date.
Introduced a new LGBTIQ+ rainbow icon SVG to enhance visual representation and inclusivity on the platform. This update includes the integration of the icon within the base template, specifically at the footer section to signal support for the LGBTIQ+ community. This change aligns with our commitment to diversity and inclusiveness.
Adjust the media query breakpoint to 991px to enhance the responsive layout for devices with larger screens. Added specific styling for `p.text-center.special-header` to increase the font size for improved readability. Optimized CSS to ensure primary buttons and navigation elements adapt more smoothly across a wider range of device widths. These adjustments make the UI more flexible and visually accessible, addressing user feedback on readability and interaction with key UI elements on tablets and smaller laptop screens.
Removed the 'sticky-top' and 'navbar-shrink' classes from the navbar in base.html to enhance its responsiveness and adaptability across different screen sizes. This change aims to offer a more streamlined user experience by ensuring the navbar's style and position remain consistent and unobtrusive, particularly on mobile devices where screen real estate is limited.
- Added '.bg-pride-gradient' class to CSS for a colorful background gradient celebrating Pride Month, replacing the previous primary gradient. This change visually signifies our support for the LGBTQ+ community.
- Replaced the header logo with a detailed vector image to enhance visual engagement.
- Reformatted the HTML structure to improve code readability and maintainability. This involves adjusting indentation and whitespace, making the code easier to follow and modify.
- Updated section headers and content organization in the index page to enhance information flow and user engagement.
This update aligns with the initiative to celebrate and acknowledge Pride Month, reflecting our commitment to inclusivity. Additionally, the introduction of a more detailed logo and the restructured HTML seeks to enhance overall site aesthetics and user experience.
Introduced a new LGBTIQ+ rainbow icon SVG to enhance visual representation and inclusivity on the platform. This update includes the integration of the icon within the base template, specifically at the footer section to signal support for the LGBTIQ+ community. This change aligns with our commitment to diversity and inclusiveness.
Updated the call-to-action text in the card body from "Join and support us" to "Join or donate" to offer website visitors a clearer choice between joining the community or making a donation. This change aims to streamline user decisions and potentially increase conversions by directly addressing the primary actions users can take to support the open-source community.
