.github/sync_release.yml

@@ -0,0 +1,32 @@
+name: Update Test Branch
+
+on:
+  push:
+    branches: [main]
+
+permissions: write-all
+
+jobs:
+  sync:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v3
+        with:
+          ssh-key: ${{secrets.SECRET_KEY}}
+          fetch-depth: 0
+
+      - name: Setup Git User
+        run: |
+          git config user.name "Luke Sikina"
+          git config user.email "lucas.sikina@gmail.com"
+
+      - name: Update Test Branch
+        run: |
+          git checkout main
+          git fetch origin
+          git checkout release
+          git pull
+          git rebase origin/main
+          git push origin release --force
+

.github/workflows/sync_release.yml

@@ -0,0 +1,32 @@
+name: Update Test Branch
+
+on:
+  push:
+    branches: [main]
+
+permissions: write-all
+
+jobs:
+  sync:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v3
+        with:
+          ssh-key: ${{secrets.SECRET_KEY}}
+          fetch-depth: 0
+
+      - name: Setup Git User
+        run: |
+          git config user.name "Luke Sikina"
+          git config user.email "lucas.sikina@gmail.com"
+
+      - name: Update Test Branch
+        run: |
+          git checkout main
+          git fetch origin
+          git checkout release
+          git pull
+          git rebase origin/main
+          git push origin release --force
+

.github/workflows/test-runner.yml

@@ -0,0 +1,24 @@
+name: Java CI with Maven
+
+on:
+  push:
+    branches: [ "main", "release" ]
+  pull_request:
+    branches: [ "*" ]
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/checkout@v3
+    - name: Set up JDK 21
+      uses: actions/setup-java@v3
+      with:
+        java-version: '21'
+        distribution: 'corretto'
+        cache: maven
+    - name: Build with Maven
+      run: "for dir in 'uploader' 'info-service'; do cd $dir; mvn verify; cd ..; done" 
+

README.md

@@ -54,5 +54,9 @@ pull in the artifact by including the following in your pom:
 </dependency>
 ```
 
+:)
+
+
 When implementing the info endpoint, you can assume your service's resource ID will
-be available inside your container via the environment variable `RESOURCE_UUID`
+be available inside your container via the environment variable `RESOURCE_UUID`
+

uploader/Dockerfile

@@ -16,4 +16,4 @@ COPY --from=build target/uploader-*.jar /dataupload.jar
 # Time zone
 ENV TZ="US/Eastern"
 
-ENTRYPOINT ["java", "-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:5005", "-Xmx8192m", "-jar", "/dataupload.jar"]
+ENTRYPOINT java $DEBUG_VARS $PROXY_VARS -Xmx8192m -jar /dataupload.jar

uploader/README.md

@@ -47,7 +47,7 @@ that Amazon provides you.
 
 5. Run
 
-Run `docker run --rm --env-file .env gic-data-uploader`. Here is an example of a
+Run `docker compose --profile production up -d `. Here is an example of a
 successful output, with logging prefixes omitted:
 
 ```
@@ -79,10 +79,6 @@ Verifying delete capabilities
 S3 connection verified.
 ```
 
-TODO:
-- Mount this study in service workbench
-  - Admin UI
-- Test all 4 workspace types
-  - Mount study
-  - R/W access
-  - 
+6. Run Migrations
+
+`docker compose --profile migrate up -d`