serve VS age

The above code starts a static server (Vercel’s serve) in port 3000. Open the URL in Chrome, open the DevTools, and click the Source tab. You’ll see main.ts as follows:

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

If you don't know how to create a backend, you can try https://npmjs.com/package/serve which is a command that will run a simple server that just serves you the files in a folder (kinda like /public does) but it runs separately from CRA/Webpack so will not affect your app. You then have to take care of fetching and updating the data with fetch() as often as you need.

In app.jsx I've tried removing all the root code and just rendered a typical "Hello World" p tag and it doesn't take nearly as long. I've also ran a basic web server infront of the build folder using serve which suggests it might webpack-dev-server that is having issues with the size of the application (Or could it be saying it's built before it actually is?).

Maybe I was lacking context a bit. I was referencing this actually: https://github.com/vercel/serve/pull/680

https://github.com/vercel/serve (nodejs implementation, therefore requires npm or yarn being installed which are package managers for node)

React.js/ Next.js / Material-UI / Browserify (bundle packaging) / Serve (static site serving) / React-Dropzone (file drag drop) / React-Idle-Timer / zxcvbn.js (Password strength estimation)

https://github.com/vercel/serve (that one should run on every system since it's implemented in NodeJS)

and echoing the result after converting to an age private key

I like that https://github.com/FiloSottile/age has small public keys.

> something fresh

It exists, it's called age..

Some random links

https://github.com/FiloSottile/age

https://www.reddit.com/r/crypto/comments/hr64hr/state_of_age...

https://github.com/FiloSottile/age/discussions/432

> (Acquiring keys, rotating keys, identifying compromised keys, and most importantly either reaches a large enough percentage of emails..

Oh nevermind, age doesn't do any of that. Indeed, it doesn't even do email https://github.com/FiloSottile/age/issues/93

Encrypted secrets thanks to SOPS and Age

I never heard of "Age" before this post. Thank you to share. If others are interested to learn more, here are two other interesting posts about Age:

https://github.com/FiloSottile/age/discussions/432

https://words.filippo.io/dispatches/age-authentication/

of all things I was able to resolve the issue via this github issue: https://github.com/FiloSottile/age/issues/370#issuecomment-1...

Why keep something secret on a public repo? Is that not an oxymoron?

Also, I’m terms of encryption something like age[0] makes it much easier to not shoot yourself in the foot.

[0] https://github.com/FiloSottile/age

Why RSA specifically? For backups, I recommend Tarsnap. But if you really don't want to pay for encrypted cloud hosting, then check out age encryption.

I wouldn't use OpenSSL personally. If you just need simple but secure symmetric encryption, checkout the scrypt(1) encryption utility from Tarsnap. If you need support for public keys, check out age(1).