Update the project template to use recipes

Created on 11 February 2025, about 2 months ago

Problem/Motivation

With our recipes set up, we can create a more flexible project template. E.g. we can use env variables on gitpod to install different recipes.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

📌 Task
Status

Active

Version

1.0

Component

Miscellaneous

Created by

🇦🇹Austria arthur_lorenz Vienna

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @arthur_lorenz
  • 🇦🇹Austria arthur_lorenz Vienna

    PR on GitHub

  • 🇦🇹Austria fago Vienna

    thank you! I reviewed the PR and left a couple of remarks there, please check.
    Also, please always provide Gitpod-test links for your branches when creating a PR. You need it anyway to test it yourself, so please be so kind and provide the link to reviewers as well.

  • 🇦🇹Austria arthur_lorenz Vienna

    Thx, I updated and commented the PR.

    First, here are the Links to test the gitpod environments:
    Base
    Demo
    Blog

    Let's move the discussion for different project types here:
    I introduced the env variable LD_PROJECT_TYPE that lets you choose between predefined sets of environment variables, for the ideal configurtion depending on the use case. Since we agreed on using this repo as project template as well as a demo, I figured this would be a clear way to differentiate the different types.

    E.g. for demo purposes it makes a lot of sense to use the better styled shadcn frontend repo rather than our empty nuxt3 demo repo. All of the used variable can be overridden, so we don't lose any flexibility. It will make the transition to github code spaces also easier, since we do not have to keep various variable combinations in mind. And in case we want to streamline the installation process for local environments aswell, this will be a good starting point.

  • 🇦🇹Austria arthur_lorenz Vienna

    PR got merged!

  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.71.5 2024