Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@AleCx04 I'm in the same boat, I basically did trial and error and half-ass read the docs.
I actually hated the way information is structured in some nginx docs. Like today I had to setup nginx to cache certain requests, and the stack overflow solution to my problem didn't seem to have a lot of emphasis in the nginx cache article.
But man, that's another benefit I should have mentioned in the post. You can cache certain requests for local development, so when you refresh a page it instaloads. Very benefficial for the dev cycle.
(and I guess you can fine tune that via nginx options and env vars).
also, I run it locally on docker using `--net=host` and `--rm` args. More simple than installing, running it, reloading the config, etc.
Maybe I should write a post about this. -
@AleCx04 This course is amazing https://udemy.com/course/...
-
@erandria @lamka02sk thanks guys! i will definitely look more into it
-
Found something true as 1 == 1
Life when you didn't know about browsers developer tools
I'm learning nginx and it's simplying the way I think about web projects.
I used to think that when I used a server side framework, then that should be the master and all should go through it. Noob me.
I used to put client side projects (like create-react-app of vue-cli projects) right inside the server side project.
But with nginx you can just route subpaths to different places, then instead of having, let's say, the react project inside rails, they would be in separate git projects.
In fact, I no longer need to restrict myself to a single server framework.
I love several aspects of rails. I love several others of node. And if I need multithreaded performance, I'd very much use something like phoenix or go.
Again, with nginx, you setup subpaths with the `location` directive in the same server and voila, a no CORS setup, cookies shared and homogenous versatile website.
random
nginx
web