heroku-buildpack-nodejs VS cowboy

No default language could be detected for this app. HINT: This occurs when Heroku cannot detect the buildpack to use for this application automatically. See https://devcenter.heroku.com/articles/buildpacks

Choose a buildpack explicitly https://devcenter.heroku.com/articles/buildpacks

Another alternative that comes to my mind it is to use the node.js buildpack and serve the static files using serve or similar.

Support for Buildpacks from Heroku

You use a buildpack.

Counting objects: 36, done.Delta compression using up to 4 threads.Compressing objects: 100% (33/33), done.Writing objects: 100% (36/36), 19.22 KiB | 0 bytes/s, done.Total 36 (delta 3), reused 0 (delta 0)remote: Compressing source files... done.remote: Building source:remote: remote: -----> Failed to detect set buildpack https://codon-buildpacks.s3.amazonaws.com/buildpacks/heroku/python.tgzremote: More info: https://devcenter.heroku.com/articles/buildpacks#detection-failureremote: remote: ! Push failedremote: Verifying deploy....remote: remote: ! Push rejected to dry-waters-63931.remote: To https://git.heroku.com/dry-waters-63931.git ! [remote rejected] master -> master (pre-receive hook declined)error: failed to push some refs to 'https://git.heroku.com/dry-waters-63931.git' My root directory:

Now that your app is registered to Heroku, we have to set up a buildpack.

-----> Building on the Heroku-20 stack -----> Using buildpack: https://github.com/heroku/heroku-buildpack-nodejs -----> Node.js app detected -----> Creating runtime environment NPM_CONFIG_LOGLEVEL=error NODE_VERBOSE=false NODE_ENV=production NODE_MODULES_CACHE=true -----> Installing binaries engines.node (package.json): unspecified engines.npm (package.json): unspecified (use default) Resolving node version 16.x... Downloading and installing node 16.14.0... Using default npm version: 8.3.1 -----> Installing dependencies Installing node modules npm ERR! code 1 npm ERR! path /tmp/build_1816a6d9/node_modules/argon2 npm ERR! command failed npm ERR! command sh -c node-gyp rebuild npm ERR! gyp info it worked if it ends with ok npm ERR! gyp info using [email protected] npm ERR! gyp info using [email protected] | linux | x64 npm ERR! gyp info find Python using Python version 3.8.10 found at "/usr/bin/python3" npm ERR! gyp http GET https://nodejs.org/download/release/v16.14.0/node-v16.14.0-headers.tar.gz npm ERR! gyp http 200 https://nodejs.org/download/release/v16.14.0/node-v16.14.0-headers.tar.gz npm ERR! gyp http GET https://nodejs.org/download/release/v16.14.0/SHASUMS256.txt npm ERR! gyp http 200 https://nodejs.org/download/release/v16.14.0/SHASUMS256.txt npm ERR! gyp info spawn /usr/bin/python3 npm ERR! gyp info spawn args [ npm ERR! gyp info spawn args '/tmp/build_1816a6d9/.heroku/node/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py', npm ERR! gyp info spawn args 'binding.gyp', npm ERR! gyp info spawn args '-f', npm ERR! gyp info spawn args 'make', npm ERR! gyp info spawn args '-I', npm ERR! gyp info spawn args '/tmp/build_1816a6d9/node_modules/argon2/build/config.gypi', npm ERR! gyp info spawn args '-I', npm ERR! gyp info spawn args '/tmp/build_1816a6d9/.heroku/node/lib/node_modules/npm/node_modules/node-gyp/addon.gypi', npm ERR! gyp info spawn args '-I', npm ERR! gyp info spawn args '/app/.cache/node-gyp/16.14.0/include/node/common.gypi', npm ERR! gyp info spawn args '-Dlibrary=shared_library', npm ERR! gyp info spawn args '-Dvisibility=default', npm ERR! gyp info spawn args '-Dnode_root_dir=/app/.cache/node-gyp/16.14.0', npm ERR! gyp info spawn args '-Dnode_gyp_dir=/tmp/build_1816a6d9/.heroku/node/lib/node_modules/npm/node_modules/node-gyp', npm ERR! gyp info spawn args '-Dnode_lib_file=/app/.cache/node-gyp/16.14.0/<(target_arch)/node.lib', npm ERR! gyp info spawn args '-Dmodule_root_dir=/tmp/build_1816a6d9/node_modules/argon2', npm ERR! gyp info spawn args '-Dnode_engine=v8', npm ERR! gyp info spawn args '--depth=.', npm ERR! gyp info spawn args '--no-parallel', npm ERR! gyp info spawn args '--generator-output', npm ERR! gyp info spawn args 'build', npm ERR! gyp info spawn args '-Goutput_dir=.' npm ERR! gyp info spawn args ] npm ERR! gyp: Undefined variable module_name in binding.gyp while trying to load binding.gyp npm ERR! gyp ERR! configure error npm ERR! gyp ERR! stack Error: `gyp` failed with exit code: 1 npm ERR! gyp ERR! stack at ChildProcess.onCpExit (/tmp/build_1816a6d9/.heroku/node/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:259:16) npm ERR! gyp ERR! stack at ChildProcess.emit (node:events:520:28) npm ERR! gyp ERR! stack at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12) npm ERR! gyp ERR! System Linux 4.4.0-1098-aws npm ERR! gyp ERR! command "/tmp/build_1816a6d9/.heroku/node/bin/node" "/tmp/build_1816a6d9/.heroku/node/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild" npm ERR! gyp ERR! cwd /tmp/build_1816a6d9/node_modules/argon2 npm ERR! gyp ERR! node -v v16.14.0 npm ERR! gyp ERR! node-gyp -v v8.4.1 npm ERR! gyp ERR! not ok npm ERR! A complete log of this run can be found in: npm ERR! /tmp/npmcache.9omWv/_logs/2022-02-12T13_14_33_973Z-debug-0.log -----> Build failed We're sorry this build is failing! You can troubleshoot common issues here: https://devcenter.heroku.com/articles/troubleshooting-node-deploys Some possible problems: - Node version not specified in package.json https://devcenter.heroku.com/articles/nodejs-support#specifying-a-node-js-version Love, Heroku ! Push rejected, failed to compile Node.js app. ! Push failed

