Repository navigation
Conversation
- idem deploy: signs in through the browser if needed, links the folder (creating the application the first time: name, workspace, .env variables), sends the code as Git sees it (.gitignore/.idemignore, never node_modules, .git or .env), follows the deployment live, ends with the address or the cause of the failure (exit code 1). - idem: a menu for the application of this folder. - login (browser device flow, or --token) / logout (revokes the token) / whoami, apps, link/unlink, status, logs [-f], open [--dashboard], restart, rollback, env ls/set/rm/pull, dashboard. - --json everywhere, --yes and IDEM_TOKEN for CI. - CI (typecheck, build) and npm release on v* tags.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Command-line iDeploy:
idem deployin one command, plus most of what the UI does.Deploy (all the methods)
idem deploy--git <url> [--branch] [--base-dir]--image <ref> [--tag] [--registry-user]IDEM_REGISTRY_PASSWORD, never on the command line)--compose <file>--template <name>--regionwhen the plan allows it) or one of your servers (--server). On a terminal, the CLI asks.--install,--build,--start,--port,--publish-dir.--uploadsends the folder instead..envvariables are offered, or given with--env [file]. iDeploy then links the workspace's resources.Commands
apps,status,deployments,logs [-f],open [--dashboard],restart,start,stop,rollback,destroy,env ls/set/rm/pull,domains ls/add/rm(DNS and HTTPS state, record to create),link,unlink.workspaces ls/create/show/rmdb ls/create/show/start/stop/restart/backup/rm(9 engines)services ls/start/stop/restart/rm,templates [search]servers ls/add/check/setup/rm:addgenerates the SSH key (or uses yours), shows the line forauthorized_keys, checks the server, then installs Docker and the proxy.login(browser device flow, or--token),logout(revokes the token),whoami,dashboard.idemalone opens a menu.--jsonworks everywhere.--yesandIDEM_TOKENare for CI.Checks
Done in a Node 20 container:
tsc --noEmit, build (tsup) and--helppass;.envparsing was tried;The full flows need Idem-AI/idem#386 (browser sign-in) and #387 (live logs) deployed.
Publishing
NPM_TOKENsecret and the@idem-aiscope on npm are needed.git tag v0.1.0 && git push --tags.