paging @iKevinY , @rwblickhan , @brian-nguyen for thoughts 🙏

Does this mean we can deploy multiple projects to a single remote?

@rwblickhan no, but it does mean that you can more easily deploy a different project to the same remote to "recycle" them so to speak. For example:

inertia remote add local
inertia init
inertia project apply [profile-name] local # not implemented yet

then in another project:

inertia project apply [profile-name] local

then, when you run inertia local up in the two different projects, Inertia will apply your configured "profile" (but it'll still be one project per remote)

that said, if multi-project remotes is something people want... this would help that too 🤔

I am for the shift to YAML because of the uniformity with cloud providers configuration files e.g gcloud and aws.

@yaoharry the thing is, yml was more designed to be handwritten, whereas toml is more consistent and generally generated - hence why I feel like it's been best for Inertia in the past. I think we'll probably stick with it for now, and hopefully we never get ot a point where you have to do a lot of hand-writing inertia configuration 😋 thanks for the feedback though!

@mRabitsky note taken about the nested properties - I've update the configuration to use lists instead of maps. We lose the uniqueness guarantees, but we have a much nicer-looking configuration now (let me know if this still isn't what you had in mind:

inertia.toml

name = "test"
url = ""

[[profile]]
  name = "dev"
  branch = ""
  [profile.build]
    type = "dockerfile"
    buildfile = "Dockerfile.dev"

[[profile]]
  name = "staging"
  branch = ""
  [profile.build]
    type = "dockerfile"
    buildfile = "Dockerfile.staging"

inertia.global

[[remote]]
  version = ""
  name = "dev"
  ip = "0.0.0.0"
  [remote.ssh]
    user = "bob"
    pemfile = ""
    ssh-port = ""
  [remote.daemon]
    port = "4043"
    token = ""
    webhook-secret = ""
    verify-ssl = false
  [remote.profiles]
    asdf = "asdf"
    oipo = "oiup"

[[remote]]
  version = ""
  name = "staging"
  ip = "0.0.0.0"
  [remote.ssh]
    user = "bob"
    pemfile = ""
    ssh-port = ""
  [remote.daemon]
    port = "4043"
    token = ""
    webhook-secret = ""
    verify-ssl = false
  [remote.profiles]
    fdsa = "fdsaf"
    wqrte = "erterh"

@mRabitsky re:

As for the question of projects needing versions, perhaps that's something that Git's hashes can handle? (I think that's how it works in other similar systems).

By version I was referring to Inertia version. In remote, this is used to determine which daemon build to deploy - hence why I'm unsure if the version needs to be tracked elsewhere. Right now, if the format changes Inertia will just silently break where the format no longer matches

Codecov Report

Merging #577 into master will decrease coverage by 1.14%.
The diff coverage is 62.93%.

@@            Coverage Diff             @@
##           master     #577      +/-   ##
==========================================
- Coverage    56.5%   55.36%   -1.13%     
==========================================
  Files          62       67       +5     
  Lines        3020     3004      -16     
==========================================
- Hits         1706     1663      -43     
- Misses       1105     1145      +40     
+ Partials      209      196      -13

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update afc9e39...4133120. Read the comment docs.

thanks @iKevinY 😋 i've updated the references

you don't have to read the code, sorry for the sinful PR 😂