Aleš
Aleš
ZZerops
Created by kolisko on 1/15/2025 in #💪・community-support
obtain zerops.yml for existing service
should be fixed now @kolisko
16 replies
ZZerops
Created by Soustruh on 1/23/2025 in #💪・community-support
File listed in addToRunPrepare not available in prepareCommands
let me make a private channel for you, I already messaged Vlado with the offer to create a private support channel for you guys, but he never got back to me
9 replies
ZZerops
Created by Soustruh on 1/23/2025 in #💪・community-support
File listed in addToRunPrepare not available in prepareCommands
not senstive
9 replies
ZZerops
Created by Soustruh on 1/23/2025 in #💪・community-support
File listed in addToRunPrepare not available in prepareCommands
it's fine
9 replies
ZZerops
Created by Soustruh on 1/23/2025 in #💪・community-support
File listed in addToRunPrepare not available in prepareCommands
No description
9 replies
ZZerops
Created by Louay on 1/22/2025 in #💪・community-support
Ubuntu password
No description
191 replies
ZZerops
Created by Louay on 1/22/2025 in #💪・community-support
Ubuntu password
No description
191 replies
ZZerops
Created by Louay on 1/22/2025 in #💪・community-support
Ubuntu password
yes
191 replies
ZZerops
Created by Louay on 1/22/2025 in #💪・community-support
Ubuntu password
No description
191 replies
ZZerops
Created by Louay on 1/22/2025 in #💪・community-support
Ubuntu password
No description
191 replies
ZZerops
Created by Louay on 1/22/2025 in #💪・community-support
Ubuntu password
with this your secret APP_KEY will be available to build under TOKEN and no secret will be exposed to zerops.yml, since it will only contain the reference
191 replies
ZZerops
Created by Louay on 1/22/2025 in #💪・community-support
Ubuntu password
No description
191 replies
ZZerops
Created by Louay on 1/22/2025 in #💪・community-support
Ubuntu password
yes, you can only put non-sensitive values to zerops.yml, if your build requires some tokens, you can add them to secret variables and them reference them in build using RUNTIME_ prefix, let me show you
191 replies
ZZerops
Created by Louay on 1/22/2025 in #💪・community-support
Ubuntu password
No description
191 replies
ZZerops
Created by Louay on 1/22/2025 in #💪・community-support
Ubuntu password
all depends if you are working on some serious project or just some hobby stuff
191 replies
ZZerops
Created by Louay on 1/22/2025 in #💪・community-support
Ubuntu password
it's just the cleanest would be to do it against staging env -> deploy to staging env -> confirm everything went ok on staging env -> deploy to prod env
191 replies
ZZerops
Created by Louay on 1/22/2025 in #💪・community-support
Ubuntu password
that staging copy is actually optional, you can generate even against your production db
191 replies
ZZerops
Created by Louay on 1/22/2025 in #💪・community-support
Ubuntu password
you might need to experiment with it a bit... the command to generate migrations would be drizzle-kit generate so your professional production-ready deployment process would be 1. connect to VPN to your staging copy of the project 2. locally run drizzle-kit generate and commit the migration files 3. push to trigger deploy - Zerops will apply the migration on runtime initialization
191 replies
ZZerops
Created by Louay on 1/22/2025 in #💪・community-support
Ubuntu password
zerops:
- setup: app
build:
base: nodejs@20
buildCommands:
- npm i
- npm run build
# install deps for runtime migrations
- npm install drizzle-kit drizzle-orm postgres
deployFiles:
- .next
- package.json
- node_modules
- public
# folder that contains migration files
# example: https://github.com/spartan-ng/spartan/tree/main/apps/app/drizzle
- drizzle
# drizzle config for migrations
# example: https://github.com/spartan-ng/spartan/blob/main/tools/scripts/drizzle-migrate.config.ts
- drizzle-migrate.config.ts
cache:
- node_modules
run:
base: nodejs@20
envVariables:
DATABASE_URL: ${db_connectionString}/${db_dbName}
initCommands:
- zsc execOnce $appVersionId -- drizzle-kit migrate --config=drizzle-migrate.config.ts
ports:
- port: 3000
httpSupport: true
start: npm start
zerops:
- setup: app
build:
base: nodejs@20
buildCommands:
- npm i
- npm run build
# install deps for runtime migrations
- npm install drizzle-kit drizzle-orm postgres
deployFiles:
- .next
- package.json
- node_modules
- public
# folder that contains migration files
# example: https://github.com/spartan-ng/spartan/tree/main/apps/app/drizzle
- drizzle
# drizzle config for migrations
# example: https://github.com/spartan-ng/spartan/blob/main/tools/scripts/drizzle-migrate.config.ts
- drizzle-migrate.config.ts
cache:
- node_modules
run:
base: nodejs@20
envVariables:
DATABASE_URL: ${db_connectionString}/${db_dbName}
initCommands:
- zsc execOnce $appVersionId -- drizzle-kit migrate --config=drizzle-migrate.config.ts
ports:
- port: 3000
httpSupport: true
start: npm start
191 replies
ZZerops
Created by Louay on 1/22/2025 in #💪・community-support
Ubuntu password
sure, the problem is that drizzle is currently still all over the place (with both the code and their docs, it still feels like an alpha/beta), for example the migrate command requires you to pass a config file to it, instead of just defining the connection details using params / env variables)... you also need to locally generate the migrations, which you then commit to your repository.. but the final setup could looks something like this
191 replies