unmaintainable-code VS Nginx

Two thoughts:

* This is ridiculous. Why would you do this? Which made think of this quote: "Which is ridiculous and unnecessary but when has that ever stopped programmers?" from one of my favorite Tom Scott videos: https://www.youtube.com/watch?v=gocwRvLhDf8

* How to Write Unmaintainable Code: https://github.com/Droogans/unmaintainable-code

How to Write Unmaintainable Code is basically a must-read for any programmer in my opinion, even so many years later.

Oh my the defines. What is language and semantics?

Very ugly, ill-defined, uncodified democracy. No one tells you when you vote, no one counts up the votes, there are no official results.

When you speak or communicate with someone else, you are voting with them. "I vote this word means X, for a poor/crude/coarse agreement of what X is the first place."

And this is propaganda at its finest. Evil doublespeak: say one thing, and it actually is another. Snuck in.

Fantastic.

Related: https://github.com/Droogans/unmaintainable-code

May I anti-recommend (i.e. suggest you read so as not to follow the advice of it) this wonderfully written guide here on unmainable code.

How To Write Unmaintainable Code

So yes, I don't think I have ever typed out "fileDescriptor" but I do label these things to make it more legible!

OP has a point. We could do with more discipline when it comes to naming conventions in C. We're not using punch cards any longer.

Somewhat related, there's another comment about the 80 char max... clang-format keeps to this. I'm kind of OK with this particular remnant of punch cards because I can get four editor windows open side by side on my ultra wide monitor.

The nginx codebase is pretty freaking fantastic and I've learned a lot from just randomly browsing through the source, but I mean, come on:

https://github.com/nginx/nginx/blob/master/src/core/ngx_arra...

  if ((u_char *) a->elts + a->size * a->nalloc == p->d.last) {

For frontend applications - it can be quite simple to implement preview environments with a simple static storage and a reverse proxy tool like Nginx or Traefik.

Last but not least, we should configure TLS for upstreams. In the following, I'll use a simple nginx instance that responds with static content. Use it as an illustration for more complex upstreams.

set(NGINX_CONFIGURE_ARGS "--with-threads" "--with-compat") if (DEBUG) set(NGINX_CONFIGURE_ARGS "--with-threads" "--with-compat" "--with-debug") endif() message("args ${NGINX_CONFIGURE_ARGS}") # build against nginx at the version specified by GIT_TAG. nginx uses custom auto configuration scripts that # creates header files that are specific to the current host and output to /objs/*.h. ExternalProject_Add( nginx PREFIX ${CMAKE_BINARY_DIR}/_deps/nginx GIT_REPOSITORY https://github.com/nginx/nginx.git GIT_TAG release-1.23.2 TIMEOUT 10 CONFIGURE_COMMAND ./auto/configure ${NGINX_CONFIGURE_ARGS} INSTALL_COMMAND "" #empty install command to disable install UPDATE_COMMAND "" #empty update command to disable update LOG_DOWNLOAD ON BUILD_IN_SOURCE 1 #build inside of the downloaded repo's source directory as expected by auto/configure ) if(NOT DEFINED $ENV{ZITI_SDK_C_BRANCH}) SET(ZITI_SDK_C_BRANCH "main") endif() FetchContent_Declare(ziti-sdk-c GIT_REPOSITORY https://github.com/openziti/ziti-sdk-c.git GIT_TAG ${ZITI_SDK_C_BRANCH} ) set(ZITI_BUILD_TESTS off) set(ZITI_BUILD_PROGRAMS off)a FetchContent_MakeAvailable(ziti-sdk-c) add_dependencies(${PROJECT_NAME} nginx) ExternalProject_Get_property(nginx SOURCE_DIR) message("project name ${PROJECT_NAME}") target_include_directories(${PROJECT_NAME} PUBLIC "${SOURCE_DIR}/objs" PUBLIC "${SOURCE_DIR}/src/core" PUBLIC "${SOURCE_DIR}/src/event" PUBLIC "${SOURCE_DIR}/src/event/modules" PUBLIC "${SOURCE_DIR}/src/http" PUBLIC "${SOURCE_DIR}/src/http/modules" PUBLIC "${SOURCE_DIR}/src/mail" PUBLIC "${SOURCE_DIR}/src/stream" PUBLIC "${SOURCE_DIR}/src/os/unix" ) target_link_libraries(${PROJECT_NAME} ziti)

nginx uses switch on a combination of length + specific known characters as part of a similar optimization.

https://github.com/nginx/nginx/blob/9c7a2c7ce4ad02a36df1bb0e...

In order to publish it as service, you have to combine it with some web server. In Pleroma, the cases using nginx seem more than Apache or Caddy.

I developed an application which utilizes web sockets and tried to host it on digital ocean vps (ubuntu 22). I discovered that nginx supports web sockets starting from v 1.3.13 and I reinstalled nginx following the official guide http://nginx.org/en/linux_packages.html#Ubuntu. However the version which got installed was 1.23.3. On nginx main page https://nginx.org/, it seems that the version of the latest release is 1.29 . Can someone explain why is that the case? And how can I get nginx v1.3.13+ on my server?

On nginx main page https://nginx.org/, it seems that the version of the latest release is 1.29 .