feat: change to next-kubernetes

README.md

-# Meteor-kubernetes
+# Next-kubernetes
 
-This is an extension of https://git.panter.ch/gitlab-ci/kubernetes-base 
-that builds meteor-apps. 
+This is an extension of https://git.panter.ch/gitlab-ci/kubernetes-base
+that builds Next-apps.
 
 ## Usage:
 
 ```
 # on top of your gitlab-ci.yml
 
-include: 
-  - project: gitlab-ci/meteor-kubernetes
+include:
+  - project: gitlab-ci/next-kubernetes
     ref: v1.0.0
-    file: meteor-kubernetes.yml
+    file: next-kubernetes.yml
 
 variables:
   CUSTOMER_NAME: pan
   APP_NAME: avatar
   CLUSTER_NAME: production
-  
-  # meteors specific:
-  MONGODB_ENABLED: 'true' # whether to create a mongobd
-  WORKER_ENABLED: 'false' # whether to launch an additional pod which has WORKER_ENABLED env var. usefull for cronjobs and migrations
-  MONGODB_REPLICAS: '3' # how many mongodb-replicas it will launch on production. other envs have always 1
-
-
 ```
-
-

meteor-kubernetes.yml → next-kubernetes.yml

@@ -5,18 +5,10 @@ include:
 
 app-build:
   extends: .app-build
-  script:
-    - cd $APP_PATH
-    - echo "add healthcheck package"
-    - meteor add panter:healthroute --allow-superuser
-    - meteor add qualia:prod-shell --allow-superuser
-    - echo "current path is $(pwd)"
-    - yarn
-    - echo "building into $CI_PROJECT_DIR"
-    - TOOL_NODE_FLAGS="--max_old_space_size=3584 --min_semi_space_size=8 --max_semi_space_size=256 --optimize_for_size" meteor build $CI_PROJECT_DIR --architecture os.linux.x86_64 --allow-superuser --server-only --directory
   artifacts:
     paths:
-      - $CI_PROJECT_DIR/bundle
+      - $CI_PROJECT_DIR/dist
+      - $CI_PROJECT_DIR/.next
 
 .ensureDocker: &ensureDocker |
   function ensureDockerfile() {