Absolute Asset Paths

Hey Matteo Maranta

I think that's the right behavior (unless I misunderstood something), you're seeing your env var SITE_BASE_URL because it's being used in the getBasePath() method

Cheers!

Hey Voltel,

Our advice is KnpSnappyBundle: https://github.com/KnpLabs/... - that just a wrapper around Wkhtmltopdf tool. And looks like it' the most popular bundle for Symfony that works with PDF.

Unfortunately, I'm not sure what Ryan had on mind at that second, but I'd say that env vars approach is probably the best option. Another option would be to hardcode URLs, but that's not a good option.

Cheers!

Hi victor!

About the other approach around 4:34, I don't remember exactly (to be honest), but I believe that it mostly involved different approaches to using the SITE_BASE_URL. In Symfony, there is an idea of "asset packages" and you can define a base URL for each "asset package". Then, when you use the asset() function (or use that same code in PHP), that package will automatically add the base URL. I think this was the other approach I played with. In the end, I didn't choose that because it's... just a bit more confusing to explain. The approach I used is pretty direct: we create a SITE_BASE_URL variable and then use it in our code. We're not leveraging any, sort of, "invisible magic" to get the job done.

Cheers!

Hey Raed

The @ character is used to indicate Symfony that you want to inject a service

The % sign indicates Symfony that you want to inject a parameter or environment variable through using the %env(SOME_VARIABLE)% notation

Does it makes more sense to you now?
Cheers!

Hey MolloKhan,

Thank you so much for this very helpful and clear clarification.

Hey Tomasz,

What exactly hardcoded value are you talking about? If you're about SITE_BASE_URL - it's not exactly hardcoded value, it's dynamic variable.

Cheers!

I mean for me it seems to be better to rely on Symfony magic and mechanism already implemented in Request class instead "hardcoding" it into environment variable which you have to always fill in before starting real work. It's personal, although. :)

Hey Tomasz,

Ah, yes, I see what you mean :) Personally, I agree with you and I'm always trying to achieve it with app.request things :) But! Sometimes we need to have that HTTP host somewhere in the config, like in our case here where we set it uploads_base_url parameter, i.e. sometimes we need to have that parameter hardcoded. Or for host specific routes, etc. Yes, it causes some incoveniences that you have to tweak that parameter on some servers to get project working, but still it's done in one spot only, you don't have to change all possible hardcoded URLs all over the project code as we use that env var values everywhere, so just need to tweak that env var.

I hope this makes sense for you! But I agree, if you can avoid using such env var in favor of using app.request in your project - that would be even better.

Cheers!