uncloud/uncloud_v3
Nico Schottelius ef4ca9d879 [uncloud_v3] update to django 5.0.2 2024-02-25 16:30:05 +09:00
..
app Cleanup and more demo products 2022-07-16 18:22:52 +02:00
uauth v3: link product to resource 2022-01-02 19:34:55 +01:00
uncloud Add order-confirmation view and take user to this after the purchase 2022-02-22 13:33:29 +05:30
.gitignore v3: link product to resource 2022-01-02 19:34:55 +01:00
Dockerfile upgrade to python 3.11.1 2023-02-05 21:13:30 +01:00
Makefile Cleanup and more demo products 2022-07-16 18:22:52 +02:00
README.md Cleanup and more demo products 2022-07-16 18:22:52 +02:00
build.sh Cleanup and more demo products 2022-07-16 18:22:52 +02:00
manage.py fresh start v3 2022-01-02 17:13:01 +01:00
requirements.txt [uncloud_v3] update to django 5.0.2 2024-02-25 16:30:05 +09:00

README.md

Kubernetes integration

Development / Minikube

To setup a development environment, start minikube on your local machine. Use kubectl get nodes to verify minikube is up and running.

Settings

Environment variables / Settings / Environment

  • SECRET_KEY
  • DEBUG
  • DATABASE
  • Should be: POSTGRES_HOST, POSTGRES_DB, POSTGRES_USER, POSTRES_PASSWORD

Versions

Future (unplanned)

  • When/where to add timeframe constraints
  • Timeframe slug-or-id
  • Maybe slug and backlink to avail products
  • Timeframe in product
  • Should a product define list of time frames AND resources?
    • Then can do autoselect on and only show complete ones
    • resources are also timeframe bound
      • name != unique (?)
    • how do we link?
      • stays towards resource
      • we only show resources which have price_per_time with one of our timeframes
      • And we filter out timeframes that don't have all resources
  • Can we filter drop down in admin?
  • yes: ModelAdmin.formfield_for_manytomany(db_field, request, **kwargs)¶
  • resources should have a slug
  • can be used as an identifier and non unique names
  • Execute collectstatic for docker

3.1 (validation release, planned)

  • Ensure that one resource cannot have multiple price_per_timeframe of the same timeframe
  • Add wireguard config support

3.0.2 (planned)

  • Add basic validation to ordering

3.0.1 (planned)

NEXT STEP: CREATE THE ORDER AND RESOURCE ORDER OBJECTS

  • Show products [done]
  • Link to ProductOrderForm [done]
  • Find suitable timeframes for a product [done]
  • Continue to resources / add resources
    • Need to list resources [done]
    • Need to create manytomany relations for each resource resoluting in ResourceOrders
      • Need to pass in the price for the selected timeframe [done]
    • On submit
      • Create ProductOrder
      • Create ResourceOrder(s)

3.0.0 (2022-01-14)

  • Introduce ProductOrderView

Pre-Production requirements

  • Products need to ensure all resources are consistent for different timeframes
  • Products cannot have same resource linked twice in same timeframe