My first instinct was to (cry) manually set the appropriate buildpack for a node.js server as mentioned by Heroku's Dev Center. However, Heroku states that...

Dokku is a popular, open-source, and self-hosted platform as a service (PaaS) that allows users to easily deploy and manage their applications, very similar to your own self-hosted Heroku. Under the hood, Dokku is powered by Docker, uses Heroku buildpacks by default, and has a number of official and community plugins.

According to the 'Server' response header, Cowboy is the customer facing web server https://github.com/ninenines/cowboy

===> sh(git clone -n https://github.com/ninenines/cowboy .tmp_dir636214859401) failed with return code 128 and the following output: Cloning into '.tmp_dir636214859401'... fatal: unable to access 'https://github.com/ninenines/cowboy/': SSL certificate problem: unable to get local issuer certificate

RE: HTTP/Web Sockets/TCP/UDP/etc. - check out NineNines libraries: Ranch (TCP Socket Acceptor), Cowboy (HTTP Server), Gun (HTTP client), and CowLib (General HTTP/SPDY library) are pretty good from what I hear.

Ranch is a pretty well optimized and battle hardened tcp acceptor. It powers the Cowboy/Phoenix server which scales to extreme level of concurrency and low latency. Cowboy uses ranch to pool and accept connections and I believe it uses {active,once}.

https://github.com/ninenines/cowboy

https://github.com/ninenines/ranch

I have a web application which uses cowboy and cachex every so often cachex errors, which means my server returns a 500.

Cowboy is a small, fast and modern HTTP server for Erlang/OTP.

plug_cowboy: Uma implementação do Cowboy para o Elixir.

We are going to be using the light http server Cowboy and the adapter Plug to return our data.

At the core of your web app (and any other app that works with HTTP) will be Cowboy, but further than that, you need to know what a web app consists of and pick your tools for each layer separately.