Different environment variables for different servers

[artpolikarpov]

How to set different environment variables for different servers? Looks like env property in server object does nothing.

module.exports = {
    // Server authentication info
    "servers": {
        '1': {
            "host": "xxx.xxx.xxx.xx",
            "username": "user",
            "pem": "/Users/user/Projects/DEPLOY/google_compute_engine",
            "env": {
                "DYNO": "dyno-name",
                "ASSETS_HOST": "https://xxx.somecdn.com"
            }
        },

In your sample mup.js you even delete env property. So, how to differentiate variables from server to server?

[artpolikarpov]

In other issue I read that that feature is planed. But for me this one is absolutely critical, I already deployed servers in production and only after that I realized that you have removed that feature. Early (with mupx) it worked with no problem.

Can you point out where to start to bring this feature on? I’ll try to add it at least for myself (or will try to pr it back to you).

[madushan1000]

This function takes care of env vars, I can't think of a direct way to implement the feature though. PRs are welcome :)

[artpolikarpov]

I already found this function and still have no idea how to solve the problem. Now you build env object before iterating the session, but we need some way to revert it — to build uniq env for each session. Or find place where to extend env later.

[artpolikarpov]

@madushan1000, can you help? I think it is a essential feature.

[etyp]

+1 - @madushan1000 any chance we can get #248 merged in?

[madushan1000]

I can merge it, but I can't test it at the time. So there would not be a npm release.

[madushan1000]

One the other hand, if someone can write some tests, I can test them using out test rig.

[rclai]

Please someone make the tests :(

[rclai]

Also, shouldn't those custom env variables be in the meteor.servers[<server-key>][<custom_var>] instead of the servers.env object?

[stevenhornung]

Any updates here? Would love to get this feature merged!

[zodern]

This will be available in 1.3.

[sidzan]

Has this feature been implemented yet? Cheers!

[micahalcorn]

For reference, this is now implemented using the pattern meteor.servers.{name}.env. ✅