9d88d41d-d840-4ff7-9796-a4dcf88468f1

for a Dockerfile build, just dont use ARG in your Dockerfile and the variables will not be available during build!

Yeah, but will they be available during runtime? I'm running into that issue

yes they will

HMM

I'm POd

Spent an hour messing with stuff

from your deploy logs -

RuntimeError: Either 'SQLALCHEMY_DATABASE_URI' or 'SQLALCHEMY_BINDS' must be set.

and unless I'm blind, you do not have either of them set

app.config["SQLALCHEMY_DATABASE_URI"] = os.getenv("HH_DATABASE_URL")

There was an extra space after URL which might be causing the issue

that could do it

of course it was

just wanna let you know that you are subjecting yourself to egress fees and slower networking by having the database in a separate project and connecting to it via the public network

hmm, how would I avoid that?

This is kinda weird but I have a singular database that is connected to by multiple projects

🙂

Because, spinning up 5 different database instances is crazy expensive

not ideal tbh, you'd want an induvial database in each project

too much $$

ever since they moved the DBs over to containerized

you pay in egress and slower networking

databases have always been ran in containers though? im not sure what you mean, sorry

Awhile back there was some old version of databases and they had to get everyone to migrate

yeah they where still containers, we just didnt charge for egress or storage back then

Since then it was pretty cheap to run DBs per project, but since then I combined the databases into a singular one

hmm

postgres uses much less idle resources btw

im telling you this because i've seen too many people ask the "why do i have a $200 in egress my application doesnt get much traffic" question and i dont want that to be you

Maybe I am missing something

Is there a cap?

oh

new billing period

$200 was just an example, you are connecting to the database publicly, theres always the possibility of some rouge code generating a lot of traffic to your database

Oh I'm actually doing this a lot lol

Example: 98e650c9-d0c2-42e7-9e30-641d0e0cabbf

Connects to Redis through its public URL even though I have them in the same instance

the potential for a large egress bill and the much slower networking is not worth the immediate cost savings of a single separate database

I mean, at that point I could just move everything to a singular project

thats clutter though and not scalable

you hardcoded the url to the public url for redis

$5/mo for each database vs my current $0.22 in egress usage

That's fine, these are all just for my portfolio

like i mentioned, there is always the possibility your code does something and generates a lot of egress to the database, many such cases

of course you do what you think is best, i just don't want us to have to tell you that you indeed need to pay that random unexpected $200 bill for egress

I appreciate the insight

I'll work on switching stuff over

to postgres? 😉

Maybe 😂

your mysql idles at ~500mb of memory with 410mb of used volume, i have a postgres database that has ~7gb of used volume and idles at 105mb.

maybe thats enough to convince you

Btw, is this how I would create a proper reference?

When I click add, the template gets replaced with the actual URL

I'll start converting 🫡

Luckily most of these are using Sequelize or other ORMs so I should be able to just switch the connector, but I think there's a couple projects that are a little more involved

And some that require a data migration unfortunately :/

!s