Merge pull request #200 from devforth/next

Next

Author: ivictbor

adminforth/commands/createApp/main.js

@@ -22,6 +22,7 @@ export default async function createApp(args) {
     await tasks.run();
   } catch (err) {
     console.error(chalk.red(`\n❌  ${err.message}\n`));
+    console.error(err.stack);
     process.exit(1);
   }
 }

adminforth/commands/createApp/utils.js

@@ -237,7 +237,7 @@ async function writeTemplateFiles(dirname, cwd, options) {
       src: '.dockerignore.hbs',
       dest: '.dockerignore',
       data: {
-        sqliteFile: detectDbProvider(options.db).startsWith('sqlite') ? options.db.split('://')[1] : null,
+        sqliteFile: detectDbProvider(dbUrl).startsWith('sqlite') ? dbUrl.split('://')[1] : null,
       },
     }
   ];

adminforth/documentation/blog/2025-02-19-compose-ec2-deployment-ci-registry/index.md

@@ -1,6 +1,6 @@
 ---
 slug: compose-ec2-deployment-github-actions-registry
-title: "Amazon EC2 Deployments with GitHub Actions, Terraform, Docker & Amazon ECR"
+title: "Amazon EC2 Deployments with GitHub Actions, Terraform, Docker & Self-hosted Registry"
 authors: ivanb
 tags: [aws, terraform, github-actions]
 description: "The ultimate step-by-step guide to cost-effective, build-time-efficient, and easy managable EC2 deployments using GitHub Actions, Terraform, Docker, and a self-hosted registry."
@@ -108,7 +108,7 @@ Make sure you are not calling bundleNow in `index.ts` file for non-development m
   }
 ```
 
-### Step 1.3 - Make sure you have `migrateLiveAndStart` script in `package.json`
+### Step 1.3 - Make sure you have all required scripts in `package.json`
 
 ```json title="./myadmin/package.json"
 ...

adminforth/documentation/blog/2025-02-19-compose-ec2-deployment-ecr-ci/index.md

@@ -8,7 +8,7 @@ image: "/ogs/ga-tf-ecr.jpg"
 ---
 
 
-![alt text](ga-tf-aws.jpg)
+![alt text](ga-tf-ecr.jpg)
 
 
 This guide shows how to deploy own Docker apps (with AdminForth as example) to Amazon EC2 instance with Docker and Terraform involving pushing images into Amazon ECR.
@@ -40,7 +40,7 @@ Quick difference between approaches from previous post and current post:
 | How build happens | Source code is rsync-ed from CI to EC2 and docker build is done there | Docker build is done on CI and docker image is pushed to registry, then Docker on EC2 pulls from registry |
 | Where build is done | On EC2 | On CI |
 | How Docker build layers are cached | Cache is stored on EC2 | GitHub actions has no own Docker cache out of the box, so it should be stored in dedicated place (we use Amazon ECR) |
-| Advantages | Cheaper (no egrass traffik from EC2) and faster | Build is done on CI, so EC2 server is not overloaded |
+| Advantages | Cheaper (no egrass cache traffik from EC2) and faster | Build is done on CI, so EC2 server is not overloaded |
 | Disadvantages | Build on EC2 requires additional server RAM / requires swap / overloads CPU | More terraform code is needed. Extra cost for egress traffik to GitHub for cache transfer |
 | Initial build time\* | 3m 13.541s | 3m 54s |
 | Rebuild time (changed `index.ts`)\*| 0m 51.653s | 0m 54.120s |
@@ -98,7 +98,7 @@ Drawback is that buildx which is running on GitHub action server will download c
 
 # Prerequisites
 
-I will use you run Ubuntu (Native or WSL2).
+I will assume you run Ubuntu (Native or WSL2).
 
 You should have terraform, here is official repository: 
 

adminforth/package-lock.json

@@ -58,6 +58,7 @@
   "license": "ISC",
   "type": "module",
   "dependencies": {
+    "@babel/parser": "^7.27.0",
     "@clickhouse/client": "^1.4.0",
     "@faker-js/faker": "^9.0.3",
     "@inquirer/prompts": "^7.4.1",