fix: Support Airtable import even mapped to a different port

[pranavxc]

Change Summary

In the existing release it Airtable import will fail in docker if mapped to a port other than 8080.

Change type

• feat: (new feature for the user, not a new feature for build script)
• fix: (bug fix for the user, not a fix to a build script)
• docs: (changes to the documentation)
• style: (formatting, missing semi colons, etc; no production code change)
• refactor: (refactoring production code, eg. renaming a variable)
• test: (adding missing tests, refactoring tests; no production code change)
• chore: (updating grunt tasks etc; no production code change)

Test/ Verification

re #2127

[wingkwong]

@pranavxc Since PR Release failed, I triggered nightly build on f99ad57.

I got Error: connect ECONNREFUSED 127.0.0.1:80.

Here's the command I used. Not sure if I missed some env var or not.

docker run -d --name nocodb-pr2134 \
-p 7777:8080 \
-e NC_BASEURL_INTERNAL=7777 \
nocodb/nocodb-timely:0.91.0-20220524-1028

[pranavxc]

@pranavxc Since PR Release failed, I triggered nightly build on f99ad57.

I got Error: connect ECONNREFUSED 127.0.0.1:80.

Here's the command I used. Not sure if I missed some env var or not.

docker run -d --name nocodb-pr2134 \
-p 7777:8080 \
-e NC_BASEURL_INTERNAL=7777 \
nocodb/nocodb-timely:0.91.0-20220524-1028

In the case of docker, you can ignore the NC_BASEURL_INTERNAL since it will populate based on PORT. If you are providing it need to be a full URL like http://localhost:8080.

Within docker port 7777 is not available so the value should be http://localhost:8080 unless you are changing the PORT env value.

Try the following

docker run -d --name nocodb-pr2134 \
-p 7777:8080 \
nocodb/nocodb-timely:0.91.0-20220524-1028

[wingkwong]

Oh yes. I misread it. Verified using your command.